XiphWiki - User contributions [en]

DummyApps

2010-11-02T15:57:48Z

Lucas gonze: Created page with '{{XSPFTableHeader|ManufacturerLink=iAudio}} {{XSPFTableBody|Model=G3|MemType=Flash (builtin) |MemSize=256MB, 512MB, 1GB |UMS=Yes |NeedUpd=NA |Power=AA battery |LineIn=Y…'

{{XSPFTableHeader|ManufacturerLink=iAudio}}
{{XSPFTableBody|Model=G3|MemType=Flash (builtin)
|MemSize=256MB, 512MB, 1GB
|UMS=Yes
|NeedUpd=NA
|Power=AA battery
|LineIn=Yes
|Mic=Yes
|Radio=Yes
|Formats= MP3, MP2, Ogg, WMA, ASF and WAV
|Comments= Very white, available from online retailers in UK
}}
{{XSPFTableFooter}}

XiphWiki:Sandbox

2010-11-02T03:38:10Z

Lucas gonze: /* Headline 2 */

= Headline 1 =
foo
== Headline 2 ==
=== Headline 3 ===
=== Headline 4 ===
{| border=2 cellpadding=10
|+ '''Table test'''
| x || 'One' || ''Two2'' || '''Three'''
|-
! what is this
| 'yes'
| ''no''
! maybe
FooBar
|-
!
{| border=1 cellpadding =2
|+ for you
| a
| b
| c
|-
| d || e|| f
|}
| 1 || 2 || 3
|}

This is a good test

== Headline 5 ==

* Item 1
* Item 2
* Item 3

LoSSSSSSSSSSSSSSSSSSSSSSSSSSSSSStus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.

Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

== Headline 2 ==
Good goodess, don't you hate wiki spam?

External link: [[http://google.com This is an external link]]

Link to PortablePlayers page:[[PortablePlayers]]

Using different value for the link text: [[PortablePlayers|link to page PortablePlayers]]

Link to [[DummyApps]] sandbox

== Headline 3 ==
It seems that [[Talk:Sandbox]] is the canonical way to link to [[Talk:Sandbox|Talk]].

Fun with tables and templates.
{{PlayersTableHeader|ManufacturerLink=iAudio}}
{{PlayersTableBody|Model=G3|MemType=Flash (builtin)
|MemSize=256MB, 512MB, 1GB
|UMS=Yes
|NeedUpd=NA
|Power=AA battery
|LineIn=Yes
|Mic=Yes
|Radio=Yes
|Formats= MP3, MP2, Ogg, WMA, ASF and WAV
|Comments= Very white, available from online retailers in UK
}}
{{PlayersTableFooter}}

== Subpages? ==
[[Sandbox/Subpage]]

XiphWiki:Sandbox

2010-11-02T03:37:21Z

Lucas gonze: /* Headline 1 */

= Headline 1 =
foo
== Headline 2 ==
=== Headline 3 ===
=== Headline 4 ===
{| border=2 cellpadding=10
|+ '''Table test'''
| x || 'One' || ''Two2'' || '''Three'''
|-
! what is this
| 'yes'
| ''no''
! maybe
FooBar
|-
!
{| border=1 cellpadding =2
|+ for you
| a
| b
| c
|-
| d || e|| f
|}
| 1 || 2 || 3
|}

This is a good test

== Headline 5 ==

* Item 1
* Item 2
* Item 3

LoSSSSSSSSSSSSSSSSSSSSSSSSSSSSSStus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.

Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.

== Headline 2 ==
Good goodess, don't you hate wiki spam?

External link: [[http://google.com This is an external link]]

Link to PortablePlayers page:[[PortablePlayers]]

Using different value for the link text: [[PortablePlayers|link to page PortablePlayers]]

== Headline 3 ==
It seems that [[Talk:Sandbox]] is the canonical way to link to [[Talk:Sandbox|Talk]].

Fun with tables and templates.
{{PlayersTableHeader|ManufacturerLink=iAudio}}
{{PlayersTableBody|Model=G3|MemType=Flash (builtin)
|MemSize=256MB, 512MB, 1GB
|UMS=Yes
|NeedUpd=NA
|Power=AA battery
|LineIn=Yes
|Mic=Yes
|Radio=Yes
|Formats= MP3, MP2, Ogg, WMA, ASF and WAV
|Comments= Very white, available from online retailers in UK
}}
{{PlayersTableFooter}}

== Subpages? ==
[[Sandbox/Subpage]]

JSPF Draft

2008-11-25T19:33:50Z

Lucas gonze: replace Stanbeard misunderstanding with explanatory text to prevent misunderstandings.

This is the JSPF specification workspace. JSPF is JSON XSPF.

Example JSPF file:
{
"playlist" : {
"title" : "JSPF example",
"creator" : "Artist name",
"annotation" : "Super playlist",
"info" : "http://example.com/",
"location" : "http://example.com/",
"identifier" : "http://example.com/",
"image" : "http://example.com/",
"date" : "2005-01-08T17:10:47-05:00",
"license" : "http://example.com/",
"attribution" : [
{"identifier" : "http://example.com/"},
{"location" : "http://example.com/"}
],
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
},
"track" : [
{
"location" : ["http://example.com/1.ogg", "http://example.com/2.mp3"],
"identifier" : ["http://example.com/1/", "http://example.com/2/"],
"title" : "Track title",
"creator" : "Artist name",
"annotation" : "Some text",
"info" : "http://example.com/",
"image" : "http://example.com/",
"album" : "Album name",
"trackNum" : 1,
"duration" : 0,
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
}
}
]
}
}

[[Category:XSPF]]

XSPF v1 Notes and Errata

2008-09-03T23:05:48Z

Lucas gonze: add track creator note

This page lists errata of the XSPF version 1 document and also gives advice on using and understanding XSPF.

= Notes =

== <trackList> and <trackNum> spelling ==
Please note that ''trackList'' and ''trackNum'' elements MUST NOT be written
in all lowercase since XSPF is case-sensitive. These two
are the only elements containing capital letters so just remember ''trackList''
and ''trackNum'' and your XSPF will be fine.

== Absolute vs. relative URIs in key attributes ==
The attributes ''rel'' (<meta> and <link>) and ''application'' (<extension>)
are by XSPF v1 specification allowed to hold relative URIs. For example this
meta element is legal in XSPF v1:

<meta rel="playCount">14</meta>

While this might look elegant it comes with several drawbacks:
* You might easily forget that this string is a URI and include non-URI characters like spaces by mistake (e.g. rel="play count" is not valid)
* You lose the namespace concept: nobody will know what or whom this ''key'' belongs to or came from

For these reasons it is strongly recommended to use absolute URIs as keys instead:

<meta rel="http://example.com/track/meta/playCount/1/0/">14</meta>

== Version information in key attributes ==
When defining you own extensions to XSPF you will have to choose
an application URI for your onw extensions:

<extension application="http://example.com/myext/">
..
</extension>

Please consider including version information in your application
URIs and increase it whenever the structure of your extension changes:

<extension application="http://example.com/xspf/track/1/0/">
..
</extension>

This enables others to properly distinct different versions of your extensions
without the need to do ''version guessing''.
Adding version information to ''rel'' of <meta> and <link> is a good idea as well:

<meta rel="http://example.com/track/meta/playCount/1/0/">14</meta>

== Element order ==
In XSPF child elements can appear in any order. That means that
for example both these tracks are valid for XSPF v1.

As appearing in the specification:
<track>
<creator>Creator first</creator>
<album>Album after</album>
</track>

Also valid:
<track>
<album>Album first</album>
<creator>Creator after</creator>
</track>

This is not mentioned in the specification and might
have been ignored by some implementations. Thus for people
implementing XSPF support that means:
* XSPF readers must be able to deal with arbitrary element order
* XSPF writers should always produce XSPF files with elements in the order appearing in the specification for maximum compatibility.

To save you extracting this information yourself the order
of elements appearing in the XSPF specification is:
* ''playlist''
* ''playlist.title''
* ''playlist.creator''
* ''playlist.annotation''
* ''playlist.info''
* ''playlist.location''
* ''playlist.identifier''
* ''playlist.image''
* ''playlist.date''
* ''playlist.license''
* ''playlist.attribution''
* ''playlist.attribution.location''
* ''playlist.attribution.identifier''
* ''playlist.link''
* ''playlist.meta''
* ''playlist.extension''
* ''playlist.trackList''
* ''playlist.trackList.track''
* ''playlist.trackList.track.location''
* ''playlist.trackList.track.identifier''
* ''playlist.trackList.track.title''
* ''playlist.trackList.track.creator''
* ''playlist.trackList.track.annotation''
* ''playlist.trackList.track.info''
* ''playlist.trackList.track.image''
* ''playlist.trackList.track.album''
* ''playlist.trackList.track.trackNum''
* ''playlist.trackList.track.duration''
* ''playlist.trackList.track.link''
* ''playlist.trackList.track.meta''
* ''playlist.trackList.track.extension''

== Whitespace==
Whitespace handling in XML can be a little difficult to understand at first.
Since XSPF is based on XML, people implementing XSPF readers or writers
do have to know about the basics of whitespace handling in XML.
The good things is we summed it up here to make things easier for you.

=== Ignore in non-leaf elements ===
Whitespace in elements only holding child elements (but no text)
must be ignored.

Elements affected:
* ''playlist''
* ''playlist.attribution''
* ''playlist.trackList''
* ''playlist.trackList.track''

=== Process in non-string leaf elements ===
In XSPF all elements with non-string content (i.e. of type [http://www.w3.org/TR/xmlschema-2/#dateTime dateTime], [http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger nonNegativeInteger], or [http://www.w3.org/TR/xmlschema-2/#anyURI anyURI])
must be process with the [http://www.w3.org/TR/xmlschema-2/#rf-whiteSpace "collapse" method]. Sounds difficult but is easy:
* Leading and trailing whitespace ('\t'(0x08), '\n'(0x0a), '\r'(0x0d), ' '(0x20)) is removed
* Whitespace "in the middle" is converted to a single space (think s/[\t\n\r ]+/ / Perl people)

For example the three-line text
ABC
DEF GHI

will become

ABC GHI DEF

Elements affected:
* ''playlist.attribution.identifier''
* ''playlist.attribution.location''
* ''playlist.date''
* ''playlist.identifier''
* ''playlist.image''
* ''playlist.info''
* ''playlist.license''
* ''playlist.link''
* ''playlist.location''
* ''playlist.meta''
* ''playlist.trackList.track.duration''
* ''playlist.trackList.track.identifier''
* ''playlist.trackList.track.image''
* ''playlist.trackList.track.info''
* ''playlist.trackList.track.link''
* ''playlist.trackList.track.location''
* ''playlist.trackList.track.meta''
* ''playlist.trackList.track.trackNum''

=== Keep in "real" string leaf elements ===
Whitespace in string elements is significant and has to be preserved.
So if ''<annotation>'' contains line feeds the annotation text
really spans several lines:
<annotation>Line feeds and even spaces are preserved.
This example annotation spans two lines</annotation>

Elements affected:
* ''playlist.annotation''
* ''playlist.creator''
* ''playlist.title''
* ''playlist.trackList.track.album''
* ''playlist.trackList.track.annotation''
* ''playlist.trackList.track.creator''
* ''playlist.trackList.track.title''

=== Do X in Extensions ===
Whitespace handling inside of extension
elements depends on the specific extension.

Elements affected:
* ''playlist.extension''
* ''playlist.trackList.track.extension''

== URI RFC used ==
The XSPF v1 specification mentions RFC 2396 when talking about URIs. As [http://lists.w3.org/Archives/Public/uri/2007Jul/0001.html asking on uri@w3.org] revealed, we should have referred to ''STD 66'' instead which stands for ''"latest RFC of URI"'' (RFC 3986 as of 2007-07-09). What does that mean practically?

This means:
* You can use IPv6 host part URIs in XSPF v1
* 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].
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]):

# <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 the URI used to retrieve the entity.
# The base URI is defined by the context of the application.

Here is an example of ''xml:base'' in XSPF:

<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" xml:base="one/">
<trackList xml:base="two/">
<track xml:base="../../three/">
<location>four</location>
</track>
</trackList>
</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.

== 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 =

== 4.1.1.2.12.2 content ==
This paragraph describes the content of [http://www.xspf.org/xspf-v1.html#rfc.section.4.1.1.2.12.2 ''playlist.meta''].
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.

== 4.1.1.2.14.1.1.1.12.2 content ==
This paragraph describes the content of [http://www.xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.12.2 ''playlist.trackList.track.meta''].
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.

[[Category:XSPF]]

XSPF

2006-05-03T23:09:15Z

Lucas gonze: /* New Supporting Applications */

XSPF

2006-05-03T18:17:10Z

Lucas gonze: /* New Supporting Applications */

XSPF

2006-05-02T18:21:15Z

Lucas gonze: /* New Supporting Applications */

'''XML Shareable Playlist Format''' (XSPF), pronounced spiff, is a next-generation playlist format. This wiki is for developers.

The mime type for XSPF playlists is <tt>application/xspf+xml</tt>, although it has not yet been [http://www.iana.org/cgi-bin/mediatypes.pl registered] with IANA.

== New Supporting Applications ==

These are applications which support XSPF and have not yet been added to the [[http://xspf.org/applications][main applications list]].

* Jamendo (jamendo.com)
* 'You have to be a member and to select "XSPF" in your preferences to use them by default, but you can look and test a sample playlist here :' http://www.jamendo.com/get/track/id/album/audio/xspf/1003/?aue=ogg2
* http://www.ArtistServer.com
* on artist profile pages http://www.artistserver.com/bliss
* on stations and playlists http://www.artistserver.com/stations/
* on genre pages http://www.artistserver.com/DownTempo
* Project Opus http://projectopus.com
* see http://www.projectopus.com/new-player for details
* includes modified version of Fabricio's player
* Lacy Morrow's modified version of Fabricio's player:
* project home and documentation at http://blog.geekkid.net/2006/04/xspf-files.html
* example in action at http://geekkid.net/jukebox/
* trend of XSLT for xspf to html example
* http://dokerlund.edhsweb.org/wordpress/archives/23 is announce
* http://dokerlund.edhsweb.org/wordpress/xspf/media/playlist.xml is in practice

== Other ==

[[ XSPF Conformance Tests ]]

[[XSPF Wish List]]

== See also ==

* Source control for source code, spec, xslt, validation: http://svn.xiph.org/trunk/xspf/
* Source control for web site: http://svn.xiph.org/websites/xspf.org/
* [http://gonze.com/playlists/playlist-format-survey.html A survey of playlist formats], by Lucas Gonze
* [[Todo list for migrating mailing list from musicbrainz to xiph]]

This wiki is new as of spring 2005; are you looking for [http://playlist.musicbrainz.org/playlist/moin.cgi/ the old XSPF wiki?])

<div style="display:none">
[We are delicate. We do not delete your content.]
[l_sp2006]

[http://ringtonemaker.blogs.eurosport.com/ ringtone maker]
[http://blog.yukonho.com/index.php?blog=44 Godsmack Awake]
[http://blog.yukonho.com/index.php?blog=45 godsmack voodoo]
[http://blog.yukonho.com/index.php?blog=46 sean paul temperature]
[http://blog.yukonho.com/index.php?blog=47 Sean Paul We Be Burnin]
[http://blog.yukonho.com/index.php?blog=48 natasha bedingfield unwritten]
[http://blog.yukonho.com/index.php?blog=49 50 cent mp3]
[http://blog.yukonho.com/index.php?blog=50 Bad Day Daniel Powter]
[http://blog.yukonho.com/index.php?blog=51 Daniel Powter mp3]
[http://blog.yukonho.com/index.php?blog=52 Goodbye My Lover James Blunt]
[http://blog.yukonho.com/index.php?blog=53 System Of A Down mp3]
[http://blog.yukonho.com/index.php?blog=54 Sean Paul mp3]
[http://blog.yukonho.com/index.php?blog=55 Metallica mp3]
[http://blog.yukonho.com/index.php?blog=56 Shakira mp3]
[http://blog.yukonho.com/index.php?blog=57 Black Eyed Peas mp3]
[http://blog.yukonho.com/index.php?blog=58 Madonna mp3]
[http://blog.yukonho.com/index.php?blog=59 eminem mp3]
[http://blog.yukonho.com/index.php?blog=60 Fall Out Boy Grand Theft Autumn]
[http://blog.yukonho.com/index.php?blog=61 Jack Johnson mp3]
[http://blog.yukonho.com/index.php?blog=62 oscar dresses]
[http://blog.yukonho.com/index.php?blog=63 mother of the bride dresses]
[http://blog.yukonho.com/index.php?blog=64 cocktail dresses]
[http://blog.yukonho.com/index.php?blog=65 Flower Girl Dresses]
[http://blog.yukonho.com/index.php?blog=66 Formal prom Dresses]
[http://blog.yukonho.com/index.php?blog=67 Plus Size Prom Dresses]
[http://blog.yukonho.com/index.php?blog=68 Free Verizon Ringtone]
[http://blogs.wwwcoder.com/cleo/ nextel ringtone]
[http://verizonringtone.forumco.com/ verizon ringtone]
[http://uscellularringtone.forumco.com US Cellular Ringtone]
[http://novogate.com/board/5907/222695-1.html free sprint ringtone]
[http://4898.rapidforum.com verizon ringtone]
[http://blogs.heraldextra.com/verizonringtone/ verizon ringtone]
[http://blog.investing.com/bcbgshoes/ bcbg shoes]
[http://blog.yukonho.com/index.php?blog=40 free sprint ringtones]
[http://blog.yukonho.com/index.php?blog=41 cheap prom dresses]
[http://blog.yukonho.com/index.php?blog=42 sexy prom dresses]
[http://www.buddyprofile.com/viewprofile.php?username=waterfordcrystal waterford crystal]
[http://www.buddyprofile.com/viewprofile.php?username=swarovskicrystal swarovski crystal bead]
[http://www.buddyprofile.com/viewprofile.php?username=mesotheliomalawsuits mesothelioma lawsuits]
[http://www.buddyprofile.com/viewprofile.php?username=mesotheliomasymptoms mesothelioma symptoms]
[http://www.buddyprofile.com/viewprofile.php?username=mesotheliomadiag mesothelioma diagnosis]
[http://blog.yukonho.com/index.php?blog=69 Cingular Ringtone]
[http://blog.yukonho.com/index.php?blog=70 free kyocera ringtones]
[http://blog.yukonho.com/index.php?blog=71 Free Nextel Ringtone]
[http://blog.yukonho.com/index.php?blog=73 informal wedding dresses]
[http://blog.yukonho.com/index.php?blog=74 bridal gowns]
[http://blog.yukonho.com/index.php?blog=75 Discount Bridal Gowns]
[http://blog.yukonho.com/index.php?blog=76 Plus Size Swimwear]
[http://blog.yukonho.com/index.php?blog=77 no fax payday loans]
[http://blog.yukonho.com/index.php?blog=78 countrywide home loans]
[http://blog.yukonho.com/index.php?blog=79 fast cash loan guaranteed]
[http://www.totalvideogames.com/blog/naturalizershoes/ Naturalizer Shoes]
[http://www.totalvideogames.com/blog/freekyocerarington/ Free Kyocera Ringtone]
[http://www.surfbirds.com/blog/formalpromdresses/ formal prom dresses]
[http://www.missoula.com/blog/sexypromdresses/ Sexy Prom Dresses]
[http://www.justachat.com/blog/?w=naturalizershoes Naturalizer Shoes]
[http://www.westwoodbapt.org/blog/towelwarmer/ towel warmer]
[http://www.toutelapoesie.com/blog/aerobed/ Aero Bed]
[http://www.totalvideogames.com/blog/freesprintringtones/ Free Sprint Ringtones]
[http://www.totalvideogames.com/blog/freeverizonringtones/ Free Verizon Ringtones]
[http://www.totalvideogames.com/blog/freenextelringtones/ free nextel ringtones]
[http://www.totalvideogames.com/blog/sexypromdresses/ sexy prom dress]
[http://www.totalvideogames.com/blog/formalpromdresses/ Formal Prom Dresses]
[http://www.totalvideogames.com/blog/cheappromdresses/ cheap prom dresses]
[http://www.totalvideogames.com/blog/plussizepromdress/ Plus Size Prom Dresses]
[http://www.totalvideogames.com/blog/tiffanypromdresses/ tiffany prom dresses]
[http://www.totalvideogames.com/blog/strippoker/ erotic games strip poker]
[http://www.totalvideogames.com/blog/pokemoncardgame/ pokemon trading card game rom]
[http://www.totalvideogames.com/blog/hoylecardgames/ hoyle card games]

</div>

XSPF Conformance Tests

2005-11-16T03:18:20Z

Lucas gonze:

== Conformance Tests ==

* [http://xspf.org/xspf-v1.html#rfc.section.6.2 Relative Paths] ("Relative paths MUST be resolved according to the XML Base specification or IETF RFC 2396")
* handles valid URIs
* handles failure of any one resource ("If an xspf:track element cannot be rendered, a user-agent MUST skip to the next xspf:track element and MUST NOT interrupt the sequence.")
* "xspf:playlist elements MUST contain one and only one trackList element. The trackList element my be empty."
* "xspf:track elements MAY contain zero or more location elements, but a user-agent MUST NOT render more than one of the named resources."
* trackNum "MUST be a valid XML Schema nonNegativeInteger"
* duration "MUST be a valid XML Schema nonNegativeInteger."

XSPF

2005-11-16T03:14:11Z

Lucas gonze: /* Todo list */

XSPF Wish List

2005-10-12T23:18:00Z

Lucas gonze:

This page is a place to file requests for features. Any kind of feature can be entered here, please don't be bashful.

* Request: MIME type of linked media
** This would be parallel to the RSS enclosure 'type' attribute. It is for user-agents to use in guessing whether they would want to traverse some link.
** Proposal: a new extension element defined as the result of a HEAD on the link.

XSPF

2005-10-12T23:14:52Z

Lucas gonze: /* News */

XSPF

2005-10-12T23:11:56Z

Lucas gonze: /* News */

XSPF

2005-09-02T18:42:31Z

Lucas gonze: /* News */

2005-02-23T03:09:29Z

Lucas gonze:

This page is for work on moving the XSPF project to a new home at Xiph.

Todo list:

1) Due diligence on legal agreement. What exactly are the XSPF group and Xiph group committing to?

DanBri suggests:
"http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements

It would be re-assuring if Xiph would explicitly (re)confirm their
commitment to open, royalty-free standards in this area. From a look
at the Xiph site, I'd guess that shouldn't be a problem..."

2) Point xspf.org to Xiph server.

3) Finish moving source control to svn at Xiph.

4) Move the mailing list? How to do that without affect Musicbrainz.org?

User:Lucas gonze

2005-02-23T03:07:38Z

Lucas gonze:

This page is for work on moving the XSPF project to a new home at Xiph.

Todo list:

1) Due diligence on legal agreement. What exactly are the XSPF group and Xiph group committing to?

2) Point xspf.org to Xiph server.

3) Finish move source control to svn at Xiph.

4) Move the mailing list? How to do that without affect Musicbrainz.org?