From Steeple

Contents 1 Description of abstract element: ID 2 Discussion of id [add to discussion,edit discussion] 2.1 Do we need multiple identifiers? 2.2 Os Solution 2.3 series id vs. item id 3 Expression of id in various schemes [Edit properties] 4 Edit properties [Edit properties]

[edit] 1 Description of abstract element: ID

The identifier of the resource. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system

2 Discussion of id [add to discussion,edit discussion]

[edit] 2.1 Do we need multiple identifiers?

One of the problems is that the identifiers may be local, in that sense we have a problem using an rss:guid ar an atom:id in this place. So we may need an <o:id domain="..."></o:id> type element. I.e. if a feed from ETH gets aggregated, the aggregator might have "ETH-123456" as id for the element, but ETH may have 123456

<rss:guid>ETH-123456</rss:guid>
<o:id domain="ETH">123456</o:id>

(of course the two ids may be completely unrelated).

OAS: This neatly leads to the question whether persistent identifiers could be (one of) the identifiers: At least in the DOI world, a local prefix is part of the string. On the issue of having two (or more) ID, it certainly plays a role whether you work with a local handle and/or a registered one like DOI.

Bjoern 11:13, 16 September 2009 (UTC): Just to add some more thoughts: The <o:id> would be something that is passed 'up' to the syndication engine. It's really for situations where a local guid is not suitable for the aggregator, and so allows the institution to pass a different id to the syndication engine (the format of which is specified by the syndication engine). It might be <o:id>ox.ac.uk/something</o:id>.

Bjoern 15:41, 28 October 2009 (UTC): Update. Steeple now includes <s:id domain="...">id</s:id>, see http://purl.org/steeple/s:id

[edit] 2.2 Os Solution

We use an lecture recordings system identifier, it's: <administration server url>/lecutre/id to get not in trouble with identifier from different systems Nbirnbaum 14:48, 16 September 2009 (UTC)

[edit] 2.3 series id vs. item id

c.f. "latest episodes" feed witll nned series id at item level. Bjoern 14:54, 16 September 2009 (UTC)

3 Expression of id in various schemes [Edit properties]

As xml in Matterhorn xml and rss/atom:

<Dcterms:identifier> ... id ... </Dcterms:identifier>
<Rss:guid IsPermaLink="false"> ... id ... </Rss:guid>
<Atom:id> ... id ... </Atom:id>

Full table:

name	number	MH xml	RSS (with Yahoo/Steeple)	attributes	Atom (with Yahoo/Steeple)	attr
ID	11	Dcterms:identifier	Rss:guid	IsPermaLink="false"	Atom:id

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
Object id, series id	Identifier	-	-	-	-

Further information:

Obligation	Human readable type	data type	Encoding	URI DC term	Body
1-n	-	Text	1. handle, 2. DOI	Http://purl.org/dc/terms/identifier

[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"{{{cssf_body}}}" cannot be used as a page name in this wiki.