xmdp-issues: Difference between revisions
Jump to navigation
Jump to search
(moved issues from xmdp-brainstorming to here, cleaned them up.) |
No edit summary |
||
| Line 18: | Line 18: | ||
*# ''Currently, the XMDP can only be linked from the profile attribute of the head element. In many instances, authors will not have access to the head element.'' | *# ''Currently, the XMDP can only be linked from the profile attribute of the head element. In many instances, authors will not have access to the head element.'' | ||
*#* ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in [[xmdp-brainstorming]]: | *#* ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in [[xmdp-brainstorming]]: | ||
*#*# <code> | *#*# <code> | ||
Revision as of 13:24, 14 July 2007
XMDP issues
These are externally raised issues about XMDP with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek
See related xmdp-faq and xmdp-brainstorming.
Issues
- 2005-07-?? raised by Bud.
- Just because a profile value mentioned in a microformat's linked XMDP also appears in the document does not mean that that microformat is in use. Such co-occurrences could be purely by chance.
- REJECTED. No this does not make sense. By definition, an XMDP profile defines certain properties and values. Any use of such property or value in the document is thus defined by the definition in the XMDP.
- Just because a profile value mentioned in a microformat's linked XMDP also appears in the document does not mean that that microformat is in use. Such co-occurrences could be purely by chance.
- 2005-07-13T20:01-07:00 raised by Bud.
- Follow-up to above issue: Actually, this is far from clear. Reading this excerpt from the XMDP description: "This specification does not define a set of legal meta data properties. The meaning of a property and the set of legal values for that property should be defined in a reference lexicon called a profile. For example, a profile designed to help search engines index documents might define properties such as "author", "copyright", "keywords", etc." seems not to imply exclusivity for the whole document, only for the part covered by the profile. If we assumed the quoted words implied exclusivity for the whole document, then only defined attribute values could be used for the whole document. The current usage suggests that we mean the profile to only cover the part of the document covered by the microformat. As such, we cannot use occurrence of a value to connote presence of the microformat. Consider this example, xFolk and hCalendar both use a description class attribute value. Presence of that value is therefore indeterminate as to which format is being used, even if we accepted your claim here, which seems dubious.
- REJECETED. Bud, that quote you give is XMDP quoting HTML4, please re-read the XMDP spec more carefullly. This is a non-issue.
- Follow-up to above issue: Actually, this is far from clear. Reading this excerpt from the XMDP description: "This specification does not define a set of legal meta data properties. The meaning of a property and the set of legal values for that property should be defined in a reference lexicon called a profile. For example, a profile designed to help search engines index documents might define properties such as "author", "copyright", "keywords", etc." seems not to imply exclusivity for the whole document, only for the part covered by the profile. If we assumed the quoted words implied exclusivity for the whole document, then only defined attribute values could be used for the whole document. The current usage suggests that we mean the profile to only cover the part of the document covered by the microformat. As such, we cannot use occurrence of a value to connote presence of the microformat. Consider this example, xFolk and hCalendar both use a description class attribute value. Presence of that value is therefore indeterminate as to which format is being used, even if we accepted your claim here, which seems dubious.
- 2005-07-?? raised by Bud(?).
- Currently, the XMDP can only be linked from the profile attribute of the head element. In many instances, authors will not have access to the head element.
- ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in xmdp-brainstorming:
- ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in xmdp-brainstorming:
- Currently, the XMDP can only be linked from the profile attribute of the head element. In many instances, authors will not have access to the head element.