XSPF v1 Notes and Errata - Revision history

Wagettyh: Fix whitespace collapse example

2010-01-25T12:22:37Z

Fix whitespace collapse example

← Older revision		Revision as of 12:22, 25 January 2010
Line 130:		Line 130:
	will become		will become

-	ABC ~~GHI~~ DEF	+	ABC DEF GHI

	Elements affected:		Elements affected:

Sping: /* and privacy */

2008-10-16T03:46:20Z

<playlist.location> and privacy

← Older revision		Revision as of 03:46, 16 October 2008
Line 186:		Line 186:
	Saving an absolute file location in ''playlist.location'' as is not a good idea as it has potential to hurt privacy. To give an example this playlist location		Saving an absolute file location in ''playlist.location'' as is not a good idea as it has potential to hurt privacy. To give an example this playlist location

-	<location>file:///home/bob/porn/~~sountrack~~/ginawild34.xspf</location>	+	<location>file:///home/bob/porn/soundtrack/ginawild34.xspf</location>

	might reveal information that Bob would have liked to keep private.		might reveal information that Bob would have liked to keep private.

Sping: /* and privacy */

2008-10-16T00:50:44Z

<playlist.location> and privacy

← Older revision		Revision as of 00:50, 16 October 2008
Line 189:		Line 189:

	might reveal information that Bob would have liked to keep private.		might reveal information that Bob would have liked to keep private.
		+	This problem is not very XSPF-specific actually, for instance [https://bugs.launchpad.net/inkscape/+bug/168958 Inkscape does this wrong with SVG].

	== <playlist.location> vs. xml:base ==		== <playlist.location> vs. xml:base ==

Sping: playlist location privacy trouble

2008-10-16T00:43:56Z

playlist location privacy trouble

← Older revision		Revision as of 00:43, 16 October 2008
Line 182:		Line 182:
	* You can use IPv6 host part URIs in XSPF v1		* You can use IPv6 host part URIs in XSPF v1
	* You should use a RFC 3986 parser for your XSPF v1 implementation		* You should use a RFC 3986 parser for your XSPF v1 implementation
		+
		+	== <playlist.location> and privacy ==
		+	Saving an absolute file location in ''playlist.location'' as is not a good idea as it has potential to hurt privacy. To give an example this playlist location
		+
		+	<location>file:///home/bob/porn/sountrack/ginawild34.xspf</location>
		+
		+	might reveal information that Bob would have liked to keep private.

	== <playlist.location> vs. xml:base ==		== <playlist.location> vs. xml:base ==

Lucas gonze: add track creator note

2008-09-03T23:05:48Z

add track creator note

← Older revision		Revision as of 23:05, 3 September 2008
Line 9:		Line 9:
	and ''trackNum'' and your XSPF will be fine.		and ''trackNum'' and your XSPF will be fine.

-	== Absolute vs. relative URIs in key ~~attibutes~~ ==	+	== Absolute vs. relative URIs in key attributes ==
	The attributes ''rel'' (<meta> and <link>) and ''application'' (<extension>)		The attributes ''rel'' (<meta> and <link>) and ''application'' (<extension>)
	are by XSPF v1 specification allowed to hold relative URIs. For example this		are by XSPF v1 specification allowed to hold relative URIs. For example this
Line 219:		Line 219:

	Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly. Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well.		Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly. Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well.
		+
		+	== Role of track creator ==
		+
		+	The //playlist/trackList/track/creator element is defined as "name of the entity (author, authors, group, company, etc) that authored the resource." However this leaves ambiguity as to the difference between performer and author. Please note that this element might contain any one of the performer, newsreader, composer, author, etc.

	= Errata =		= Errata =

Sping: /* xml:base */ rewrite

2008-09-02T15:07:48Z

xml:base: rewrite

← Older revision		Revision as of 15:07, 2 September 2008
Line 193:		Line 193:

	=== xml:base ===		=== xml:base ===
-	.. is an xml-wide attribute defined in [http://www.w3.org/TR/xmlbase/ XML Base]. If ''xml:base'' is ~~set it contains~~ the ~~absolute~~ URI ~~that~~ ''~~must~~'' be ~~used to resolve any~~ relative ~~URI from the surrounding XSPF playlist, as~~ an ~~embedded~~ URI ~~has highest priority when resolving relative URIs~~ (~~from [http://xspf.org/xspf-v1.html#rfc.section.6.2 XSPF-1, 6.2 Relative paths], originally~~ from [http://www.w3.org/TR/xmlbase/#rfc2396 XML Base, 4.1]):	+	.. is an xml-wide attribute defined in [http://www.w3.org/TR/xmlbase/ XML Base].
		+	The ''xml:base'' attribute can appear in any element. The Base URI for an element
		+	is computed from ''the stack of xml:base attributes''.
		+	The URI in ''xml:base'' can be relative so you will need an ''external Base URI''
		+	as a ''backup'' (from [http://www.w3.org/TR/xmlbase/#rfc2396 XML Base, 4.1]):

-	# ''The base URI is embedded in the document's content.''	+	# <s>The base URI is embedded in the document's content.</s>
	# The base URI is that of the encapsulating entity (message, document, or none).		# The base URI is that of the encapsulating entity (message, document, or none).
	# The base URI is the URI used to retrieve the entity.		# The base URI is the URI used to retrieve the entity.
	# The base URI is defined by the context of the application.		# The base URI is defined by the context of the application.

-	~~Please note this also includes the ''playlist.location'' element.~~	+	Here is an example of ''xml:base'' in XSPF:
-	~~<BR>~~	+
-	Here is an example of ~~using~~ ''xml:base'' ~~with~~ XSPF:	+

	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
-	<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="~~http~~://~~example~~.~~org~~/~~one~~/">	+	<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="one/">
-	<location>~~two~~</location>~~<!-- Resolves to http://example.org~~/~~one/two -->~~	+	<trackList xml:base="two/">
-	<~~trackList~~ />	+	<track xml:base="../../three/">
		+	<location>four</location>
		+	</track>
		+	</trackList>
	</playlist>		</playlist>
		+
		+	If our ''external Base URI'' would be http://example.org/ the location above would
		+	resolve to http://example.org/three/four.

	Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly. Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well.		Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly. Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well.

Sping: /* xml:base */ Swap two sentences

2008-07-29T19:06:35Z

xml:base: Swap two sentences

← Older revision		Revision as of 19:06, 29 July 2008
Line 210:		Line 210:
	</playlist>		</playlist>

-	Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well~~. Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly~~.	+	Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly. Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well.

	= Errata =		= Errata =

Sping: /* xml:base */ Fix XML comment

2008-07-29T19:01:33Z

xml:base: Fix XML comment

← Older revision		Revision as of 19:01, 29 July 2008
Line 206:		Line 206:
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="http://example.org/one/">		<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="http://example.org/one/">
-	<location>two</location><!-- Resolves to http://example.org/one/two -->	+	<location>two</location><!-- Resolves to http://example.org/one/two -->
	<trackList />		<trackList />
	</playlist>		</playlist>

Sping: /* Notes */ xml:base and playlist.location

2008-07-29T18:55:53Z

Notes: xml:base and playlist.location

← Older revision		Revision as of 18:55, 29 July 2008
Line 182:		Line 182:
	* You can use IPv6 host part URIs in XSPF v1		* You can use IPv6 host part URIs in XSPF v1
	* You should use a RFC 3986 parser for your XSPF v1 implementation		* You should use a RFC 3986 parser for your XSPF v1 implementation
		+
		+	== <playlist.location> vs. xml:base ==
		+
		+	=== playlist.location ===
		+	.. contains the (possibly relative) URI recommended to retrieve the surrounding playlist (or an updated version of it). playlist.location is ''not'' an embedded base URI used to resolve relative URIs, ''[[#xml:base\|xml:base]]'' is. ''playlist.location'' can be thought of as XSPF's counterpart to [http://tools.ietf.org/html/rfc4287 Atom]'s [http://tools.ietf.org/html/rfc4287#section-4.1.1 ''feed.link''] element:
		+
		+	atom:feed elements SHOULD contain one atom:link element with a rel
		+	attribute value of "self". This is the preferred URI for
		+	retrieving Atom Feed Documents representing this Atom feed.
		+
		+	=== xml:base ===
		+	.. is an xml-wide attribute defined in [http://www.w3.org/TR/xmlbase/ XML Base]. If ''xml:base'' is set it contains the absolute URI that ''must'' be used to resolve any relative URI from the surrounding XSPF playlist, as an embedded URI has highest priority when resolving relative URIs (from [http://xspf.org/xspf-v1.html#rfc.section.6.2 XSPF-1, 6.2 Relative paths], originally from [http://www.w3.org/TR/xmlbase/#rfc2396 XML Base, 4.1]):
		+
		+	# ''The base URI is embedded in the document's content.''
		+	# The base URI is that of the encapsulating entity (message, document, or none).
		+	# The base URI is the URI used to retrieve the entity.
		+	# The base URI is defined by the context of the application.
		+
		+	Please note this also includes the ''playlist.location'' element.
		+	<BR>
		+	Here is an example of using ''xml:base'' with XSPF:
		+
		+	<?xml version="1.0" encoding="UTF-8"?>
		+	<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="http://example.org/one/">
		+	<location>two</location><!-- Resolves to http://example.org/one/two -->
		+	<trackList />
		+	</playlist>
		+
		+	Both XSPF-0 and XSPF-1 support the ''xml:base'' attribute and your implementation of XSPF should do as well. Though XML Base is mentioned in the XSPF specification, the ''xml:base'' attribute is not mentioned explicitly.

	= Errata =		= Errata =

Saoshyant at 19:18, 21 December 2007

2007-12-21T19:18:31Z

← Older revision		Revision as of 19:18, 21 December 2007
Line 194:		Line 194:
	It also reads "xspf:playlist elements MAY contain exactly one" which		It also reads "xspf:playlist elements MAY contain exactly one" which
	does not make sense for the content of an element and can be safely ignored.		does not make sense for the content of an element and can be safely ignored.
		+
		+	[[Category:XSPF]]