2. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Problem
given a topic identity
subject identifier
subject locator
item identifier
give me everything you know about that topic
names, occurrences, associations
not: other axes (all constructs where this topic is type of)
only direct neighbours
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 2 of 10
3. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Use cases
Linked data
browse huge (inferred) topic maps
e.g. information on all proteins ever discovered
Web 3.0 (e.g. Browse remote Topic Maps in Maiana)
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 3 of 10
4. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Request
Use HTTP GET
One base URI
e.g. “http://browse.foo.com/somemap/browse”
3 query parameters
“sid”: topic identified by subject indicator
“slo”: topic identified by subject locator
“iid”: topic identified by item identifier
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 4 of 10
5. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Example Request
GET /somemap/browse?slo=urn:isbn:978-3-540-71944-1
Host: browse.foo.com
Accept: application/tm+xml; version=2.1
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 5 of 10
6. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Response
either: HTTP 204 No Content
in case the topic is not found in the map
or: HTTP 200 OK
a topic map fragment around the topic
with additional “next link” data
in the data format desired:
application/tm+xml
text/ctm
text/html
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 6 of 10
7. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Next link data
each topic, before transferring to the client, receives
an additional occurrence by the server
type: “more-information-at”
value: TMBrowseProtocol-URL
datatype: IRI
This occurrence should be filtered out by the client
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 7 of 10
9. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Conformance by servers
Support at least these media types:
application/tm+xml
text/ctm
text/html
Properly interpret the “Accept” header (according to
the HTTP/1.1 standard)
HTML is for a user manually browsing
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 9 of 10
10. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Conformance by clients
Properly specify the desired media type in the
“Accept” header
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 10 of 10
11. TMRA 2009: Openspace Session Friday: TMBrowse Protocol
2009-11-13
Kills subj3ct.com?
It is possible to deliver more than 1 “more-
information-at” occurrence per topic
for everyone
Sorry Graham ☺
Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org>
Lutz Maicher <maicher@informatik.uni-leipzig.de> 11 of 10