Gordon wrote:
I second Andy Mabbet's concern about allowing multiple instances for
fields like e.g. country not making sense.
RFC 2426 says, 'Where it makes semantic sense, individual text
components can include multiple text values (e.g., a street
component with multiple lines) separated
Toby A Inkster schrieb:
Gordon wrote:
I second Andy Mabbet's concern about allowing multiple instances for
fields like e.g. country not making sense.
RFC 2426 says, 'Where it makes semantic sense, individual text
components can include multiple text values (e.g., a street
component with
On Wed, Apr 2, 2008 at 4:03 PM, Gordon [EMAIL PROTECTED] wrote:
One more thing: I am unsure about the plural naming convention I suggested.
Apart from indicating if the value of a property can hold multiple values,
I don't see any added benefit right now. But I do see an unnecessary level
Hi all
Ciaran McNulty wrote:
On Wed, Apr 2, 2008 at 4:03 PM, Gordon [EMAIL PROTECTED] wrote:
One more thing: I am unsure about the plural naming convention I suggested.
[...]
There's very little utility in having the field names reflect their
plurality - a parser needs to know how
Dan Brickley schrieb:
+1 ...keeping the naming the same (minus punctuation fixes for .js
syntax) makes sense.
Ok. New Diagram and Zip are online now.
To sum it up:
1. A jCard has the same properties as any hCard/vCard.
2. Hyphenated properties from hCard/vCard drop the hyphen and use
Here's my contribution!
http://userscripts.org/scripts/show/24705
Microformat marked up BT directory searches.
Should only have taken me 5 mins but thanks to the crappiness and
inconsistencies of BT it took all evening! I mean why does one search
type say Tel: and the other Telephone: !?!?
