Summary: | ContactInfo: terminology inconsistent with RFC2426, and no room for expansion | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | Keywords: | patch |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/contactinfo | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Simon McVittie
2009-01-16 09:29:19 UTC
Oops, didn't mean to submit that yet. What I meant to say was: In the current ContactInfo draft, vCard fields' type parameters are referred to as "flags". The RFC calls them type parameters, and we should call them that, to avoid confusion with our <tp:flags> (bitfield) structures. Also, Mandatory is a boolean when it could usefully be a uint containing a bitfield of flags, with one flag (Parameters_Mandatory) currently defined. My contactinfo branch documents this. Fixed in 0.17.18 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.