www.archive-org-2013.com » ORG » X » XSPF

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 14 . Archive date: 2013-02.

  • Title: XSPF: XML Shareable Playlist Format: Home
    Descriptive info: .. Xiph.. org.. Vorbis.. Theora.. Icecast.. Speex.. Opus.. FLAC.. XSPF.. Home.. Quick Start.. Specification.. Validation.. Applications.. Mailing List.. Wiki.. About Us.. XSPF Home.. XSPF is the XML format for sharing playlists.. It is.. free.. and.. open.. -- No proprietary lock-in.. portable.. -- You should be able to send a  ...   Most playlist formats get the easy things wrong.. Unlike M3U.. XSPF is XML.. Unlike SMIL.. XSPF is simple.. Unlike ASX.. XSPF is open.. The Xiph OSC and XSPF logos are trademarks ( ) of Xiph.. Org.. These pages 1994 - 2007 Xiph.. All rights reserved.. Last Modified:.. Validate.. XHTML.. CSS..

    Original link path: /
    Open archive

  • Title: XSPF: XML Shareable Playlist Format: Quick Start
    Descriptive info: XSPF: XML Shareable Playlist Format: Quick Start.. Quick Start Guide.. This document is a guide for people just encountering XSPF for the first time.. What is XSPF?.. A playlist format like M3U.. XML like RSS.. Pronounced.. spiff.. MIME type.. application/xspf+xml.. What does XSPF look like?.. A very simple document looks like this:.. ?xml version="1.. 0" encoding="UTF-8"? playlist version="1" xmlns="http://xspf.. org/ns/0/" trackList track location file:///mp3s/song_1.. mp3 /location /track track location file:///mp3s/song_2.. mp3 /location /track track location file:///mp3s/song_3.. mp3 /location /track /trackList /playlist.. Notice that the file names are.. URIs.. , meaning that you could pass them to a web browser.. Also notice that it's.. track.. L.. ist.. , with an uppercase.. , not.. l.. , with a lowercase.. The following playlist is just the same except that the files are out on the web:.. org/ns/0/" trackList track location.. http://.. example.. com/song_1.. mp3 /location /track track location.. com/song_2.. com/song_3.. MIME type.. The MIME type for XSPF documents is.. NOT..  ...   the playlist, like the title, the name of the author, and the homepage of the author?.. org/ns/0/" !-- title of the playlist --.. title 80s Music /title.. !-- name of the author --.. creator Jane Doe /creator.. !-- homepage of the author --.. info http://example.. com/~jane /info.. trackList track location http://example.. For a song in a playlist, how do I set metadata like the name of the artist and title of the album?.. mp3 /location !-- artist or band name --.. creator Led Zeppelin /creator.. !-- album title --.. album Houses of the Holy /album.. !-- name of the song --.. title No Quarter /title.. !-- comment on the song --.. annotation I love this song /annotation.. !-- song length, in milliseconds --.. duration 271066 /duration.. !-- album art --.. image http://images.. amazon.. com/images/P/B000002J0B.. 01.. MZZZZZZZ.. jpg /image.. !-- if this is a deep link, URL of the original web page --.. com /info.. /track /trackList /playlist..

    Original link path: /quickstart/
    Open archive

  • Title: XSPF: XML Shareable Playlist Format: Specifications
    Descriptive info: XSPF: XML Shareable Playlist Format: Specifications.. Specifications.. Unless you have a specific reason otherwise, the following is the One True Spec:.. XSPF version 1.. (November, 2006).. For historical reasons, you may find the following two versions of the spec useful.. Specification for XSPF version 0.. (May,  ...   between version 0 and version 1.. trackList.. may be empty.. extension.. added.. date.. changed from ISO 8601 to xsd:dateTime.. version.. incremented.. See also.. XSPF v1 Notes and Errata.. Because it is easy to make mistakes, those who create XSPF documents should check their output against.. a validator..

    Original link path: /specs/
    Open archive
  •  

  • Title: XSPF: XML Shareable Playlist Format: Validation
    Descriptive info: XSPF: XML Shareable Playlist Format: Validation.. If you are generating XSPF, your playlist should be valid according to one of the tools listed below.. This is crucial for interoperability.. Please take it seriously, despite the inconvenience.. Online XSPF validator.. by Sebastian Pipping.. Relax NG (XML) Schema for XSPF-1.. by Matthias Friedrich.. Sample usage of.. XMLStarlet.. :.. (Unix) xmlstarlet validate -e -r xspf-1_0.. 7.. rng myplaylist.. xspf (Windows) xml.. exe validate -e -r xspf-1_0.. xspf.. There also exists a schema for.. XSPF-0.. , but working with XSPF-1 should be preferred.. Relax  ...   of xspf_check:.. (Unix) cat myplaylist.. xspf | xspf_check - (Windows) xspf_check - myplaylist.. XML Schema for XSPF.. (Unix) xmlstarlet validate -e -s xspf-1_0.. 2.. xsd myplaylist.. exe validate -e -s xspf-1_0.. Note: The above XML Schema (XSD) is not fully spec compliant and therefore.. deprecated.. Please use the Relax NG schema instead if you can.. Since the XSD schema language is not powerful enough to express the XSPF specification there will never be a correct XSD schema for XSPF.. Please see the mailing list archive for the discussion on this topic..

    Original link path: /validation/
    Open archive

  • Title: XSPF: XML Shareable Playlist Format: Applications
    Descriptive info: XSPF: XML Shareable Playlist Format: Applications.. Programs.. Amarok.. (Unix).. A feature-rich, library-oriented music player for Unix systems.. Ampache.. According to the site, Ampache is.. a PHP-based tool for managing, updating and playing your MP3/OGG/RM/FLAC/WMA/M4A files via a web interface.. It allows you to save playlists, create user accounts, and share your music catalogs with other Ampache servers.. Armangil's podcatcher (Unix).. A podcast client for the command line which supports XSPF enclosures.. Audacious.. A media player for Unix systems.. Audacious is a fork of the Beep Media Player and therefore also descendant of XMMS.. BMPx.. (GNU/Linux).. A media player for GNU/Linux systems.. A rewrite of.. BMP.. , a compact media player that was originally forked from XMMS (http://www.. xmms.. org) with the goal of porting XMMS to GTK2 and make use of more modern desktop standards.. ccHost.. (web-based system supporting remixing and collaboration on media).. ccHost is an open source (GPL licensed) project that provides web-based infrastructure (PHP) to support collaboration, sharing, and storage of multi-media using the Creative Commons licenses and metadata.. It is the codebase used by.. ccMixter.. and other sites.. Since version 3.. 0 cchost supports XSPF 1.. 0 (see.. release notes 3.. 0.. ).. Cruxy Second-Life player.. (Second-Life XSPF player).. Cruxy Player for Second Life is a portable music player for use at listening parties, as a promotional giveaway, or for just some relaxing downtime in your personal parcel of land.. It can load and play music from mp3 playlists using the XSPF standard.. To provide maximum opportunity for creativity, the player is being released open-source, under the GNU General Public License.. Drupal playlist module.. (blog/web publishing).. The playlist module allows [publishers] to arrange content into personal playlists.. This module empowers users to become organizers of content as they re-order content from the site and create lists of their favorite content items.. See also:.. Audio and Playlist Modules for Drupal.. Drupal playlist demo page.. Easy Musicplayer For Flash.. Skinnable Flash MP3 player.. See here for the.. full list of features.. FMP3 Flash XSPF Player.. A Flash-based application for playing music in web pages.. Under.. Creative Commons Attribution-NonCommercial-NoDerivs 2.. 5 license.. , with additional conditions.. foo_xspf.. (Windows, Foobar2000).. Adds XSPF read and write support to.. Foobar2000.. Gnomoradio.. A program that can find, fetch, share, and play music that is freely available for file sharing.. Herrie.. Herrie is a minimalistic music player that uses the command line.. It is written to support a variety of operating systems, audio subsystems and file formats, including playlists.. I/ON.. (Java, runs on MacOS X and Windows XP).. A media player oriented towards internet based content rather than locally stored content.. Support for video formats like Quicktime, Windows Media, Flash, Ogg and MPEG formats; RSS/podcasts; BitTorrent.. Makes available.. Java source for XSPF support based on JDOM.. Jeroen Wijering's Flash MP3 Player.. Distinguished by an appealing look design, configurable behavior and appearance, and a Javascript/Actionscript API.. Attribution-NonCommercial-ShareAlike 2.. 0 license.. Joint Radio.. A distributed playlist aggregator.. It takes RSS bookmark feeds from a social bookmarking service (del.. icio.. us currently tested) and creates a playlist (XSPF, but that's not important here).. Further, members can aggregate other user's playlists into a master playlist or use the whole site playlist.. Jukes.. A cross platform MP3 player and organizer written in Java that uses XSPF as its playlist format.. m3u2xspf.. A tool for converting M3U playlists to XSPF.. This is a console tool written in Python, so for a Unix-like environment.. It is free software under the Gnu GPL.. Musicmobs / Mobster (OS X and Windows).. Playlist publication community and XSPF content resolver.. Mobster creates iTunes playlists based on XSPF metadata by searching the local music collection for available tracks.. The focus is on portability since the file location is ignored.. Musicmobs acts as a playlist trading community by accepting XSPFs from Mobster or manual upload.. Musicplayer.. (web).. Open source under the BSD license; can be used and modified by anyone, including for commercial purposes.. Very popular both in its own right and as a source for derived applications.. Ning.. (web development framework).. A hosted software development framework for web applications.. The XSPF module allows applications to edit, parse, and publish XSPF documents.. Paul Lamere's playlist resolver.. An experimental playlist resolver which will look at the track information and attempt to find information about the track at MusicBrainz, and fix or augment this information.. PHP XSPF Playlist Generator.. A PHP script that reads the contents of a folder containing MP3s, reads the ID3 tags and outputs an XSPF playlist.. It means you just have to upload your files into a folder and then the playlist is generated automatically.. Plait command line jukebox.. A script that creates playlists from a music library and submits the playlists to music players.. Now includes an XSPF publishing feature which creates a complete web site including an XSPF playlist, a web page that embeds the XSPF Web Music Player, and MP3 files.. Plext.. (Windows, Winamp).. Winamp plugin for  ...   streaming.. earfl.. Website allowing you to record and host audio stories and slideshows, and make them available in XSPF.. feedpixel.. a free online feed reader and podcast player service.. Foafing the music.. A music recommendation system, based on user's profile.. Uses the.. FOAF.. vocabulary to recommend music.. Looks promising, but seems to be in an experimental phase at this moment.. Grabb.. it.. An online music player that will create playlists for any web page that links to music files.. You can remember, download, and share the songs you find.. iLike.. A music site oriented towards social-networks; for sharing music tastes and playlists, and learning about new artists and concerts together.. Internet Archive Netlabels.. hosts complete, freely downloadable/streamable, often Creative Commons-licensed catalogs of 'virtual record labels'.. Jamendo.. A repository of artists and music that allows users to create XSPF playlists.. Jinzora.. A web based media streaming and management system, designed to stream audio and video files to any internet connected computer.. Last.. fm / Audioscrobbler.. A listener community grown out of Audioscrobbler.. Listeners send information about each track they play to Last.. fm.. That way Last.. fm can build statistics about your music habits and make suggestions for music you might want to check out in the future.. Magnatune.. A "non-evil" record label offering free downloads of all their albums.. You can.. try before you buy.. : Listen to 128KB/s MP3s for free or buy a higher quality (or even lossless) version if you like it.. 50% go directly to the artist.. More details.. here.. Music for Dozens.. (web site; Flash player).. Pay-per-download no-DRM music store emphasizing independent artists.. Sample songs use custom Flash player which accepts XSPF.. Myplaylist.. combines relevant images into a music slideshow playlist.. Myplaylist lyrics.. combines music slideshows with accompanying lyrics.. These mashups combine content (Flickr / Seeqpod) which is then reformulated and made available via the Myplaylist.. API.. MyStrands.. A music-oriented social site focused on taste-sharing and recommendations.. Odeo.. A directory of online audio.. playlistar.. Browser-based playlist manager for audio files you find while wandering through the halls of music - crosslink tracks you find into your account and listen to them at your leisure from anywhere.. Playr.. A web-based tool for screen-scraping web pages and emitting the results as a playlist.. Says Playr creator Alf Eaton:.. There's a Flash/XSPF bookmarklet on the front page -- which you can use to directly play any page containing linked MP3s -- as well as 'Flash' links on the New Playlists page.. Plurn.. A web-based playlist community modeled after Webjay.. Project Opus.. A music community site which makes playlists available in XSPF.. Seeqpod Playabale Search.. Audio and video search engine with online playlists.. XSPF is used in the.. SeeqPod REST API.. ultraPh0nZ FMP256.. A Flash application for playing music in web pages.. Skinnable and slick.. Webjay.. A playlist community site and playlist authoring tool which exports XSPF playlists.. Tools.. fspiff.. Command line tool to produce an XSPF playlist from M3U or a list of filenames.. xspf-download-0.. 1.. py.. A Python script that parses XSPF and M3U files and downloads the files to the local harddrive.. PHP.. Generates XSPF playlists from MP3 tags.. XSPF playlist generator.. Live playlist editor/generator implemented in JavaScript.. XSPF to JSPF Parser.. (Javascript).. Converts your XSPF files to.. JSPF.. ("XSPF on JSON") online.. XSPF Validator.. Online validator for XSPF documents.. Libraries.. cl-xspf.. (Common Lisp).. A Common Lisp API for writing XSPF playlists.. haXe XSPF.. (.. haXe.. XSPF support for haXe web applications.. JSpiff.. (Java).. JSpiff is a Java API for reading and writing XSPF ("Spiff") open XML playlists using JAXP or JAXB.. libxspf.. (C, C++).. The official reference implementation of XSPF by the Xiph.. Org Foundation.. libxspf (formerly called libSpiff) is a cross-platform C++ library for reading and writing XSPF playlist files (both Version 0 and 1).. It is licensed under the New BSD license.. See also.. libxspf tutorial.. Lizzy.. Java library and tools allowing to parse, create, edit, convert and save almost any kind of multimedia playlist.. Amongst other formats, XSPF is of course supported.. PEAR :: Package :: File_XSPF.. (PHP).. PHP library for parsing and generating XSPF.. Ruby XSPF playlist class.. (Ruby).. A Ruby library to parse XML Shareable Playlist Format (XSPF) documents and export them to M3U, SMIL, HTML and SoundBlox.. License: GNU General Public License (GPL) version 2, Ruby License.. XML::XSPF on CPAN.. (Perl).. Perl library for parsing and generating XSPF.. toJSPF().. (JavaScript).. toJSPF() is a function for parsing XSPF in Javascript.. The resulting Javascript object is easy to use and manipulate to create client-side playlist browsers and media players.. The parsed result can also easily be serialized into JSON for easy server-client transport.. This allows developers to use one player for handling both XML XSPF and JSON JSPF playlists provided by the server.. XSPF4PHP.. Set of classes for creating XSPF files from PHP.. Note to application developers: to be included here, write your entry in the format above and email it to.. the XSPF mailing list..

    Original link path: /applications/
    Open archive

  • Title: XSPF: XML Shareable Playlist Format: About Us
    Descriptive info: XSPF: XML Shareable Playlist Format: About Us.. Our group started work in February 2004, achieved rough consensus on version 0 in April 2004, did implementations and fine tuning throughout summer and fall 2004, and declared the tuned version to be version 1 in January 2005.. During the spring of 2005 we settled into a permanent home at.. Between August and November of 2006 we unfroze the version 1 document for a final round of improvements to the drafting and formatting, limiting changes to those which did not require any implementation to be modified.. Ian C.. Rogers and Robert Kaye bootstrapped our project.. Dave Brown, Dan Brickley, and Kevin Marks  ...   web resources like the applications and extensions directories.. Lucas Gonze, Matthias Friedrich, and Robert Kaye authored the specification documents.. We are grateful for comments and feedback from Ryan Shaw, Alf Eaton, Steve Gedikian, Russell Garrett, Ben Tesch and Pau Garcia i Quiles.. Special thanks to the developers Tomas Franzén (who participated in our work from the very beginning), Jim Garrison, Brander Lien, Fabricio Zuardi and to everyone who contributed their time and skill on the mailing list and wiki.. We are grateful to the Metabrainz foundation for their continuing generosity.. We are in awe of Fabricio Zuardi, who popularized the format by creating.. a player.. which became a runaway hit..

    Original link path: /aboutus/
    Open archive

  • Title: XSPF Version 1
    Descriptive info: TOC.. Playlist Ad-Hoc Group.. Gonze.. M.. Friedrich.. R.. Kaye.. November 2006.. Version 1.. XML Shareable Playlist Format ("spiff").. Abstract.. We describe an.. XML.. playlist format which is open, moderately simple, and carefully engineered.. Table of Contents.. 1.. Introduction.. 1.. 1.. Example.. 2.. Administration.. 2.. History.. 2.. Acknowledgements.. 3.. terminology.. 3.. URI, URLs and URNs.. Requirements notation.. 3.. Abstractions.. 3.. Defining playlists.. What a playlist is not.. Shareability.. 4.. Content resolver.. 5.. Fuzzy names.. 4.. Element definitions.. 4.. elements.. playlist.. attributes.. xmlns.. title.. creator.. annotation.. info.. location.. 6.. identifier.. 7.. image.. 8.. 9.. license.. 10.. attribution.. 11.. link.. 11.. rel.. content.. 12.. meta.. 12.. 13.. 13.. application.. 14.. 14.. album.. trackNum.. duration.. 5.. Requirements for XSPF generators.. 6.. Requirements for XSPF players.. 6.. Graceful failure.. Relative paths.. Extension URIs.. References.. Author's Addresses.. Copyright and Patent Statements.. There is no XML format for playlists that can measure up to the standards of the formats for web pages (.. HTML.. ), weblogs (.. RSS.. /Atom), and web graphs (.. RDF.. /XML).. It is evident that there is a need, because XML is the preferred data description language of the moment and as a result the tools and skills to use it are ubiquitous.. It is also evident that existing playlist formats fall short.. ASX.. (for Windows Media Player) and the iTunes library format are proprietary.. ASX resembles XML in that it uses angle brackets, but is not XML by any means.. M3U.. , RAM, and M4U are flat files; QuickTime is binary; Pls is in the Windows.. ini format; Gnomoradio RDF is RDF, not XML.. SMIL.. addresses a much larger problem space than the average digital music player.. The timing model of RSS is incompatible with playlists.. Few of these formats are well documented.. None of these formats make simple features easy to code and hard features possible.. Only one is an open standard.. Not one offers playlist interoperability across major vendors.. The question for software developers is.. why should I support this new XML playlist format.. ? The choice is between M3U and SMIL.. Almost every digital music player accepts M3U but also invents an XML playlist format.. Inventing a format creates work, for example to study related formats; you should use XSPF to avoid the work.. SMIL, on the other hand, is a prescription for a kind of application that is different from a typical music player it describes layouts in time, while XSPF describes concepts common among music players.. Given a song with the comment "danceable!", SMIL might have an instruction to write that text in the upper left in a bold sans-serif font, while XSPF would tell a player that the text is a comment and say nothing about formatting.. 0" encoding="UTF-8"?> playlist version="1" xmlns="http://xspf.. org/ns/0/"> trackList> track> location>file:///music/song_1.. ogg /location> /track> track> location>file:///music/song_2.. flac /location> /track> track> location>file:///music/song_3.. mp3 /location> /track> /trackList> /playlist>.. or this:.. net/song_1.. ogg /location /track track location http://example.. net/song_2.. flac /location /track track location http://example.. Between August and November of 2006 we unfroze this document for a final round of improvements to the drafting, limiting changes to those which did not require any implementation to be modified.. Special thanks to the developers Tomas Franzén (who participated in our work from the very beginning), Jim Garrison, Brander Lien, and Fabricio Zuardi, and to everyone who contributed their time and skill on the mailing list and wiki.. We would especially like to thank our hosts at the the Xiph.. org foundation and Metabrainz foundation for their continuing generosity.. URI.. URL.. s and.. URN.. s.. We use the term.. in this document regardless of whether a given URI specifies the location of a resource (a URL) or its name (a URN) independent of location.. RFC2396bis.. ;.. URIs, URLs, and URNs: Clarifications and Recommendations 1.. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in.. [RFC2119].. An XSPF playlist describes a sequence of objects to be rendered.. Objects might be audio, video, text, playlists, or any other media type.. The function of a playlist is to identify the objects and communicate their order.. The function of a playlist.. is not.. to communicate metadata about the composer, song title, etc.. Metadata is hard and there are many providers already.. We decided that we couldn't compete, and that there was no need for us to try.. Moreover, good metadata does not travel well every user has to recreate it.. Metadata should come from external sources and namespaces like MusicBrainz or Gracenote; this what the XSPF.. elements are for.. to store derived information about objects that a user has a copy of.. A playlist is not a catalog.. A catalog is computed across hard data like files; it stores information like filesystem paths and the contents of ID3 tags.. This data has no value on any machine but the one on which it originated.. Sharing this data would be a privacy and security violation.. Software which needs access to this data has no reason to maintain it in a standard format, because it has no reason to allow access to it.. Standardizing this data would be fruitless, because there are an endless number of measurements that software might take and store.. Derived information belongs in a.. catalog.. Things a playlist is not, then, are a metadata format or a catalog.. We took care to enable these features, but also to avoid duplicating their functionality, poorly.. If there is no reason for a playlist to be shared, there is no need for a new format.. Even a buggy format does no damage if it is created and consumed by the same software on the same machine.. The need for a new format only comes up when  ...   zero or one license element.. 10.. An ordered list of URIs.. The purpose is to satisfy licenses allowing modification but requiring attribution.. If you modify such a playlist, move its //playlist/location or //playlist/identifier element to the top of the items in the //playlist/attribution element.. xspf:playlist elements MAY contain exactly one xspf:attribution element.. Such a list can grow without limit, so as a practical matter we suggest deleting ancestors more than ten generations back.. attribution location http://bar.. com/modified_version_of_original_playlist.. xspf /location identifier somescheme:original_playlist.. xspf /identifier /attribution.. The link element allows XSPF to be extended without the use of XML namespaces.. xspf:playlist elements MAY contain zero or more link elements.. link rel="http://foaf.. example.. org/namespace/version1" http://socialnetwork.. org/foaf/mary.. rdfs /link.. URI of a resource type.. URI of a resource.. The meta element allows metadata fields to be added to XSPF.. xspf:playlist elements MAY contain zero or more meta elements.. meta rel="http://example.. org/key" value /meta.. URI of a resource defining the metadata.. Value of the metadata element.. This is plain old text, not XML, and it may not contain markup.. The extension element allows non-XSPF XML to be included in XSPF documents.. The purpose is to allow nested XML, which the meta and link elements do not.. xspf:playlist elements MAY contain zero or more extension elements.. playlist version="1" xmlns="http://xspf.. org/ns/0/" xmlns:cl="http://example.. com" extension application="http://example.. com" cl:clip start="25000" end="34500"/ /extension trackList / /playlist.. URI of a resource defining the structure and purpose of the nested XML.. nested XML.. Ordered list of xspf:track elements to be rendered.. The sequence is a hint, not a requirement; renderers are advised to play tracks from top to bottom unless there is an indication otherwise.. 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.. URI of resource to be rendered.. Probably an audio resource, but MAY be any type of resource with a well-known duration, such as video, a SMIL document, or an XSPF document.. The duration of the resource defined in this element defines the duration of rendering.. xspf:track elements MAY contain zero or more location elements, but a user-agent MUST NOT render more than one of the named resources.. Canonical ID for this resource.. Likely to be a hash or other location-independent name, such as a MusicBrainz identifier.. xspf:track elements MAY contain zero or more identifier elements.. For example, the URI.. http://musicbrainz.. org/track/7e1d6f5f-0ac3-4889-8b57-506a67b459fc.. html.. is an identifier for a specific song, but dereferencing that identifier will not yield a copy of the song.. Human-readable name of the track that authored the resource which defines the duration of track rendering.. This value is primarily for fuzzy lookups, though a user-agent may display it.. xspf:track elements MAY contain exactly one.. Human-readable name of the entity (author, authors, group, company, etc) that authored the resource which defines the duration of track rendering.. A human-readable comment on the track.. URI of a place where this resource can be bought or more info can be found.. URI of an image to display for the duration of the track.. Human-readable name of the collection from which the resource which defines the duration of track rendering comes.. For a song originally published as a part of a CD or LP, this would be the title of the original release.. Integer with value greater than zero giving the ordinal position of the media on the xspf:album.. It MUST be a valid.. XML Schema nonNegativeInteger.. The time to render a resource, in milliseconds.. This value is only a hint different XSPF generators will generate slightly different values.. A user-agent MUST NOT use this value to determine the rendering duration, since the data will likely be low quality.. xspf:track elements MAY contain exactly one duration element.. xspf:track elements MAY contain zero or more link elements.. The meta element allows metadata fields to be added to xspf:track elements.. xspf:track elements MAY contain zero or more meta elements.. xspf:track elements MAY contain zero or more extension elements.. com" trackList track extension application="http://example.. com" cl:clip start="25000" end="34500"/ /extension /track /trackList /playlist.. 5.. To ensure interoperability, conforming applications MUST generate playlists that follow the definitions listed in section 4 (element descriptions).. If a media player is unable to render a track in the sequence, the player MUST NOT stop rendering the sequence and MUST attempt to continue at the next track.. Players will frequently encounter resources that they cannot render this is not a fatal error unless the player stops processing the playlist.. Relative paths MUST be resolved according to the.. XML Base.. specification or.. IETF.. RFC.. 2396.. :.. The rules for determining the base URI can be be summarized as follows (highest priority to lowest): 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.. Generators should take extra care to ensure that relative paths are correctly encoded.. Do:.. location>My%20Song.. flac /location>.. Don t:.. location>My Song.. Applications MUST assign unique URIs from their own namespace for each link, meta and extension element.. New URIs SHOULD be assigned if syntax and/or semantics of a link, meta or extension element changes.. Bradner, S.. , ".. Key words for use in RFCs to Indicate Requirement Levels.. ", BCP14, RFC2119, March1997.. Lucas Gonze.. E-mail:.. Matthias Friedrich.. Robert Kaye.. rob@eorbit.. net.. Copyright Xiph.. org Foundation 2005.. The primary author of this work is.. He knows of no patent claims related to this work, and hereby forgoes any such claims with regard to his own contributions.. This work is licensed under a.. Creative Commons Attribution-NoDerivs 2.. 5 License..

    Original link path: /xspf-v1.html
    Open archive

  • Title: The XSPF Playlist Format, version 0
    Descriptive info: The XSPF Playlist Format, version 0.. There is no XML format for playlists that can measure up to the standards of the formats for web pages (HTML), weblogs (RSS), and web graphs (RDF/XML).. ASX (for Windows Media Player) and the iTunes library format are proprietary.. M3U, RAM, and M4U are flat files; QuickTime is binary; Pls is in the Windows.. SMIL is too hard to implement.. The timing model of RSS doesn't fit audio and video.. Forcing timing models into HTML, as HTML+Time does, creates an unintelligible feature set.. Not a single one offers interoperability across major vendors.. Not a single one attempts to solve these problems.. The pressing question for software developers is.. why should I support this XML playlist format.. instead of or in addition to ASX, SMIL, Gnomoradio RDF, iTunes XML, or RSS? Why does the world need yet another XML playlist format? The answer is.. XSPF is by far the most carefully crafted XML playlist format.. A very simple document looks like this:.. 0" encoding="UTF-8"? playlist version="0" xmlns = "http://xspf.. org/ns/0/" trackList track location file:///mp3s/Yo%20La%20Tengo/1_Nuclear%20War%20Version%201.. mp3 /location /track track location file:///mp3s/Yo%20La%20Tengo/2_Nuclear%20War%20Version%202.. mp3 /location /track track location file:///mp3s/Yo%20La%20Tengo/3_Nuclear%20War%20Version%203.. mp3 /location /track track location file:///mp3s/Yo%20La%20Tengo/4_Nuclear%20War%20Version%204 /location /track track location file:///mp3s/Yo%20La%20Tengo/5_Nuclear%20War%20Version%204%20(Mike%20Ladd%20Remix).. or this:.. org/ns/0/" trackList track location http://yolatengo.. com/1_Nuclear%20War%20Version%201.. mp3 /location /track track location http://yolatengo.. com/2_Nuclear%20War%20Version%202.. com/3_Nuclear%20War%20Version%203.. com/4_Nuclear%20War%20Version%204 /location /track track location http://yolatengo.. com/5_Nuclear%20War%20Version%204%20(Mike%20Ladd%20Remix).. Administrative notes.. xml.. encoding.. Design and architecture.. Usecases for playlists.. Flag player application.. Allow streaming.. Collecting fragmented resources.. Alternate media types.. Caching derived info.. Metadata storage.. Authoring compilations for expressive reasons.. Recipes.. How do I set relative paths in an XSPF playlist, for example if I want to use it as a file manifest?.. How to I convert XSPF to M3U?.. How to I convert XSPF to HTML?.. How to I convert XSPF to SMIL?.. How to I convert XSPF to Soundblox?.. How do I customize XSPF? Should I use namespaces?.. How do I validate XSPF?.. How do I use MusicBrainz metadata?.. How do I refer to a BitTorrent?.. How do I refer to a Magnet or sha1: URI?.. Administrative.. Validate.. Version 0 is frozen and complete.. Anybody writing code according to this specification can be very confident that it will not change.. The home of our working group is.. Members include Dave Brown and Ian Rogers of Yahoo; Dan Brickley from the W3C; Kevin Marks of Technorati; Matthias Freidrich and Robert Kaye of MusicBrainz; Ryan Shaw of UC Berkely; and myself, from Webjay.. This author of this document is.. Our group started work in the winter of 2004.. The first public draft of this document was May 9, 2004, the most recent was January 6, 2005.. In a few places in this document I will use the term MUST in all caps, which will remind some readers of formal standards.. In this document the term should be interpreted to mean that something shouted is important.. XSPF is not a standard, it is an ad-hoc project by a group of individuals.. Moreover, good metadata does not travel well -- every user has to recreate it.. It is common for playlists created with one application to not be usable by another application on the same machine because of different or conflicting interpretations of the playlist format.. Audio and video objects are often abstractions like "movie X by director Y" rather than computer-friendly objects like "whatever file can be gotten from the URL http://foo/x/y".. utf-8 recommended to allow unicode characters in text fields.. 0.. A human-readable comment on the playlist in text/plain format.. xspf:playlist elements MAY contain zero or more location elements.. xspf:playlist elements MAY contain zero or more identifier elements.. ISO8601 creation date (not last-modified date) of the playlist.. If you modify such a playlist, move its //playlist/location element or //playlist/identifier to the top of the items in the //playlist/attribution element.. attribution location http://snafu.. com/modified_version_of_modified_version_of_original_playlist.. xspf /location location http://bar.. xspf /location location http://foo.. com/original_playlist.. xspf /location /attribution.. The link element allows non-XSPF web resources to be included in XSPF documents without breaking XSPF validation.. The meta element allows non-XSPF metadata to be included in XSPF documents without breaking XSPF validation.. MUST be valid text/plain, not XML.. Likely to be a hash or other location-independent name, such as a MusicBrainz identifier or isbn URN (if there existed isbn numbers for audio).. A human-readable comment on the track in text/plain format.. This value is only a hint -- different XSPF generators will generate slightly different values.. The link element allows non-XSPF web resources to be included in xspf:track elements without breaking XSPF validation.. The meta element allows non-XSPF metadata to be included in xspf:track elements without breaking XSPF validation.. Most MP3 players have some sort of cache for file information.. to do the job of converting XSPF to a plain old list of files or URLs.. A content resolver would be  ...   relative paths in a playlist according to the XML Base specification or IETF RFC 2396.. Scenario: There is a renderer which is capable of rendering one form of a media object but not another.. The server is able to deliver the object in either format, but it needs to communicate URLs for both.. Though HTTP content negotiation can be used for instances where the renderer contacts the server directly, it doesn't support protocol negotiation, and it can't be used in non-HTTP protocols.. Typical solution: This is particularly a problem for Real, which has a large installed base of obsolete software to be babied.. The solution is to delver alternate URLs within the same playlist and allow the client to choose.. The RAM format allows both a pnm: and a rtsp: URI within the same playlist, separated by a line containg the keyword "--stop--".. XSPF' solution: An XSPF track object can contain multiple identifiers or locations for the same media object.. Scenario: An MP3 player needs to access information about media objects which is too expensive to compute in real time.. For a large number of file a user can't wait to re-read ID3 tags, computing SHA1 hashes, or perform a fourier transform for each.. Typical solution: An MP3 player computes the information once, the first time it encounters an object, then caches the data.. The iTunes library format stores computed information like ID3 data in the global catalog and playlist.. XSPF' solution: XSPF defers this information to an external module called the content resolver, and mandates that the information not be included in shared playlists.. Scenario: A user needs information about high level concepts like artist and song title rather than machine-level concepts like file name and bit rate.. How should artist and song title be communicated, and how should they be stored?.. Typical solution: Derive the metadata according to an application-defined process like extracting ID3 tags, then then store a copy of the metadata in any playlists that reference a media object.. The EXTINF property of the extended M3U format is used in this way.. XSPF' solution: XSPF defers this functionality to other sources.. Metadata is hard; there are already many projects to deal with it, some of which are very good.. Metadata is attached to an XSPF track according to whatever syntax an imported vocabulary defines.. XML namespaces may be used, but the preferred syntax is the XSPF.. (These elements allows us to validate metadata from external sources, while namespaces don't.. ).. Scenario: A businessperson wants to make a batch of videos of related talks from a conference because watching them in a shared context gives a deeper understanding of the subject as a whole.. Typical solution: A user compiles copies of the videos and puts them in the same location, maybe in the same directory on a web server, maybe in the same directory on a hard drive.. The user then puts the locations, whether paths or URIs, into a file in the M3U format.. XSPF' solution: The XSPF.. element contains a sequence of.. elements, each of which points to one of the objects.. See the.. Use the.. xspf2m3u.. xsl.. stylesheet.. xspf2html.. xspf2smil.. xspf2soundblox.. Use the meta or link elements.. Use meta if the element contains a single value, like "blue" or "rock"; use link if the element contents are a URL.. Try to avoid using namespaces to add fields, because namespaced items cannot be validated by an XSPF validator.. Robert Kaye has created a Relax NG schema for XSPF draft 8 at.. http://mayhem-chaos.. net/stuff/xspf-draft8.. rng.. You can use.. Jing.. to invoke it.. For users of Emacs nxml-mode, Ryan Shaw has posted a.. rnc version of Robert's schema at.. http://lists.. musicbrainz.. org/pipermail/playlist/2004-October/000429.. This is just a matter of putting the.. rnc file in the schema/ subdirectory of your nxml-mode installation.. nxml-mode will find it automatically and add it to the list of available schemas; if you begin authoring an XSPF playlist, nxml-mode will choose the correct schema by examining the root element name.. Rather than include the literal artist name, song duration, etc, for a track within a playlist, MusicBrainz gives the URL of an XML file containing these items.. Assume that the MusicBrainz definition of what a track listing means is at http://musicbrainz.. org/track.. (There is nothing at that URL, which is fine -- the URL in an XSPF meta[@rel] attribute works the same way as the URL in an XML namespace declaration).. A typical track listing has a URL like http://musicbrainz.. org/mm-2.. 1/track/bdc846e7-6c26-4193-82a6-8d1b5a4d3429.. track identifier bdc846e7-6c26-4193-82a6-8d1b5a4d3429 /identifier title Smoke Two Joints /title creator Sublime /creator duration 175466 /duration meta rel="http://musicbrainz.. org/track" http://musicbrainz.. 1/track/bdc846e7-6c26-4193-82a6-8d1b5a4d3429 /meta /track.. Put the torrent file in a playlist/trackList/track/location element.. A sha1: URI is a location independent canonical ID, so it belongs in a playlist/trackList/track/identifier element.. A Magnet URI is resolvable, so belongs in playlist/trackList/track/location..

    Original link path: /xspf-v0.html
    Open archive

  • Title: XSPF Version 1
    Descriptive info: D.. Brown.. January 2005.. XSPF Version 1.. We describe an XML playlist format which is open, moderately simple, and carefully engineered.. 7.. 7.. 8.. 8.. A.. IANA Considerations.. A.. MIME media type name.. MIME subtype name.. Mandatory parameters.. Optional parameters.. Translated into plain english.. File extension.. Security Considerations.. Intellectual Property and Copyright Statements.. SMIL addresses a much larger problem space than the average MP3 player.. ? The choice is mainly between M3U and SMIL.. Almost every MP3 player accepts M3U but also invents an XML playlist format.. SMIL, on the other hand, is a prescription for a kind of application that is different from an MP3 player -- it describes layouts in time, while XSPF describes concepts common among MP3 players.. Given a song with the comment "danceable!", SMIL might have an instruction to write that text in the upper left in a bold sans-serif font, while XSPF would tell an MP3 player that the text is a comment and say nothing about formatting.. 0" encoding="UTF-8"? playlist version="1" xmlns = "http://xspf.. mp3 /location /track track location http://example.. Version 1 is not far from being frozen and code-ready.. This document describes version 1, which is not ready for implementation.. Version 0, the previous one, is stable and frozen -- developers can assume that it will not change.. The home of our working group on the web is http://xspf.. We have benefitted a great deal from the contributions of Dan Brickley, Kevin Marks and Ian C.. Rogers, each of whom strongly influenced the shape of the format.. We are grateful for comments and feedback from Ryan Shaw, Alf Eaton, Steve Gedikian, Russell Garrett, and Ben Tesch.. The terms URI, URL, and URN should be  ...   URN.. URL of an image to display in the absence of a //playlist/trackList/image element.. $main_date = date("Y-m-d\TH:i:s", $timestamp); $tz = date("O", $timestamp); $tz = substr_replace ($tz, ':', 3, 0);.. URL of a resource that describes the license under which this playlist was released.. URL of a resource.. The extension element allows non-XSPF XML to be included in XSPF documents without breaking XSPF validation.. playlist xmlns:cl="http://example.. com" cl:clip start="25000" end="34500"/ /extension /playlist.. URL of resource to be rendered.. URL of a place where this resource can be bought or more info can be found.. URL of an image to display for the duration of the track.. URN of a resource type.. URN of a resource defining the metadata.. A Relax NG schema.. has been provided to test for syntactic conformance.. Applications MUST assign unique URNs from their own namespace for each link, meta and extension element.. New URNs SHOULD be assigned if syntax and/or semantics of a link, meta or extension element changes.. The RAM format allows both a pnm: and a rtsp: URL within the same playlist, separated by a line containg the keyword "--stop--".. The user then puts the locations, whether paths or URLs, into a file in the M3U format.. Matthias Friedrich has created an XML schema for XSPF version 1 at.. http://www.. stud.. uni-karlsruhe.. de/~uy7l/xspf-1.. xsd.. Robert Kaye has created a Relax NG schema for XSPF version 0 draft 8 at.. ,".. EMail:.. lucas@gonze.. matt@mafr.. de.. Dave Brown.. dabrown@yahoo-inc.. xspf+xml.. (This name is provisional, meaning that we have not yet found a volunteer to steer it through the name-granting process).. none.. "charset", per.. RFC3023.. The mime type for XSPF playlists is.. Playlist authors should not publish documents containing local paths..

    Original link path: /orig-xspf-v1.html
    Open archive

  • Title:
    Original link path: /validation/xspf-1_0.7.rng
    (No additional info available in detailed archive for this subpage)

  • Title:
    Original link path: /validation/xspf-0_0.7.rng
    (No additional info available in detailed archive for this subpage)



  •  


    Archived pages: 14