Difference between revisions of "Sidecar File"
Jon Phillips (talk | contribs) |
Jon Phillips (talk | contribs) |
||
Line 3: | Line 3: | ||
[[Category:metadata]] | [[Category:metadata]] | ||
[[Category:Developer Challenges]] | [[Category:Developer Challenges]] | ||
+ | [[Category:Developer Challenges Completed]] | ||
[[Category:specification]] | [[Category:specification]] | ||
+ | [[Category:example]] | ||
+ | [[Category:XML]] | ||
+ | [[Category:SVG]] | ||
+ | [[Category:filetype]] | ||
{{incomplete}} | {{incomplete}} | ||
− | This is a specification for companion file metadata. This takes the form of an associated RDF file that has metadata and licensing. | + | This is a specification for companion file metadata. This takes the form of an associated RDF file that has metadata and licensing that is included along with a work. |
− | Thus if you had a file such as the one referenced, '''barcode_ean13.svg''', one would create a file barcode_ean13.rdf that would contain the following. The rdf:about reference in <Work /> tag is very important for linking both relative and absolute information to a file. | + | Thus if you had a file such as the one referenced, '''barcode_ean13.svg''', one would create a file '''barcode_ean13.rdf''' that would contain the following. The rdf:about reference in <Work /> tag is very important for linking both relative and absolute information to a file. |
== Sample == | == Sample == |
Revision as of 23:23, 1 May 2006
This is a specification for companion file metadata. This takes the form of an associated RDF file that has metadata and licensing that is included along with a work.
Thus if you had a file such as the one referenced, barcode_ean13.svg, one would create a file barcode_ean13.rdf that would contain the following. The rdf:about reference in <Work /> tag is very important for linking both relative and absolute information to a file.
Sample
<rdf:RDF xmlns="http://web.resource.org/cc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > <Work rdf:about="http://www.openclipart.org/incoming/2004/04/contents/barcode_ean13.svg"> <dc:title>EAN-13 Bar Code</dc:title> <dc:description>A Bar Code: EAN-13.</dc:description> <dc:subject>barcode, bar code, bar, code, UPC, EAN, EAN-13, universal product code, universal, product, code, product code</dc:subject> <dc:publisher><Agent rdf:about="http://www.openclipart.org/"><dc:title>Open Clip Art Project</dc:title></Agent></dc:publisher> <dc:creator><Agent rdf:about="http://www.theworths.org/richard/"><dc:title>Richard D. Worth</dc:title></Agent></dc:creator> <dc:rights><Agent rdf:about="http://web.resource.org/cc/PublicDomain"><dc:title>Public Domain</dc:title></Agent></dc:rights> <dc:date>2004-04-27</dc:date> <dc:format>image/svg+xml</dc:format> <dc:type>http://purl.org/dc/dcmitype/StillImage</dc:type> <license rdf:resource="http://web.resource.org/cc/PublicDomain" /> </Work> <License rdf:about="http://web.resource.org/cc/PublicDomain"> <permits rdf:resource="http://web.resource.org/cc/Reproduction" /> <permits rdf:resource="http://web.resource.org/cc/Distribution" /> <permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> </License> </rdf:RDF>
NOTE: The above #Sample does not include all of the Dublin Core elements.
Developer Challenges
It is impractical to embed metadata in some file formats, and, it should be optional to store metadata outside of a file. So we need a specification for a "companion" metadata file that would define license and other metadata information. This could take
Implementations
- Open Clip Art Library puts RDF metadata and licensning info into a package of clip art that is named with *.rdf.
- Please add your implementation here :)
Examples
- See this page detailing the Open Clip Art Library's solution.
- See the #Sample above to figure out how to connect your file with CC licesning and metadata.
- Please add your example, screenshot, mockup, etc here :)
TODO
- Please add your TODO here :)