Published on

Subj3ct is a directory service for the Semantic Web. Subj3ct provides tools for registering and discovering identifiers for subjects and for linking subjects to related information.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Use the first one to find more related identifiers or resources for a given subject identifier
    Use the second one to find the identifiers that reference a given resource as a representation
    Use the third one to support identifier discovery (e.g. When classifying new resources)
  • Subj3ct

    1. 1. NetworkedPlanet Subject Identity Resolution Service
    2. 2. What is meaning, what are semantics?
    3. 3. Semantics
    4. 4. Semantics
    5. 5. Agreement in computing
    6. 6. Service for Managing this... Store identifiers, with names and descriptions Store equivalence between identifiers
    7. 7. Providing an Identifier Feed (Subject Identifier Aggregator) Wikipedia Bob’s Feed Organisations that want to expose subject identifiers can publish an ATOM feed..
    8. 8. Providing an Identifier Feed TRUST and PROVENANCE
    9. 9. Using the Service Developers can use it to look up identifiers for things they want to talk about in their code. Places for example, or people, or anything really. Machines can use it to retrieve Subject Identity Records that can be used to find equivalent identifiers AND links to other online structured information about a subject.
    10. 10. Using The Portal • Without an account – Full Text Search: – Display Information about a Subject: com%2Fpsi%2Ftechquila%2F%23kal_ahmed – Follow new feed and subject registrations: • • – Anonymous Feed Registration • With an account – Namespace Registration – Feed Registration – Personal Subj3ct identifier namespace
    11. 11. Providing an ATOM Identifier Feed Documentation: Sample: <entry> <title>{SUBJECT NAME}</title> <id></id> <updated>2003-12-04T14:39:10Z</updated> <summary> {SUBJECT DESCRIPTION} </summary> <link rel="SubjectIdentifier" href="{SI URI}" /> <link rel=“SubjectEquivalence” href=“{EQUIV URI}” /> <link rel=“SubjectRepresentation” href=“{RESOURCE URI}” /> </entry>
    12. 12. Providing a SKOS Identifier Feed Documentation: Sample: <skos:Concept rdf:about=“{SI URI}"> <skos:prefLabel>{SUBJECT NAME}</skos:prefLabel> <skos:definition> {SUBJECT DESCRIPTION} </skos:definition> <skos:exactMatch rdf:resource=“{EQUIV URI}” /> <skos:subjectIndicator rdf:resource=“{RESOURCE URI}” /> </skos:Concept>
    13. 13. Registering A Feed 1. Create a Subj3ct account 2. Register a namespace URI 3. Validate your ownership of the namespace 4. Register the URI of your feed OR 1. Register the URI of a feed anonymously Documentation:
    14. 14. Creating Identifiers Manually • Every registered Subj3ct user has their own namespace ( • Create as many identifiers as you like under this namespace Documentation:
    15. 15. API • Retrieve subjects – By Identifier:{identifierUri}&provenance={pr ovenance} – By Resource:{representationUri}&s kip={skip}&take={take} – By Query{query}&skip={skip}&take= {take} – Formats: XML, JSON (including support for JSONP callback), SKOS RDF, XTM 1.0, ATOM, RSS 2.0 Documentation: Method Listing:
    16. 16. The Small Vision provides a common service for searching and getting identifiers that can be used to tag up content produced in CMS systems. EPiServer, SharePoint etc.... Javascript used in the rendering of ‘tagged’ pages can connect to the subj3ct service to show links to related subjects and also link to online content about the same subject (Representation links)
    17. 17. The Grand Vision Subj3ct as the DNS of the semantic web. Web 3.0 is about publishing data online. Clients will grab fragments of data, and from URLs in that data pull other data. URIs are used as Addresses and Subject Identifiers provides a way to go from subject identifiers to addresses for relevant semantic content The next generation web will not be HTML and Google it will be RDF/Topic Maps and