xmdp-issues

(Difference between revisions)

Jump to: navigation, search
m (heading, toc editorial, add new issues to end.)
Current revision (11:01, 14 January 2008) (view source)
({{issues-format}})
 
(3 intermediate revisions not shown.)
Line 6: Line 6:
See related [[xmdp-faq]] and [[xmdp-brainstorming]].
See related [[xmdp-faq]] and [[xmdp-brainstorming]].
-
== Issues ==
+
== Closed Issues ==
-
Add new issues to the ''end'' of this list.
+
Resolved issues that have no further actions to take.  These will likely be moved to a separate page like [[xmdp-issues-closed]].
-
 
+
=== 2005 ===
* 2005-07-?? raised by [[User:Bud|Bud]].
* 2005-07-?? raised by [[User:Bud|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.''
*# ''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.''
Line 15: Line 15:
* 2005-07-13T20:01-07:00 raised by [[User:Bud|Bud]].
* 2005-07-13T20:01-07:00 raised by [[User:Bud|Bud]].
*# Follow-up to above issue: ''Actually, this is far from clear.  Reading this excerpt from [http://gmpg.org/xmdp/description 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.''
*# Follow-up to above issue: ''Actually, this is far from clear.  Reading this excerpt from [http://gmpg.org/xmdp/description 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.
+
*#* REJECETD. Bud, that quote you give is XMDP quoting HTML4, please re-read the XMDP spec more carefullly.  This is a non-issue.
 +
== Resolved Issues ==
 +
Issues that are resolved but may have outstanding [[to-do]] items. As issues are resolved, they will be moved from the top of the [[xmdp-issues#Issues|Issues list]] to the bottom of this section.
 +
=== 2005 ===
* 2005-07-?? raised by Bud(?).
* 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.''
*# ''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.''
Line 25: Line 28:
*#* ACCEPTED. These are good use cases and will be cited in any development/improvement to XMDP.
*#* ACCEPTED. These are good use cases and will be cited in any development/improvement to XMDP.
-
* 2005-07-?? raised by Bud(?).
+
== Issues ==
-
*# ''Documents with user-generated content are hard to parse, and microformats present particular parsing challenges.''
+
Add new issues to the ''end'' of this list.
-
*#* REJECTED. This is a straw man issue.
+
-
* 2005-07-13T19:44-07:00 raised by [[User:Bud|Bud]]
+
-
*# Follow-up to previous issue: ''Tantek needs to supply some justification for why this is a strawman as every developer I have talked to has raised it.  It may be that the solutions described below are sufficient to solve the issue. More neutral statements to that effect might be more constructive.''
+
-
*#* REJECTED. Bud, saying "particular parsing challenges", without stating them is meaningless.  Hence strawman.  I think you may be mistaking questions for issues.
+
 +
=== 2007 ===
 +
From: [http://www.pacificspirit.com/blog/2007/09/28/microformats_and_uri_based_extensibility Dave Orchard's Blog: Microformats and URI based extensibility]
 +
* TO DO: extract issues from that URL and itemize them here.
-
''Feel free to add issues here.  Keep issues in this list in summary form. Save lengthy discussion and potential solutions for elaboration below.''
+
* 2007-11-07 raised by [[User:Tantek|Tantek]]
 +
*# [[xmdp-parsing]] needs to be specified above and beyond the declarative explanation in [http://gmpg.org/xmdp/ XMDP].
-
== Template ==
 
-
Please use this format (copy and paste this above to add your issues):
+
'''Feel free to add issues here. Keep issues in this list in summary form. Save lengthy discussion and potential solutions for elaboration below.'''
-
* YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
+
 
-
*# ''Issue 1: Here is the first issue I have.''
+
== Template ==
-
*# ''Issue 2: Here is the second issue I have.''
+
{{issues-format}}

Current revision

XMDP issues

Contents


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.

Closed Issues

Resolved issues that have no further actions to take. These will likely be moved to a separate page like xmdp-issues-closed.

2005

Resolved Issues

Issues that are resolved but may have outstanding to-do items. As issues are resolved, they will be moved from the top of the Issues list to the bottom of this section.

2005

Issues

Add new issues to the end of this list.

2007

From: Dave Orchard's Blog: Microformats and URI based extensibility


Feel free to add issues here. Keep issues in this list in summary form. Save lengthy discussion and potential solutions for elaboration below.

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>
xmdp-issues was last modified: Monday, January 14th, 2008

Views