[Bug 13929] The microdata vCard and vEvent vocabularies support global identifiers, but the RFC UID formats are invalid URLs

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13929

--- Comment #1 from Oli Studholme <w3.org@boblet.net> 2011-08-28 15:04:19 UTC ---
itemids must be valid URLs, however the spec example microdata vocabularies
give no guidance to valid global identifiers. The example UIDs listed in the
referred RFCs also don’t appear to be one of the IANA URI schemes, eg:

“The type can include the type parameter "TYPE" to specify the format
   of the identifier. The TYPE parameter value should be an IANA
   registered identifier format. The value can also be a non-standard
   format.
Type example: UID:19950401-080045-40000F192713-0052”
http://tools.ietf.org/html/rfc2426#section-3.6.7

“Property Parameters: Non-standard property parameters can be
   specified on this property.
Description: The UID itself MUST be a globally unique identifier. The
   generator of the identifier MUST guarantee that the identifier is
   unique. There are several algorithms that can be used to accomplish
   this. The identifier is RECOMMENDED to be the identical syntax to the
   [RFC 822] addr-spec.
Example: The following is an example of this property:
     UID:19960401T080045Z-4000F192713-0052@host1.com”
http://tools.ietf.org/html/rfc2445#section-4.8.4.7

As itemid is entirely up to the vocabulary it’d help ppl to understand itemid
usage if these specs were clear about what global identifiers are valid,
ideally with an example using a global identifier. This would also help
vocabulary writers (schema.org) to clearly define global identifiers —
http://schema.org/Book only defines ISBN as an itemprop currently.

Ref:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13452
http://microformats.org/wiki/vcard-errata#3.6.7_UID_Type_Definition
http://www.iana.org/assignments/uri-schemes.html

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 28 August 2011 15:04:27 UTC