xmdp-issues - Revision history

AndyMabbett: {{issues-format}}

2008-01-14T11:01:39Z

← Older revision		Revision as of 11:01, 14 January 2008
Line 36:		Line 36:

	* 2007-11-07 raised by [[User:Tantek\|Tantek]]		* 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].''		*# [[xmdp-parsing]] needs to be specified above and beyond the declarative explanation in [http://gmpg.org/xmdp/ XMDP].


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

	== Template ==		== Template ==
	~~Please use this format (copy and paste this above to add your~~ issues):		{{issues-format}}
	* YYYY-~~MM-DD raised by [http://yourhomepage.example.com YOURNAME].~~
	*# ''Issue 1: Here is the first issue I have.''
	*# ''Issue 2: Here is the second issue I have.''

Tantek: added need for explicit xmdp-parsing explanation.

2007-11-07T20:47:10Z

added need for explicit xmdp-parsing explanation.

← Older revision		Revision as of 20:47, 7 November 2007
Line 34:		Line 34:
	From: [http://www.pacificspirit.com/blog/2007/09/28/microformats_and_uri_based_extensibility Dave Orchard's Blog: Microformats and URI based extensibility]		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.		* TO DO: extract issues from that URL and itemize them here.

			* 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].''


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

Tantek: collected URL to issues raised by David Orchard in his blog post, note need to extract them.

2007-11-07T20:41:15Z

collected URL to issues raised by David Orchard in his blog post, note need to extract them.

← Older revision		Revision as of 20:41, 7 November 2007
Line 8:		Line 8:
	== Closed Issues ==		== Closed Issues ==
	Resolved issues that have no further actions to take. These will likely be moved to a separate page like [[xmdp-issues-closed]].		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 19:		Line 19:
	== Resolved Issues ==		== 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.		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 31:		Line 31:
	Add new issues to the ''end'' of this list.		Add new issues to the ''end'' of this list.

	* ...		=== 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.''		''Feel free to add issues here. Keep issues in this list in summary form. Save lengthy discussion and potential solutions for elaboration below.''

Tantek: added Closed and Resolved issues sections, moved issues around accordingly

2007-11-07T20:01:03Z

added Closed and Resolved issues sections, moved issues around accordingly

← Older revision		Revision as of 20:01, 7 November 2007
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-07-?? raised by [[User:Bud\|Bud]].		* 2005-07-?? raised by [[User:Bud\|Bud]].
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-07-?? raised by Bud(?).		* 2005-07-?? raised by Bud(?).
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.

			* ...

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

	== Template ==		== Template ==

	Please use this format (copy and paste this above to add your issues):		Please use this format (copy and paste this above to add your issues):
	* YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].		* YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
	*# ''Issue 1: Here is the first issue I have.''		*# ''Issue 1: Here is the first issue I have.''
	*# ''Issue 2: Here is the second issue I have.''		*# ''Issue 2: Here is the second issue I have.''

Tantek: heading, toc editorial, add new issues to end.

2007-11-07T19:38:44Z

heading, toc editorial, add new issues to end.

← Older revision		Revision as of 19:38, 7 November 2007
Line 1:		Line 1:
	= XMDP issues =		<h1> XMDP issues </h1>
			{{TOC-right}}

	These are externally raised issues about [http://gmpg.org/xmdp/ 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. — [http://tantek.com/log/ Tantek]		These are externally raised issues about [http://gmpg.org/xmdp/ 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. — [http://tantek.com/log/ Tantek]
Line 6:		Line 7:

	== Issues ==		== Issues ==
			Add new issues to the ''end'' of this list.

	* 2005-07-?? raised by [[User:Bud\|Bud]].		* 2005-07-?? raised by [[User:Bud\|Bud]].

Tantek: Reverted edit of FucXh0, changed back to last version by Tantek

2007-07-14T17:26:46Z

Reverted edit of FucXh0, changed back to last version by Tantek

@@ 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.''
 *#* ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in [[xmdp-brainstorming]]:
-*#*# <code>
+*#*# <code>&lt;link rel="profile"&gt;</code>, as introduced in the XMDP poster submitted to WWW2005.

FucXh0 at 13:24, 14 July 2007

2007-07-14T13:24:07Z

@@ 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.''
 *#* ACCEPTED. There are two additional proposed ways to link to XMDP profiles which are being discussed/explored in [[xmdp-brainstorming]]:
-*#*# <code>&lt;link rel="profile"&gt;</code>, as introduced in the XMDP poster submitted to WWW2005.
+*#*# <code>

Tantek: moved issues from xmdp-brainstorming to here, cleaned them up.

2005-10-25T21:29:00Z

moved issues from xmdp-brainstorming to here, cleaned them up.

← Older revision		Revision as of 21:29, 25 October 2005
Line 6:		Line 6:

	== Issues ==		== Issues ==

			* 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.''
			# 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.

			* 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.''
			# REJECETED. Bud, that quote you give is XMDP quoting HTML4, please re-read the XMDP spec more carefullly. This is a non-issue.

			* 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]]:
			## <code><link rel="profile"></code>, as introduced in the XMDP poster submitted to WWW2005.
			## <code><a rel="profile" href></code>, as similarly discussed.
			*# ''Consider the supporting use cases: Providing explicit profile definitions for microformats embedded in RSS and Atom and other feeds / envelope formats that don't necessarily have a <head> element with a 'profile' attribute or something similar. I.e. : A very practical motivation for this question is the process of embedding xFolk in an RSS 2.0 feed and the ability to indicate the microformat is in use and where information about it can be found.''
			# ACCEPTED. These are good use cases and will be cited in any development/improvement to XMDP.

			* 2005-07-?? raised by Bud(?).
			*# ''Documents with user-generated content are hard to parse, and microformats present particular parsing challenges.''
			# 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.


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

			== Template ==

			Please use this format (copy and paste this above to add your issues):
			* YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
			*# ''Issue 1: Here is the first issue I have.''
			*# ''Issue 2: Here is the second issue I have.''

Tantek: create and add boilerplate / related

2005-10-25T20:53:18Z

create and add boilerplate / related

New page

= XMDP issues =

These are externally raised issues about [http://gmpg.org/xmdp/ 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. — [http://tantek.com/log/ Tantek]

See related [[xmdp-faq]] and [[xmdp-brainstorming]].

== Issues ==