Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Aggregation Identity & owl:sameAs


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Aggregation Identity & owl:sameAs

  1. 1. Aggregation Identity and owl:sameAs OAI ORE Technical Committee Meeting, Washington, D.C.
  2. 2. Aggregation Identity & owl:sameAs <ul><li>owl:sameAs </li></ul><ul><li>What do we want to say? </li></ul>Title slide photo of Washington Monument by Flickr user AlbinoFlea See Made available under CC Attribution- NonCommercial 2.0 Generic license
  3. 3. owl:sameAs <ul><li>Property defined by Web Ontology Language (OWL) </li></ul><ul><li>States that two URI references refer to the same thing </li></ul><ul><li>Reflects the “no unique name“ assumption of the Semantic Web </li></ul><ul><ul><li>i.e. no assumption that all data creators refer to thing using one name/URI </li></ul></ul><ul><ul><li>multiple data creators may define names/URIs for the same thing (URI Aliases) </li></ul></ul><ul><li>Widely used in “Linked Data” </li></ul>
  4. 4. Identification v Interaction <ul><li>N.B. Dealing here with identification, not interaction </li></ul><ul><li>If I claim Resource:A owl:sameAs Resource:B, then </li></ul><ul><ul><li>My assertion says nothing about (set of) representation(s) for Resource:A and Resource:B available at any time </li></ul></ul><ul><ul><li>Set of representations available for Resource:A may be quite different from set of representations for Resource:B </li></ul></ul><ul><li>And conversely… </li></ul><ul><li>If Resource:A and Resource:B have same set of representations, then </li></ul><ul><ul><li>That alone is not sufficient to support the conclusion that Resource:A owl:sameAs Resource:B </li></ul></ul>
  5. 5. owl:sameAs and Inferences <ul><li>If </li></ul><ul><ul><li>Resource:A owl:sameAs Resource:B </li></ul></ul><ul><li>Then </li></ul><ul><ul><li>Resource:A Prop:P Resource:X => Resource:B Prop:P Resource:X </li></ul></ul><ul><ul><li>Resource:X Prop:P Resource:A => Resource:X Prop:P Resource:B </li></ul></ul><ul><li>e.g. </li></ul><ul><ul><li>Resource:A dc:creator Person:P => Resource:B dc:creator Person:P </li></ul></ul><ul><ul><li>Resource:A dcterms:created “2008-01-14” => Resource:B dcterms:created “2008-01-14” </li></ul></ul><ul><ul><li>ReM:R ore:describes Resource:A => ReM:R ore:describes Resource:B </li></ul></ul>
  6. 6. What do we want to “say”? <ul><li>If the requirement is to say “Aggregation:A and Resource:R are the same resource” (i.e. URIs are aliases, “Aggregation:A aka Resource:R”) </li></ul><ul><li>Then </li></ul><ul><ul><li>Use owl:sameAs </li></ul></ul><ul><ul><li>But providers must bear in mind what that means, i.e. the inferences which follow, and make assertion only where appropriate </li></ul></ul><ul><li>If the requirement is to say “Aggregation:A and Resource:R are different resources, related in some way” (i.e. URIs are not aliases) </li></ul><ul><li>Then </li></ul><ul><ul><li>Need to clarify what that “related in some way” relationship is </li></ul></ul><ul><ul><li>Need to define new ORE property (or select existing property from other vocabulary) </li></ul></ul>
  7. 7. Aggregation Identity and owl:sameAs OAI ORE Technical Committee Meeting, Washington, D.C.