Msc/E/title
From Steeple
(up) view all abstract elements
<< typeedit
| title |
creatoredit
>>
- id (edit)
- type (edit)
- title (edit)
- creator (edit)
- contributor (edit)
- abstract (edit)
- description (edit)
- subject (edit)
- institution (edit)
- place (edit)
- spacetime (edit)
- time (edit)
- collection (edit)
- size (edit)
- publisher (edit)
- language (edit)
- created (edit)
- modified (edit)
- available (edit)
- valid (edit)
- oldversion (edit)
- newversion (edit)
- license (edit)
- rightsholder (edit)
- mediacontent (edit)
- mediadistribution (edit)
- relatedinformation (edit)
- linkedmetadata (edit)
- timedimages (edit)
- subtitles (edit)
- timedkeywords (edit)
- chapters (edit)
- timeddescription (edit)
Contents |
[edit] 1 Description of abstract element: Title
A name given to the resource. In current practice, this term is used primarily with literal values; however, there are important uses with non-literal values as well. As of December 2007, the DCMI Usage Board is leaving this range unspecified pending an investigation of options.
2 Discussion of title [add to discussion,edit discussion]
Status is 'draft' because:
[edit] 2.1 languages
Title, subtitle, description should be available in different languages. So may need to carry a lang=”en” attribute. In which case we'd have 1-n, distinguished by lang attribute. I guess this would be solved by xml:lang.
[edit] 2.2 subtitle/seriestitle
Bjoern: Does the encoding scheme "title_:_subtitle" make sense? This means the title doesn't print prettily. For mhxml this is perhaps ok, but certainly for rss/atom we need a subtitle solution. Why not have a proper subtitle field in the mhxml as well?
Proposal is to add s:type="maintitle|subtitle|seriestitle".
- Maintitle: optional. The <title> is the main title.
- Series title: additional title that is the title of the series
- subtitle: a subtitle to the title.
[edit] 2.3 Multiple titles?
What if different streams belonging to the same media item have got different titles or different descritions? Also see Msc/E/mediacontent.
3 Expression of title in various schemes [Edit properties]
As xml in Matterhorn xml and rss/atom:
<Dcterms:title> ... title ... </Dcterms:title>
<Rss:title S:type="main/series/subtitle"> ... title ... </Rss:title>
<Atom:title S:type="main/series/subtitle"> ... title ... </Atom:title>
Full table:
| name | number | MH xml | RSS (with Yahoo/Steeple) | attributes | Atom (with Yahoo/Steeple) | attr |
|---|---|---|---|---|---|---|
| Title | 33 | Dcterms:title | Rss:title | S:type="main/series/subtitle" | Atom:title | S:type="main/series/subtitle" |
Are there alternative constructs available through Yahoo media or iTunesU? If so, list them here:
| yahoo media | attr | iTunesU | attr | PCP | attr |
|---|---|---|---|---|---|
| - |
How is the same xml handled by different systems?
| VirtPresenter | ELAN AP | SURF media | ARCA | IEEE LOM | MPEG7 |
|---|---|---|---|---|---|
| Title |
Further information:
| Obligation | Human readable type | data type | Encoding | URI DC term | Body |
|---|---|---|---|---|---|
| 1-n | Text | Title : subtitle | Http://purl.org/dc/terms/title |
[edit] 4 Edit properties [Edit properties]
warning.png"{{{cssf_ethelementname}}}" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"{{{cssf_itunesu_att}}}" cannot be used as a page name in this wiki. warning.png"{{{cssf_opencast}}}" cannot be used as a page name in this wiki. warning.png"{{{cssf_opencast_att}}}" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"" cannot be used as a page name in this wiki. warning.png"{{{cssf_body}}}" cannot be used as a page name in this wiki.
Page imported from here.
