(edited) Re: XMDP/GRDDL was Re: [uf-new] Namespace anti-pattern and hAudio TITLE (was: hAudio FN or Title)

Mon Feb 4 15:21:51 PST 2008

Apologies, this email sent from my outbox as I was editing it and
unintentionally duplicated some text sent in another email.

It should have had its subject updated and been edited down to:

On 2/4/08 3:05 PM, "Tantek Çelik" <tantek at cs.stanford.edu> wrote:

>> Microformats declare a formal profile[1] in their proposals[2]
>> 
>> [1] http://gmpg.org/xmdp/
>> [2] http://microformats.org/wiki/haudio#XMDP_Profile
>> 
>> and then do this...
>> 
>> <head profile="http://gmpg.org/xfn/11">
>> 
>> very GRDDL Like
>> 
>> <head profile="http://www.w3.org/2003/g/data-view">
> 
> The uses are quite different actually.  XMDP uses the profile attribute for
> defining terms, and GRDDL uses the profile attribute for defining how to
> transform.
> 
> 
>> Maybe someone can explain to me why declare a profile if there isn't
>> some kind of metadata description at the end?
>> 
>> http://gmpg.org/xfn/11
> 
> XMDP provides a simple description mostly just to define the terms.  So far
> we've resisted additional metadata similar to DTDs or XML Schema docs.
> 
> Another big difference is the way XMDP overrides work, linked from [1] cited
> previously above:
> 
> http://gmpg.org/xmdp/description
> 
> Note that if two different profiles define the same term, only the first
> definition is used.  Thus they are not "namespaces" in any data/programming
> functional way (like XML namespaces), as such namespaces make such multiple
> references exist simultaneously and distinctly by keeping them in their own
> silos.
> 
> I have added both of these to the XMDP FAQ:
> http://microformats.org/wiki/xmdp-faq
> 
> Tantek
> 
> _______________________________________________
> microformats-new mailing list
> microformats-new at microformats.org
> http://microformats.org/mailman/listinfo/microformats-new