In-house usage scenarios - Revision history

Dbalzer at 08:34, 22 May 2011

2011-05-22T08:34:15Z

Dbalzer at 22:49, 20 May 2011

2011-05-20T22:49:10Z

Dbalzer at 22:19, 20 May 2011

2011-05-20T22:19:40Z

Dbalzer at 20:39, 20 May 2011

2011-05-20T20:39:12Z

Dbalzer at 20:10, 20 May 2011

2011-05-20T20:10:04Z

Dbalzer at 18:05, 20 May 2011

2011-05-20T18:05:06Z

Dbalzer at 14:38, 20 May 2011

2011-05-20T14:38:54Z

Dbalzer: Created page with "''From the TC 372 Workshop Compendium'' Why is it that most cinematheques collect various things in addition to moving images? {| style="float: right; border: 1px solid #BB..."

2011-05-20T07:56:39Z

Created page with "''From the TC 372 Workshop Compendium'' Why is it that most cinematheques collect various things in addition to moving images? {| style="float: right; border: 1px solid #BB..."

New page

''From the [[TC 372 Workshop Compendium]]''

Why is it that most cinematheques collect various things in addition to moving images?

{| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
|-
| valign="top" width="405px" |[[File:Event-metadata.png|400px]] 



| valign="top" width="405px" |
Taking the idea of '''events as connectors''' a bit further, we could envision a resource that allows us to uniquely identify events. Such a resource would resemble what librarians call an ''authority file''.

Using a publicly available '''identifier for the''' Basel film '''festival''' would allow machines to find other resources referring to this event. This could be other films shown at the festival, posters like the one seen in the previous session, or any other materials such as press articles or photographs.
|}

{| height="20px" width="100%"
|- style="text-align:center; "
| • Previous: [[Relationships with objects in other databases]] • Up: [[TC 372 Workshop Compendium|Contents]] • Next: [[....]] • 
|-
|}

@@ Line 52: / Line 52: @@
 References and Materials: In-house usage scenarios
 * [http://linkeddatabook.com/editions/1.0/ The Linked Data Book. Explains how to publish linked data.]
 |}

@@ Line 32: / Line 32: @@
 | valign="top" width="405px" |[[File:Reisestecker-b.jpg|400px]]<br />
 <span style="font-size:8pt">
 </span>
@@ Line 42: / Line 43: @@
 '''Enrich your metadata''' with relationship statements. Use publicly available vocabularies for relationship types, and URIs for relationship targets.
 |}

← Older revision		Revision as of 22:19, 20 May 2011
Line 26:		Line 26:

	At present, the DNB catalogue is not as link-friendly as it could be. If it were capable of supplying the catalogue record in '''RDF''', then standard software tools could immediately '''explore further paths''', e.g. retrieving the authority record for the author ([http://d-nb.info/gnd/142990698 http://d-nb.info/gnd/142990698]).		At present, the DNB catalogue is not as link-friendly as it could be. If it were capable of supplying the catalogue record in '''RDF''', then standard software tools could immediately '''explore further paths''', e.g. retrieving the authority record for the author ([http://d-nb.info/gnd/142990698 http://d-nb.info/gnd/142990698]).
		+	\|}
		+
		+	{\| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
		+	\|-
		+	\| valign="top" width="405px" \|[[File:Reisestecker-b.jpg\|400px]]<br />
		+	<span style="font-size:8pt">
		+	</span>
		+
		+	\| valign="top" width="405px" \|
		+	How can we make a catalogue link-friendly?
		+
		+	'''Define a Uniform Resource Identifier''' (URI) for each unit of information (e.g. catalogue record, or part thereof). Make sure that the URI can remain stable over a long period of time.
		+
		+	'''Let a Web server respond''' to a HTTP URI request with the set of associated metadata (e.g. a catalogue record). Observe the rules of the game and use an agreed data model (i.e. RDF) and offer a choice of recommended encodings (XML, N3/Turtle, and something human-readable).
		+
		+	'''Enrich your metadata''' with relationship statements. Use publicly available vocabularies for relationship types, and URIs for relationship targets.
	\|}		\|}

@@ Line 5: / Line 5: @@
 {| style="float: right; border: 1px solid #BBB; margin: .46em 0 0 .2em;"
 |-
-| valign="top" width="405px" |[[File:Event-metadata.png|400px]]<br />
+| valign="top" width="405px" |[[File:Krimskrams.jpg|400px]]<br />
 <span style="font-size:8pt">
 </span>

@@ Line 31: / Line 31: @@
 {| height="20px" width="100%"
 |- style="text-align:center; "
-|<span style="color:#808080"> • Previous: [[Relationships with objects in other databases]] • Up: [[TC 372 Workshop Compendium|Contents]] •  Next: [[....]] • </span>
+|<span style="color:#808080"> • Previous: [[Relationships with objects in other databases]] • Up: [[TC 372 Workshop Compendium|Contents]] •  Next: [[Filmographic information in the ocean of data]] • </span>
 |-
 |}

@@ Line 10: / Line 10: @@
 | valign="top" width="405px" |
-Why is it that most cinematheques collect various things in addition to moving images? It is because we tend to think of '''cinema''' as something that '''is embedded in a cultural context'''. How can we make our catalogues and other knowledge tools reflect this context?
+Why is it that most cinematheques collect various things in addition to moving images?
 |}
 {| height="20px" width="100%"