Manu Sporny wrote:
- What exactly will be hurt by generalizing TITLE's definition?
- How could this break hCard?
If parsers can disambiguate (can anyone say with confidence that this is so?), perhaps it is okay to leave the value just "title" rather than the
fully qualified "audio-title". However, even if you are comfortable with this -- i.e., that parsers can adequately discern a title in an hCard from
one in hAudio -- I'd steer clear of a "generalized TITLE definition". Handling the definitions that way quickly results in a compilation of useless
information. What you want to do, even if you can leave your property name unqualified (title instead of audio-title), is to use a fully qualified
dictionary entry name for each definition in the wiki. Something like below:
haudio. title The name or label of an audio work
hcard. title The name of a position held by the person
Handling these as two different entries seems strange, but if it makes sense if in fact humans and parsers discern two different concepts based on
context.
This sort of an ISO 15000-lite way of constructing these dictionary names.
Chuck Allen
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
