[uf-discuss] Human and machine readable data format

Ameer Dawood ameer1234567890 at gmail.com
Wed Jul 2 13:04:00 PDT 2008

Hi G,
Internationalization of metadata is a bad and ineffective concept. It would not only result bloat in pharsers, but also bloat in the data format itself. You are proposing to internationalize the machine readable date which is metadata (and not content, in this case). A very clear example would be; if we are to internationalize CSS then "border-color" would become "border-colour" in en-uk. It's like proposing this change with a lang attribute/element.


Sent from my phone using flurry - Get free mobile email and news at: http://www.flurry.com

--- Original Message ---
Date: Wed Jul 02 09:43:00 PDT 2008
From: Guillaume Lebleu <guillaume at lebleu.org>
To: Microformats Discuss <microformats-discuss at microformats.org>
Subject: Re: [uf-discuss] Human and machine readable data format

Michael MD wrote:
> Allowing language conventions for date parsing to be determined by anything "global" sounds a bit dangerous to me.
> Someone might post on a shared blog/forum site in a different country and mark it up in a way that does not match a lang attribute somewhere else on the page!
> also - who is going to say that all replies to the post or comments that might also appear on that same page are going to follow the same language rules 
Sorry if I didn't express myself clearly. What I meant here was that a lang="..." attribute on the element of class vevent or dstart is recommended at all times (to deal with the very ambiguity you are referring to), but is optional to comply with DRY. If not present, its value may be inferred from the closest containing/ancestor element with a lang attribute, for instance a lang attribute value at the level of the html element.

In other words, if I want to write my date in French in an en-us html document, I'd have to attach lang="fr" to my date or its containing content, but if I want to write my date in American English in the same document, I don't have to attach lang="en-us", although it wouldn't hurt to.

Do you still see this as dangerous practice?

microformats-discuss mailing list
microformats-discuss at microformats.org

More information about the microformats-discuss mailing list