xoxo-faq - Revision history

KitchM: Outlines Currently in Use

2009-09-16T17:13:42Z

Outlines Currently in Use

← Older revision		Revision as of 17:13, 16 September 2009
Line 66:		Line 66:

	A:		A:


			''Q: Are any wikis using XOXO or anything similar to create collapsing outlines? If so, which ones?

			A:

	== see also ==		== see also ==
	* [[XOXO]]		* [[XOXO]]
	* [[xoxo-issues]]		* [[xoxo-issues]]

Reeder.29: added question: Is there a way to specify a title or name for the outline as a whole?

2009-05-18T02:48:21Z

added question: Is there a way to specify a title or name for the outline as a whole?

← Older revision		Revision as of 02:48, 18 May 2009
Line 61:		Line 61:
	</ol>		</ol>
	</nowiki></pre>		</nowiki></pre>


			''Q: Is there a way to specify a title or name for the outline as a whole?''

			A:

	== see also ==		== see also ==
	* [[XOXO]]		* [[XOXO]]
	* [[xoxo-issues]]		* [[xoxo-issues]]

Brian: Reverted edits by CdronPasol (Talk) to last version by Tantek

2008-12-20T21:49:08Z

Reverted edits by CdronPasol (Talk) to last version by Tantek

← Older revision		Revision as of 21:49, 20 December 2008
Line 1:		Line 1:
	~~delcaacel~~
	<h1> XOXO FAQ </h1>		<h1> XOXO FAQ </h1>
	{{TOC-right}}		{{TOC-right}}

CdronPasol: taerchi

2008-12-20T00:13:08Z

taerchi

← Older revision		Revision as of 00:13, 20 December 2008
Line 1:		Line 1:
			delcaacel
	<h1> XOXO FAQ </h1>		<h1> XOXO FAQ </h1>
	{{TOC-right}}		{{TOC-right}}

Tantek: added Q&A what's XOXO for

2007-10-29T19:59:15Z

added Q&A what's XOXO for

← Older revision		Revision as of 19:59, 29 October 2007
Line 1:		Line 1:
	<h1> XOXO FAQ </h1>		<h1> XOXO FAQ </h1>
			{{TOC-right}}
			This page documents questions and answers regarding the [[XOXO]] (Extensible Open XHTML Outlines) format.

	~~This page documents questions and answers regarding the~~ [[~~xoxo~~]] (~~Extensible Open XHTML Outlines~~) ~~format~~.		== purpose ==
			''Q: what's XOXO for?''

			A: XOXO is a [[microformat]] for marking up collections, lists, and outlines in (X)HTML. [[XOXO]] is based on [[POSH]]. [[XOXO]] can often be used as a building block with other [[microformats]] to construct specific structures and formats. E.g. [[XOXO]]+[[XFN]] produces a portable XFN friends list. See [[hcard-xfn-supporting-friends-lists]] for more on portable XFN friends lists.

	== the 'compact' attribute ==		== the 'compact' attribute ==

	''Q: why is compact/expanded expressed via a new attribute and not by a style class? Wouldn't it be more compatible to simply use a style class?''		''Q: why is compact/expanded expressed via a new attribute and not by a style class? Wouldn't it be more compatible to simply use a style class?''

Line 23:		Line 27:

	A: The 'compact' attribute as specified in HTML4 is purely presentational and as such was deprecated. Since this attribute has been little used, we have repurposed it as a semantic attribute in XOXO that actually preserves the state of whether or not the ''user'' has twiddled an outline item and all its children in the open state vs. the closed state. We recycled the 'compact' attribute instead of making a new attribute to minimize reinvention, and to make an otherwise useless attribute useful again.		A: The 'compact' attribute as specified in HTML4 is purely presentational and as such was deprecated. Since this attribute has been little used, we have repurposed it as a semantic attribute in XOXO that actually preserves the state of whether or not the ''user'' has twiddled an outline item and all its children in the open state vs. the closed state. We recycled the 'compact' attribute instead of making a new attribute to minimize reinvention, and to make an otherwise useless attribute useful again.


	== class="xoxo" ==		== class="xoxo" ==

	''Q: Why don't MarkP's examples use <code><ol class="xoxo"></code> ?''		''Q: Why don't MarkP's examples use <code><ol class="xoxo"></code> ?''

Line 32:		Line 34:

	== other markup in xoxo ==		== other markup in xoxo ==

	''Q: MarkP uses <code><p></code> in some of his examples. Is that allowed? If yes, shouldn't <code><p></code> then be added to the description of XOXO's "document type" (see above)?''		''Q: MarkP uses <code><p></code> in some of his examples. Is that allowed? If yes, shouldn't <code><p></code> then be added to the description of XOXO's "document type" (see above)?''

Line 44:		Line 45:

	== xoxo properties and values ==		== xoxo properties and values ==

	''Q: Can an XOXO item have a multi-valued property, or a property with multiple values?''		''Q: Can an XOXO item have a multi-valued property, or a property with multiple values?''

Tantek: moved unanswered issues to xoxo-issues page for processing

2007-10-29T19:54:26Z

moved unanswered issues to xoxo-issues page for processing

← Older revision		Revision as of 19:54, 29 October 2007
Line 1:		Line 1:
	= XOXO FAQ =		<h1> XOXO FAQ </h1>

	This page documents questions and answers regarding the [[xoxo]] (Extensible Open XHTML Outlines) format.		This page documents questions and answers regarding the [[xoxo]] (Extensible Open XHTML Outlines) format.

	~~== I don't understand what benefits xoxo provides ==~~
	Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. [[User:MikeSchinkel\|MikeSchinkel]] 21:30, 11 Oct 2006 (PDT)

	~~I also do not quite understand the dividing line between a bog-standard HTML list and a xoxo list. What is the defining difference? [[User:Premasagar\|Premasagar]]~~

	== the 'compact' attribute ==		== the 'compact' attribute ==
Line 66:		Line 61:
	</ol>		</ol>
	</nowiki></pre>		</nowiki></pre>

			== see also ==
			* [[XOXO]]
			* [[xoxo-issues]]

WilleRaab: Fixed typo.

2007-07-25T01:54:36Z

Fixed typo.

← Older revision		Revision as of 01:54, 25 July 2007
Line 27:		Line 27:
	''Q: Why is the 'compact' attribute, which was deprecated in the HTML4 specification, used in the XOXO format? Isn't it better not to use any deprecated elements or attributes?''		''Q: Why is the 'compact' attribute, which was deprecated in the HTML4 specification, used in the XOXO format? Isn't it better not to use any deprecated elements or attributes?''

	A: The 'compact' attribute as specified in HTML4 is purely presentational and as such was deprecated. Since this attribute has been little used, we have repurposed it as a semantic attribute in XOXO that actually preserves the state of whether or not the ''user'' has twiddled an an outline item and all its children in the open state vs. the closed state. We recycled the 'compact' attribute instead of making a new attribute to minimize reinvention, and to make an otherwise useless attribute useful again.		A: The 'compact' attribute as specified in HTML4 is purely presentational and as such was deprecated. Since this attribute has been little used, we have repurposed it as a semantic attribute in XOXO that actually preserves the state of whether or not the ''user'' has twiddled an outline item and all its children in the open state vs. the closed state. We recycled the 'compact' attribute instead of making a new attribute to minimize reinvention, and to make an otherwise useless attribute useful again.

Premasagar: /* I don't understand what benefits xoxo provides */

2007-01-13T13:25:54Z

I don't understand what benefits xoxo provides

← Older revision		Revision as of 13:25, 13 January 2007
Line 5:		Line 5:
	== I don't understand what benefits xoxo provides ==		== I don't understand what benefits xoxo provides ==
	Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. [[User:MikeSchinkel\|MikeSchinkel]] 21:30, 11 Oct 2006 (PDT)		Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. [[User:MikeSchinkel\|MikeSchinkel]] 21:30, 11 Oct 2006 (PDT)

			I also do not quite understand the dividing line between a bog-standard HTML list and a xoxo list. What is the defining difference? [[User:Premasagar\|Premasagar]]

	== the 'compact' attribute ==		== the 'compact' attribute ==

MikeSchinkel: Need help understanding XOXO's benefits and use cases

2006-10-12T04:30:14Z

Need help understanding XOXO's benefits and use cases

← Older revision		Revision as of 04:30, 12 October 2006
Line 2:		Line 2:

	This page documents questions and answers regarding the [[xoxo]] (Extensible Open XHTML Outlines) format.		This page documents questions and answers regarding the [[xoxo]] (Extensible Open XHTML Outlines) format.

			== I don't understand what benefits xoxo provides ==
			Color me dense, but I can't for the life of me figure out what XOXO offers. I read about syntax on this wiki, but not about use cases or benefits. Please help me understand! Thanks in advance. [[User:MikeSchinkel\|MikeSchinkel]] 21:30, 11 Oct 2006 (PDT)

	== the 'compact' attribute ==		== the 'compact' attribute ==

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

2005-12-22T01:46:37Z

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

← Older revision		Revision as of 01:46, 22 December 2005
Line 36:		Line 36:

	A: Yes, additional elements and/or attributes are allowed per XHTML Modularization, and no, all such possible additions (e.g. <code><p></code>) don't need to be added to the XOXO document type since XOXO user agents may simply treat them according to the XHTML Modularization user agent conformance requirements (4-6):		A: Yes, additional elements and/or attributes are allowed per XHTML Modularization, and no, all such possible additions (e.g. <code><p></code>) don't need to be added to the XOXO document type since XOXO user agents may simply treat them according to the XHTML Modularization user agent conformance requirements (4-6):
	# ...		1. ...
	# ...		2. ...
	# ...		3. ...
	# If a user agent encounters an element it does not recognize, it must continue to process the children of that element. If the content is text, the text must be presented to the user.		4. If a user agent encounters an element it does not recognize, it must continue to process the children of that element. If the content is text, the text must be presented to the user.
	# If a user agent encounters an attribute it does not recognize, it must ignore the entire attribute specification (i.e., the attribute and its value).		5. If a user agent encounters an attribute it does not recognize, it must ignore the entire attribute specification (i.e., the attribute and its value).
	# If a user agent encounters an attribute value it doesn't recognize, it must use the default attribute value.		6. If a user agent encounters an attribute value it doesn't recognize, it must use the default attribute value.

	== xoxo properties and values ==		== xoxo properties and values ==
Line 61:		Line 61:
	</ol>		</ol>
	</nowiki></pre>		</nowiki></pre>
	~~Note that parsers are not ''required'' to capture both values (in this case, "item1" and the "dl"), but ''may''. This particular pattern is in fact fairly common, and used in blogrolls and S5.~~