No, you're all wrong! :-) Ok, you're all right too.
The way the uF antipattern looks to me is the intention of "ugly URI-based XML namespaces and prefixes simply aren't necessary". Which, in a lot of senses, is probably on the nail. Manu's point seems reasonable, to the extent that parts of the markup hierarchy (vcard etc) do in effect delimit a namespace, though I'm not sure this applies to the hyphenated terms mentioned - I'd read those as names which happen to have hyphens in them. I would personally have no objection whether e.g. a song title was marked up with "title" or "fn", as long as this was adequately documented, and the definition easily discoverable. Which leads me to something Martin mentioned - if HTML Meta Data profiles are used, the whole question becomes a non-issue. By using a profile URI and putting a description of the terms used in the profile on the Web, it's possible for people (and machines) to easily discover the intended meaning. Forget namespaces. Think of a follow-your-nose chain of information to the information the publisher or consumer might need to communicate. After all, the string "title" only has a well-known meaning to a minority of the global population. Why isn't it "titel" or "titulo"? Cheers, Danny. -- http://dannyayers.com ~ http://blogs.talis.com/nodalities/this_weeks_semantic_web/ _______________________________________________ microformats-new mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-new
