Comments about Atom and Dublin
Note that many can be repeated with "lang" attributes.
Atom Dublin Comment
title DC.title or html ...
subtitle nothing good in DC; see http://askdcmi.askvrd.org/default.aspx?id=12046&cat=1720
perhaps just colon separate in title: http://ntl.bts.gov/dublincore/ntl_dc_desc.html
in atom, subtitle is only for feed, not entry
in MODS, titleInfo/title and titleInfo/subTitle do not overlap
in USMARC, 245$a may split with 245$b or may have it all
in NITF, there is and <title type="subtitle">
in newspapers, there is a "deck" that might appear between title and copy
a "lead" is the first one or few sentences
DCTERMS.alternative alternative title. may also be a "shorttitle" for indexing, vs. what appears on the page. rather vague in DC
USMARC has 246
MODS has <titleInfo type="abbreviated"> and <titleInfo type="alternative">
category/@term DC.subject generally means "classifiable under", not so much "is about".
that is, a genre or general category.
atom allows @scheme, @label. dc says keywords or classification codes
DC.subject can be comma-separated like html <meta name="keywords" content="...">
but we favor repeating the element rather than a single value
atom category may be repeated
NewsML distinguishes Topic (formal name) and Subject (IPTC Subject Codes)
DC.type one of DCMITYPE: StillImage, MovingImage, Sound, Text, Software
DCTERMS.audience
updated DCTERMS.modified DC.date is too vague, though in general taken to be publication
published DCTERMS.issued publication date
DCTERMS.available date range it is/was/will be available
DCTERMS.created when created
DCTERMS.dateSubmitted when submitted to publisher
DCTERMS.dateAccepted when accepted (or approved) by publisher
author/name DC.creator an author might have an affiliation
suggestion in http://www.dublincore.org/documents/dc-citation-guidelines/ is to use contributor for the affiliation.
but seems questionable, since associates with resource, not the author.
RFC2629 has a nested "organization"
docbook has a nested "affiliation"
DC.publisher note that the publisher and the issuing organization (which might be some professional group) might differ.
some publishers have nicknames ("W3" or "IETF" or "ISO"); MARC has Publisher Abbreviation/Name (260/b)
contributor DC.contributor
DC.language iso639-2
summary DCTERMS.abstract DC.description is too vague. see also html <meta name="description" content="..."> which describes the content (vs. synopsis?)
see also PRISM.teaser
DCTERMS.tableOfContents
DC.coverage geo scope, such as TGN http://www.getty.edu/research/tools/vocabulary/tgn/index.html
some bibliographies also expect a city of publication
DC.format mime type
DCTERMS.extent size or duration
content @type, @src
link DC.relation dcterms: isPartOf, hasPart, hasFormat, hasVersion
atom link is similar to html link: @href. optional: @rel, @type, @hreflang, @title, and @length. if just href, it is the link to the content
id DC.identifier dc is opaque identifier such as ISBN, DOI, URI. different versions has same id but different "updated"
atom id is a permanent URI, but may be like "urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a" or "tag:diveintomark.org,2004-05-27:1192"
see http://diveintomark.org/archives/2004/05/28/howto-atom-id
<id>http://www.example.org/entries/1</id> is opaque, while <link href="http://..."/> is clickable
source DC.source in atom, includes all XML about original feed. in dublin could either be originally from, or part of, etc.
rights atom rights is just content.
some suggest an attribute like:
<rights href="http://creativecommons.org/licenses/by/1.0/">Creative Commons: Attribution</rights>
for example here: http://www.intertwingly.net/wiki/pie/License
but that is not what the Atom spec says. there is a separate proposal for an atom license element:
draft-snell-atompub-feed-license-05.txt
which specifies:
<link rel="license"
type="text/html"
href="http://creativecommons.org/licenses/by/2.5/" />
DC.rights DC.rights is vague; typically the copyright statement as text, or could be URI
ID3.TCOP,WCOP,WOAF TCOP example: "1995 Example Band licensed http://creativcommons.org/licenses/by/1.0/ verify at http://example.com/licenseinfo"
or very narrowly: <year> <copyright holder> Licensed to the public under <licenseurl> verify at <verification url>
the apparent idea being that the url after "verify at" is for machines and the one before is human readable
http://lists.ibiblio.org/pipermail/cc-metadata/2003-May/000111.html
http://lists.ibiblio.org/pipermail/cc-metadata/2005-December/000755.html
blah blah {license-url} verify at {metadata-url}
license-url would move to WCOP
metadata-url would move to WOAF
[both are in 2.3 and 2.4]
4.3.1 WCOP Copyright/Legal information
4.3.1 WOAF Official audio file webpage
Though http://www.id3.org/id3v2.4.0-frames.txt indicates WCOP has both copyright and license
license
DCTERMS.license DCTERMS.license value is a URI.
DCTERMS.accessRights who can access, or security status
DCTERMS.rightsHolder a person or organization
generator like html <meta name="generator">
icon icon and logo are for feeds, not entries.
logo