Bug 19613 - ContactInfo: terminology inconsistent with RFC2426, and no room for expansion
Summary: ContactInfo: terminology inconsistent with RFC2426, and no room for expansion
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2009-01-16 09:29 UTC by Simon McVittie
Modified: 2009-02-02 03:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2009-01-16 09:29:19 UTC 
In the current ContactInfo draft, vCard fields are refered
Comment 1 Simon McVittie 2009-01-16 09:31:26 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.
Comment 2 Simon McVittie 2009-02-02 03:50:32 UTC 
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.