TMBrowse Protocol
Upcoming SlideShare
Loading in...5
×
 

TMBrowse Protocol

on

  • 920 views

 

Statistics

Views

Total Views
920
Views on SlideShare
918
Embed Views
2

Actions

Likes
0
Downloads
2
Comments
0

2 Embeds 2

http://tmra.de 1
http://www.health.medicbd.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

TMBrowse Protocol TMBrowse Protocol Presentation Transcript

  • TMRA 2009: Openspace Session Friday: TMBrowse Protocol 2009-11-13 TMBrowse Protocol Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org> Lutz Maicher <maicher@informatik.uni-leipzig.de> 1 of 10
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • TMRA 2009: Openspace Session Friday: TMBrowse Protocol 2009-11-13 Example Request+Response GET /somemap/browse?slo=urn:isbn:978-3-540-71944-1 Host: browse.foo.com Accept: text/ctm HTTP/1.1 200 OK Content-Type: text/ctm edited(editor: Lars_Marius_Garshol, editee: = <urn:isbn:978-3-540-71944-1>) Lars_Marius_Garshol http://www.garshol.priv.no/ ; more-information-at: http://browse.foo.com/somemap/browse?sid=http://www.garshol.priv.no/ Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org> Lutz Maicher <maicher@informatik.uni-leipzig.de> 8 of 10
  • 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
  • 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
  • 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
  • TMRA 2009: Openspace Session Friday: TMBrowse Protocol 2009-11-13 Finish спасибо (Russian) დიდი მადლობა (Georgian) ‫شكرا‬ (Arabic) 謝謝 (Mandarin) ありがとう (Japanese) ‫רב תודות‬ (Hebrew) ᖁᔭᓇᐃᓐᓂ (Inuktitut) ki'esai (Lojban) Xuân Baldauf <xuan--tmbrowse--2009--tmra.de@academia.baldauf.org> Lutz Maicher <maicher@informatik.uni-leipzig.de> 12 of 10