Shared Online
Media Archive
SOMA Metadata
Element Set
A Collaborative Work by SOMA Group
September 2002
|
Version |
Author |
Date |
Notes |
|
0.1.0 |
Philippe
Bechamp, AMARC |
2
August 2002 |
Based
on meeting held at CMA office in Sheffield on 22 July. |
|
0.2.0 |
Suzi
Wells, OneWorld.net |
27
September 2002 |
Based
on comments on version 0.1. |
|
0.3.0 |
Suzi
Wells, OneWorld.net |
11
October 2002 |
Based
on comments on version 0.2, and the meeting on 10 October 2002 |
|
0.4.0 |
Suzi
Wells, OneWorld.net |
22
October 2002 |
Based
on meeting on 22 October 2002 |
|
0.5.0 |
Suzi
Wells, OneWorld.net |
21
November 2002 |
Finalise
vocabularies, deal with open issues, incorporate comments from emails. |
|
0.5.1 |
Suzi
Wells, OneWorld.net |
22
January 2002 |
Correction
to SOMA Topics (some topics had been left out). |
|
1.0.0 |
Suzi
Wells, OneWorld.net |
22
January 2002 |
Same
as version 0.5.1 |
|
|
|
|
|
Table of Contents
Different
Formats of a Resource
Refinement: Relation.IsVersionOf, Relation.HasVersion
Refinement: Relation.IsReplacedBy, Relation.Replaces
Refinement: Relation.IsPartOf, Relation.HasPart
Refinement: Relation.IsFormatOf, Relation.HasFormat
Refinement: ExtendedInformation.Scheme
Appendix B: XML Representation
Organisation
Names in Several Languages
Appendix C: About This Document
Introduction
Purpose of this document
This documents describes a draft metadata format for exchange of metadata for multimedia files between members of the SOMA Group. It is based on Dublin Core 1.1 [1] as well as EBU Tech 3273 [2].
Brief Glossary
SOMA providers. Organisations who publish data using the SOMA metadata standard.
SOMA members. Members of the SOMA Group (who maintain and support the standard).
Resource. An item being represented by the metadata. Examples include: a radio programme, a film, a website, an excerpt from a radio programme. A resource may be available in several different formats. For example, an audio file may be available in MP3 or Real Audio format, a website may be available in Flash or HTML format.
Summary
When preparing this metadata set, the following assumptions have been made:
· The metadata will be used to create a shared media archive, searchable by the public and by people working at community radio / TV stations.
· The metadata set will be used to store information about a range of media files, including audio, video, websites, and learning materials.
· The audience may want to listen online or to download and rebroadcast.
· The data set should be kept as simple as possible.
· The data set should stay as close to EBU and DC as possible.
· SOMA providers may store more information about a programme locally for their own purposes.
· SOMA providers set their own level of access and security. For example, they may require users to log in to their site before they can download a file.
The metadata set is not intended for the following purposes:
· Information storage: SOMA providers will probably want to store more information locally, or to store information in a different format.
· Instant streaming of media files: organisations wishing to stream files found using the SOMA metadata set will need to download, then upload them onto their own site before they are able to stream them. They may find that, before downloading the file, they need to visit several pages, and/or create an account on the system of the member hosting the file.
Comments and Open Issues
Different Formats of a Resource
Within the SOMA Metadata standard there are two acceptable ways of representing different formats of the same resource.
A. Repeat metadata, use IsFormatOf. Each format the resource is available in has its own copy of the metadata set. The relationship between the metadata sets is indicated using Refinement 13.4 (IsFormatOf / HasFormat).
B. Link to a holding page. The SOMA provider creates a holding page with links to all formats of the resource. There is one set of metadata, with the URI of the holding page as the identifier in Element 10. Element 9 (Format) is repeated for each format available on the holding page.
Ż Ż
What is meant by “a different format of the same resource”?
· Files with the same content, but accessed using different software. For example, MP3 / Real Audio.
· Files with the same content, but of different quality. For example, mono / stereo, high / low bitrate.
· Files with the same content, but made available on a different medium. For example, an audio file / a transcript of an audio file, a video file / the soundtrack of a video file.
Audience
An
Audience element has been added to Dublin Core. This information may be of interest to people using the SOMA
standard, but we have agreed not to include the element at this stage.
We will
consider introducing this element in the future. We do not guarantee that the element will be introduced, as some
members are concerned that this may encourage censorship. We recommend that members record this
information in their own systems using their own controlled vocabulary.
Extended Information
We will include a mechanism for storing extended information. This will be used when organisations have private agreements to provide extra fields to be used by some other initiative (for example, the proposed Stream on the Fly system). This is handled by the optional element: ExtendedInformation (see Elements and Refinements section for further information.
Open Issues
Subject
·
Other controlled vocabularies. We
are open to the idea of SOMA providers including information from other
controlled vocabularies in this section.
Guidelines for such use will be agreed at a later date.
Rights
·
Include Creative Commons. When the Creative
Commons standard becomes available, we will consider using it. A draft version of the Creative Commons
licence in RDF/XML is now available [10]
·
Listen / Download / View. We will look into
including information about whether the file is available for download and for
listen/view online. We would like the
information to be available in a structured format, so that it is possible to search
for, e.g. audio programmes available for free download.
Data Changes
No data
changes since 0.5.1. Only change since
0.5.0 is correction of SOMA Topics.
Elements and Refinements
Element: Title
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
A name given to the resource. |
|
Comments: |
Typically, a title will be a name by which the resource is formally known. The title is tied to the archived item: for a series use the series title, for a programme a programme title, for an item an item title. To differentiate between a series title and programme title when these are identical, recommended best practise is to use a date along with the programme title. For example, "News" is a series title; "News 2000.11.12" is a programme title. Where there is no natural date, put a number in front of the title to show order of the series, e.g. “1. Janet Moves to London”. Where a programme has been broken into several parts, the part number should be listed here. For example, “Report from Rio, Part 1”, “Report from Rio, Part 2”. Implementation guidance: When users are entering data into the original system, the user interface should encourage them to follow best practice. It is recommended they enter title and episode/part number/date separately. These should then be combined following the guidelines above either when the data is saved locally, or when the data is exported to the SOMA format. |
|
Encoding Scheme: |
Text |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Title.Alternative
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes |
|
Definition: |
Any form of the title used as a substitute or alternative to the formal title of the resource. |
|
Comments: |
This qualifier can include title abbreviations as well as well as translations. Only the main title may be translated. Abbreviations and alternative titles should only be provided in the original language. |
|
Encoding Scheme: |
Text |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Element: Creator
|
Required: |
Yes |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes |
|
Definition: |
An entity primarily responsible for making the content of the resource. |
|
Comments: |
Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity. We recommend that names be written in the following order: surname, first name. However, they can also be written according to local practise. We recommend that organisations do not use abbreviated forms of their name, unless this is the name they are most commonly known by (e.g. OXFAM). The difference between Contributor and Creator is sometimes difficult to decide. If in doubt, use contributor. These two fields should be considered equivalent for search purposes. |
|
Element Encoding Scheme: |
See Appendix B for notes about representing translations of organisation names in RDF. In plain XML, translations of organisation names should not be provided. |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Creator.Role
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
Role the creator played in creating the resource. For example: producer, writer or editor. |
|
Comments: |
- |
|
Encoding Scheme: |
SOMA Roles (see Appendix A) |
|
Variation from DC: |
There is no Creator.Role refinement in DC. |
|
Variation from EBU: |
EBU uses EBU Reference Data Table: Roles in broadcasting [3] (not yet published) |
Element: Subject
|
Required: |
Yes |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes |
|
Definition: |
The topic of the content of the resource. |
|
Comments: |
Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Persons as subjects are also placed here. Genre of the content is placed under element Type. Geographical locations and historical periods as subjects are placed under Coverage. |
|
Encoding Scheme: |
SOMA Topics (see Appendix A) Text Where groups of organisations have similar interests, other controlled vocabularies may be used here. |
|
Variation from DC: |
Not using recommended encoding schemes |
|
Variation from EBU: |
Not using recommended encoding schemes |
Element: Description
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
An account of the content of the resource. |
|
Comments: |
Description may include but is not limited to: an abstract, a running order, or a free-text account of the content. |
|
Encoding Scheme: |
Text |
|
Variation from DC: |
None, but refinements (table of contents, abstract) aren’t used. |
|
Variation from EBU: |
None |
Element: Publisher
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
Organisation who originally made the resource available to SOMA. |
|
Comments: |
We recommend that organisations do not use abbreviated forms of their name, unless this is the name they are most commonly known by (e.g. OXFAM). |
|
Encoding Scheme: |
Text. May use RDF construct “seeAlso” to point to a FOAF file (see Appendix B for more information). |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Publisher.URI
|
Required: |
No |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
URI of the Publisher. |
|
Comments: |
May be used for linking to the homepage of the partner hosting the file. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
No such refinement in DC. |
|
Variation from EBU: |
No such refinement in EBU. |
Refinement: Publisher.Logo
|
Refinement 5.2: |
Logo |
|
Required: |
No |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
URI of a logo of the Publisher. |
|
Comments: |
May be used for linking to the homepage of partner hosting the file. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
No such refinement in DC. |
|
Variation from EBU: |
No such refinement in EBU. |
Element: Contributor
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes |
|
Definition: |
An entity responsible for making contributions to the content of the resource. |
|
Comments: |
Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity. We recommend that names be written in the following order: surname, first name. However, they can also be written according to local practise. We recommend that organisations do not use abbreviated forms of their name, unless this is the name they are most commonly known by (e.g. OXFAM). The difference between Contributor and Creator is sometimes difficult to decide. If in doubt whether an entity is a creator or contributor use the element contributor. These two fields should be considered equivalent for search purposes. |
|
Encoding Scheme: |
See Appendix B for notes about representing translations of organisation names in RDF. In plain XML, translations of organisation names should not be provided. |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Contributor.Role
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
Role the contributor played in creating the resource. For example: producer, writer or editor. |
|
Comments: |
- |
|
Encoding Scheme: |
SOMA Roles (see Appendix A) |
|
Variation from DC: |
There is no Contributor.Role refinement in DC. |
|
Variation from EBU: |
EBU uses EBU Reference Data Table: Roles in broadcasting [3] (not yet published) |
Element: Date
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
A date associated with an event in the life cycle of the resource. |
|
Comments: |
If unqualified, assume same value as the Date.Created refinement. Approximate dates should be explained in Description element. |
|
Encoding Scheme: |
DCMI: Period Encoding Scheme [4] W3C-Date and Time Format (DTF) [5] |
|
Variation from DC: |
None, but not using the Date.Valid refinement. |
|
Variation from EBU: |
None, but not using the Date.Digitized refinement. |
Refinement: Date.Created
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
Date of creation of the content of the resource. |
|
Comments: |
Approximate dates should be explained in Description element |
|
Encoding Scheme: |
W3C-Date and Time Format (DTF) [5] DCMI: Period Encoding Scheme [4] |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Date.Available
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
Date (often a range) that the resource will become or did become available. |
|
Comments: |
Should show the date the publisher made the resource available. This will generally be the date the metadata was first published. |
|
Encoding Scheme: |
DCMI: Period Encoding Scheme [4] W3C-Date and Time Format (DTF) [5] |
|
Variation from DC: |
None |
|
Variation from EBU: |
Not used in EBU |
Refinement: Date.Issued
|
Required: |
No |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
Date made available by original publisher. For example, the broadcasting date of a radio programme. |
|
Comments: |
It is recommended best practise to use the element both for recordings that are "born-digital" and recordings that are digitised. |
|
Encoding Scheme: |
DCMI: Period Encoding Scheme [4] W3C-Date and Time Format (DTF) [5] |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Refinement: Date.Modified
|
Required: |
Required if applicable. |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
Date on which the resource or metadata was last changed. |
|
Comments: |
If the resource or metadata has been modified since it was made available, this must contain the date of the most recent time this occurred. |
|
Encoding Scheme: |
W3C-Date and Time Format (DTF) [5] |
|
Variation from DC: |
None |
|
Variation from EBU: |
None |
Element: Type
|
Required: |
Yes |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
The nature or genre of the content of the resource. |
|
Comments: |
To describe the physical or digital manifestation of the resource, use the Format element. |
|
Encoding Scheme: |
DCMI Type vocabulary [6] SOMA Genres (see Appendix A) |
|
Variation from DC: |
Using SOMA Genres in addition to DCMI Types. |
|
Variation from EBU: |
EBU uses a greatly extended list of types. |
Element: Format
|
Required: |
Yes |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
The physical or digital manifestation of the resource. |
|
Comments: |
Use SOMA Media Type for online resources and same as Format.Medium for offline |
|
Encoding Scheme: |
For online resources, use SOMA Media Type (see Appendix A) For offline resources, use controlled vocabulary: “offline”. |
|
Variation from DC: |
Using an extended version of their Internet Media Type list. |
|
Variation from EBU: |
Using an extended version of their Internet Media Type list. |
Refinement: Format.Extent
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
The size or duration of the resource |
|
Comments: |
Repeat for indicating extent in seconds and extent in octets (8-bit bytes). |
|
Encoding Scheme: |
See Appendix B for further information. |
|
Variation from DC: |
None. |
|
Variation from EBU: |
Duration in seconds (not HHMMSS). Added extent in octets. |
Refinement: Format.Medium
|
Required: |
Yes, for offline resources |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
The material or physical carrier of the resource. |
|
Comments: |
When media is offline, field contains "offline". When media is online, field contains "online". |
|
Encoding Scheme: |
Controlled vocabulary: “offline” or “online”. |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Element: Identifier
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
An unambiguous reference to the resource within a given context. |
|
Comments: |
SOMA will use URI of the online resource. If the resource is offline or unavailable, or if it is necessary to log in to some website to gain access to the resource, a unique URI to a relevant web page should be used. |
|
Encoding Scheme: |
Unique URI |
|
Variation from DC: |
None. |
|
Variation from EBU: |
Not following their stated best practice (to use various ID schemes relating to broadcast material). |
Element: Language
|
Required: |
Yes |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
A language of the intellectual content of the resource. |
|
Comments: |
Repeated where the complete content of the resource may be understood in several languages. For example, a French film with English subtitles should have two language elements: French and English. Each use of the x-lang encoding should be reported to the SOMA group, who will maintain a public list. |
|
Encoding Scheme: |
ISO-639-2 - 3-letter codes [8] W3C RFC 1766 [7] Please use x-lang syntax (as in RFC 1766 [7]) for languages not covered by ISO-639-2, and report use to the SOMA group. The group will maintain a public list of x-lang strings that have been used. |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Element: Relation
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
A reference to a related resource |
|
Comments: |
Not used unqualified. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
Not using some refinements: IsRequiredBy, Requires, IsReferencedBy, References. |
|
Variation from EBU: |
Not using some refinements: IsRequiredBy, Requires, IsReferencedBy, References. |
Refinement: Relation.IsVersionOf, Relation.HasVersion
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
IsVersionOf: The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in content rather than differences in format. HasVersion: The described resource has a version, edition, or adaptation, namely, the referenced resource. |
|
SOMA Comment: |
Used exclusively for language translations. URI should ideally link to metadata of the related resource, otherwise to the related resource or a page about the related resource. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Refinement: Relation.IsReplacedBy, Relation.Replaces
|
Required: |
No |
|
Repeatable: |
No (but can have IsReplacedBy and Replaces) |
|
XML lang. qualified: |
No |
|
Definition: |
IsReplacedBy: The described resource is supplanted, displaced, or superseded by the referenced resource. Replaces: The described resource supplants, displaces, or supersedes the referenced resource. |
|
Comments: |
Used for redirects URI should ideally link to metadata of the related resource, otherwise to the related resource or a page about the related resource. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Refinement: Relation.IsPartOf, Relation.HasPart
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes, if text. No, if URI. |
|
Definition: |
IsPartOf: The described resource is a physical or logical part of the referenced resource. HasPart: The described resource includes the referenced resource either physically or logically. |
|
Comments: |
Used for membership in series. URI should ideally link to metadata of the related resource, otherwise to the related resource or a page about the related resource. |
|
Encoding Scheme: |
Text or URI. |
|
Variation from DC: |
Allow text, not just URI. |
|
Variation from EBU: |
Allow text, not just URI. |
Refinement: Relation.IsFormatOf, Relation.HasFormat
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
IsFormatOf: The described resource is the same intellectual content of the referenced resource, but presented in another format. HasFormat: The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format. |
|
Comments: |
Use for alternate formats, such as scripts or alternative media types (Real Audio, MP3, etc). URI should ideally link to metadata of the related resource, otherwise to the related resource or a page about the related resource. |
|
Encoding Scheme: |
URI |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Element: Coverage
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
The extent or scope of the content of the resource. |
|
Comments: |
If unqualified, assume the value relates to spatial coverage. |
|
Encoding Scheme: |
See refinements. |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Refinement: Coverage.Spatial
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
Yes, if text. No, if SOMA Location. |
|
Definition: |
Spatial characteristics of the intellectual content of the resource. |
|
Comments: |
For example, the geographical origin of folk music is placed here. |
|
Encoding Scheme: |
SOMA Locations (see Appendix A) Text for city names, etc. Use Getty Thesaurus [9] to check spelling. |
|
Variation from DC: |
Not using suggested controlled vocabulary. |
|
Variation from EBU: |
Not using suggested controlled vocabulary. |
Refinement: Coverage.Temporal
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
Time period(s) to which the intellectual content of the resource pertains. |
|
Comments: |
For example, historical periods discussed in a history programme might be placed here. |
|
Encoding Scheme: |
DCMI Period encoding scheme [4] W3C-Date and Time Format (DTF) [5] |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Element: Rights
|
Required: |
Yes |
|
Repeatable: |
No |
|
XML lang. qualified: |
Yes |
|
Definition: |
Information about rights held in and over the resource. |
|
Comments: |
By "Rights" we here mean the rights to the programme (sound file etc.) as a whole. For rights covering parts of the file (music, poetry etc included in the file) keep these in the institutions locally. Here register for instance NRK, BBC or the production company responsible for the programme or the record company that owns the rights to a phonogram. Instead of text, you may use a URI to point to a standardized statement of rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource. |
|
Encoding Scheme: |
Text or URI |
|
Variation from DC: |
None. |
|
Variation from EBU: |
None. |
Element: ExtendedInformation
|
Required: |
No |
|
Repeatable: |
Yes |
|
XML lang. qualified: |
No |
|
Definition: |
Additional data concerning the resource. May be used to store proprietary or application or organization specific information. |
|
Comments: |
May be repeated with different schemes. This element should mainly be used to store information that is not universally applicable but should still be exchanged with the resource. This element should be stored unchanged (as blob or similar) if the storing application cannot use it. |
|
Encoding Scheme: |
XML Element |
|
Variation from DC: |
Does not exist in DC. |
|
Variation from EBU: |
Does not exist in EBU. |
Refinement: ExtendedInformation.Scheme
|
Required: |
Yes, if ExtendedInformation element is present |
|
Repeatable: |
No |
|
XML lang. qualified: |
No |
|
Definition: |
The encoding scheme for the extended information element. |
|
Comments: |
This is a string that uniquely identifies the scheme of the extended information data. |
|
Encoding Scheme: |
Text |
|
Variation from DC: |
Does not exist in DC. |
|
Variation from EBU: |
Does not exist in EBU. |
References
[1] Dublin Core Metadata Element Set http://www.dublincore.org/documents/dces/ and qualifiers http://dublincore.org/documents/dcmes-qualifiers/
[2] EBU Metadata for Radio Archives http://www.ebu.ch/tech_t3293.pdf
[3] EBU Roles in broadcasting (not published at time of writing) http://www.ebu.ch/tech_info_roles.html
[4] Dublin Core Metadata Initiative – Period Encoding Scheme http://dublincore.org/documents/dcmi-period/
[5] W3C Note: Date and Time Formats http://www.w3.org/TR/NOTE-datetime
[6] Dublin Core Metadata Initiative – Type Vocabulary http://dublincore.org/documents/dcmi-type-vocabulary/
[7] RFC 1766: Tags for the Identification of Languages, Internet Engineering Task Force http://www.ietf.org/rfc/rfc1766.txt
[8] ISO 639-2: Codes for the representation of names of languages – Part 2: Alpha-3 code (Registration Authority) http://lcweb.loc.gov/standards/iso639-2/
[9] Getty Thesaurus of Geographic Names http://www.getty.edu/research/tools/vocabulary/tgn/
[10] Creative Commons Metadata [DRAFT] http://www.creativecommons.org/metadata/spec
Appendix A: Vocabularies
SOMA Genres
Actuality
Advert / jingle / spot
Announcement
Call-in show
Children’s / youth
Comedy
Community media
Dance
Documentary
Drama
Educational
Feature
Game show
Interview
Magazine
Music
News
Oral history / storytelling
Talk show / discussion
Training
SOMA Roles
Artist
Author
Commentator
Composer
Copyright Holder
Correspondent
Designer
Director
Editor
Funder / Sponsor
Interviewee
Interviewer
Narrator
Participant
Performer
Producer
Production Personnel
Speaker
Transcriber
Translator
Other
Based on FIU Digital Library’s Metadata Creation Manual:
http://www.fiu.edu/~diglib/metadata/roles.html
SOMA Media Types
Real Audio
audio/realaudio
audio/x-realaudio
audio/pn-realaudio
audio/x-pn-realaudio
audio/x-pn-realaudio-plugin
audio/rn-realaudio
audio/vnd.rn-realaudio
MPEG2
audio/mpeg2
audio/x-mpeg2
MP3
audio/m3u
audio/x-m3u
audio/mp3
audio/x-mp3
audio/mpg
audio/x-mpg
audio/mpeg
audio/x-mpeg
audio/mpeg3
audio/x-mpeg-3
audio/mpegurl
audio/x-mpegurl
audio/x-mpeg-url
Ogg Vorbis
application/x-ogg
audio/x-vorbis
Real Video
video/vnd.rn-realvideo
video/x-pn-RealVideo
video/x-pn-RealVideo-plugin
MPEG video
video/mpeg
video/MP4V-ES
MPEG-2 video
video/mpeg-2
Macintosh
Quicktime
video/quicktime
video/x-quicktime
Microsoft
Video
video/x-msvideo
SMIL
application/smil
Text
text/plain
text/html
text/enriched
SOMA Locations
Hierarchical system set out in the UN standard: http://www.un.org/Depts/unsd/methods/m49regin.htm
The countries of "Tibet", "Kosovo" and "Palestine" will be added to this classification system.
SOMA Topics
The top-level
categories are intended as a suggestion of how to display the categories in a
manageable form. They don't really
imply containment (so things that are about "gender" are not
necessarily about "development").