W3C home > Mailing lists > Public > public-annotation@w3.org > January 2016

Question on qualified linking between two resources

From: Hugo Manguinhas <Hugo.Manguinhas@europeana.eu>
Date: Mon, 18 Jan 2016 10:23:25 +0000
To: W3C Public Annotation List <public-annotation@w3.org>, public-openannotation <public-openannotation@w3.org>
Message-ID: <6D0598B03E7E9848A4287E110919B4BA01149244@MBX-SRV-P200.wpakb.kb.nl>
Hi all,

We have a question on linking... how can we model an annotation expressing a qualified link between two resources? ... meaning that we would like the user when suggesting that two objects are related to be able to specifically express which kind of relation it is... ideally, using a predicate/property (from an ontology/schema) to state the type/kind of link.

So that the user, for example, could make an annotation linking two similar items together: http://data.europeana.eu/item/09102/_UEDIN_214, a buccin trombone from the University of Edinburgh and http://data.europeana.eu/item/09102/_UEDIN_1000 another object from the same institution... other kinds of relations can be envisioned besides similarity, like derivations, composition, etc.

in a typical scenario for linking, an annotation would look something like this:
{
  "motivation": "oa:linking",
  "body": "http://data.europeana.eu/item/09102/_UEDIN_214",
  "target": "http://data.europeana.eu/item/09102/_UEDIN_1000"
}
... meaning that the resource referenced in the body would be related (linked) to the resource referenced in the target, the way it is expressed also denotes direction which can be relevant for specific relations such as edm:isDerivativeOf.

... but how could we express the type of the relation?

A possible way could be to add yet another body with the type (in this case a SpecificResource referencing to an RDF property), much like a semantic tagging scenario, like so (note that in this case the role is crucial to distinguish the two bodies):
{
  "motivation": "oa:linking",
  "body": [
    "http://data.europeana.eu/item/09102/_UEDIN_214",
    {
      "@type": "SpecificResource",
      "source": "http://www.europeana.eu/schemas/edm/isSimilarTo",
      "role": "tagging"
    }
  ],
  "target": "http://data.europeana.eu/item/09102/_UEDIN_1000"
}
... I am not so keen on this option since the body should be about the target, and in this case the edm:isSimilarTo should be categorizing the relation instead.

Has anyone worked with similar use cases? or have ideas on how this could be modeled?

Thank you in advance!

Best regards,
Hugo

Hugo Manguinhas
Technical R&D Coordinator

T: +31 (0)70 314 0967
M:
E: Hugo.Manguinhas@europeana.eu
Skype: hugo.manguinhas


Be part of Europe's online cultural movement - join the Europeana Network Association: http://bit.ly/NetworkAssociation
 #AllezCulture!
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.
Received on Monday, 18 January 2016 10:23:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:43 UTC