home of the
digital media encyclopedia
About, Products, Download, Search, Browse, Discuss, BitSocieties, Help
best with Bitzi-Powered Applications.
Bitzi XML Ticket ServiceRDF-compliant XML describing files in the Bitzi catalog is available from the URLs:
http://ticket.bitzi.com/rdf/»bitprint«Where »bitprint« represents a full Bitzi bitprint (Base32 SHA1 value + '.' + Base32 TigerTree value) and »SHA1« represents just a Base32 SHA1 value. These values may, but need not be, preceded by URN labelling like "urn:bitprint:" or "urn:sha1:".
Further documentation of the internal Ticket format is coming soon; browsing a few will reveal them to be helpfully self-descriptive. We have sought to conform with the Common-XML 1.0 conventions for straightforward XML, and have reused pre-existing namespaces from the W3C, Dublin Core Initiative, and MusicBrainz where appropriate.
The root element of each Ticket currently looks like:
Additional info about the fields that appear in our XML is available on our OpenBits Data Dump info page.<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:bz="http://bitzi.com/xmlns/2002/01/bz-core#" xmlns:mm="http://musicbrainz.org/mm/mm-2.0#">
If the Bitzi OpenBits Catalog does not have any information about the requested file, you will receive an empty but well-formed Ticket, containing only bookkepping fields about the Ticket's minting time, expiration time, and recommended filename as a standalone file.
As the traffic against the ticket.bitzi.com URLs increases, they may respond with unique busy, redirect, and challenge codes designed to shunt lookups to other avenues. Documentation of these special cases, and suggestions for dealing with them, is coming soon – but in the meantime, be ready to handle failed retrievals gracefully.