Subject: Re: [VCARDDAV] property definitions

From: Simon Perreault <[email-masked]>
Date: Thu, 19 May 2011 14:39:56 -0400

On 2011-04-20 16:32, Peter Saint-Andre wrote:
> 1. Section 5.6 of vcardrev says:
> 
>    ABNF:
> 
>            type-param = "TYPE=" type-value *("," type-value)
> 
>            type-value = "work" / "home" / type-param-tel
>                       / type-param-related / iana-token / x-name
> 
> vs. this is in vcardxml:
> 
> param-type = element type { element text { "work" | "home" }+ }?
> 
> Do we need to add more type definitions to vcardxml?

Well, no. Those extra values appear inline for each property to which
they apply.

> 2. Section 6.2.4 of vcardrev says:
> 
>    ABNF:
> 
>      PHOTO-param = "VALUE=uri" / altid-param / type-param
>                  / mediatype-param
>      PHOTO-value = URI
> 
> vs. this in vcardxml:
> 
> property-photo = element photo {
>     element parameters { param-altid, param-pid, param-pref, param-type,
>                          param-mediatype }?,
>     value-uri
>   }
> 
> Is it allowed to specify a preferred photo? If so, does that need to be
> added to vcardrev?
> 
> What about pid being in vcardxml but not vcardrev?

Fixed in vcardrev as indicated in a previous thread.

> 3. Section 6.4.1 of vcardrev says:
> 
>      TEL-param =/ type-param / pid-param / pref-param / altid-param
>                 / any-param
> 
> vs. this is vcardxml:
> 
> property-tel = element tel {
>     element parameters {
>       param-altid,
>       param-pid,
>       param-pref,
>       element type {
>         element text { "work" | "home" | "text" | "voice"
>                      | "fax" | "cell" | "video" | "pager"
>                      | "textphone" }+
>       }?,
>       param-mediatype
>     }?,
>     (value-text | value-uri)
>   }
> 
> It seems that the XML format allows mediatype, but the base spec doesn't.

It is in the base spec:

     TEL-uri-param = "VALUE=uri" / mediatype-param
     TEL-uri-value = URI

(It only makes sense with a URI value.)

(I know the schema is less precise, but the goal is communication, not
validation.)

> 4. Section 6.5.1 of vcardrev says:
> 
>      TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
>      TZ-value = text / URI / utc-offset
> 
> vs. this is vcardxml:
> 
> property-tz = element tz {
>     element parameters { param-altid, param-pid, param-pref,
>                          param-type, param-mediatype }?,
>     (value-text | value-uri)
>   }
> 
> Is utc-offset disallowed in vcardxml because it is not recommended in
> vcardrev?

No, it's a mistake. I added it to vcardxml.

This made me realize that we're missing the section describing the
utc-offset value type which was removed in -08. Since we're now allowing
it in TZ, we need to re-add the section. Re-added.

> 5. Section 6.6.6 of vcardrev says:
> 
>      related-type-value = "contact" / "acquaintance" / "friend" / "met"
>                         / "co-worker" / "colleague" / "co-resident"
>                         / "neighbor" / "child" / "parent"
>                         / "sibling" / "spouse" / "kin" / "muse"
>                         / "crush" / "date" / "sweetheart" / "me"
>                         / "agent" / "emergency"
> 
> vs. this in vcardxml:
> 
>         element text {
>           "work" | "home" | "contact" | "acquaintance" |
>           "friend" | "met" | "co-worker" | "colleague" | "co-resident" |
>           "neighbor" | "child" | "parent" | "sibling" | "spouse" |
>           "kin" | "muse" | "crush" | "date" | "sweetheart" | "me"
>         }+
> 
> Are "agent" and "emergency" not allowed in the XML format?

Added.

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca