Modelling annotations on Metadata Descriptions

Hi all,

There is another "category" of annotations that I would like to discuss and ask for your help.

In my early emails, I have mentioned scenarios for which the end-user makes annotations that target the object as a whole... this is the case for the annotations that we obtain for example from HistoryPin.org.

As part of our new portal (here is a glimpse btw on how it will look like http://test.europeana.eu/ ), we want to allow users to also contribute with (suggestions for) changes that will target the actual metadata description of our object by correcting the metadata fields or adding new fields to the object, or even, adding contextual information to the text within the fields (through comments, tags or semantic tags). btw, we are working with the team from the Pundit semantic annotation tool ( http://thepund.it/ ) for the portal side support.

However, we would like to represent these annotations in a way that is agnostic to how the metadata is presented/rendered in the portal so that:

  *   they survive changes to the portal design;
  *   we can allow them to be easily shared outside our portal;
  *   other software applications can take further advantage it.

I have tried to fold our requirements into 3 use cases that we wish to support and model using WebAnnotation, and which I am presenting below. btw, the URIs such as http://data.europeana.eu/item/09102/_UEDIN_214  identify the real world object in the LD sense.

Use Case 1: A end-user suggests a new value (a DBpedia resource, namely http://dbpedia.org/resource/Brass_instrument ) for the "dc:type" metadata field of the object (http://data.europeana.eu/item/09102/_UEDIN_214 ).

Notes:
- the motivation oa:editing was selected but perhaps oa:describing could be a better fit?
- the @graph as body was chosen to distinguish between the context of the annotation/suggestion from the context of the object description, otherwise the suggested statement would immediately be part of the object description (smushed).

{
  "motivation": "oa:editing",
  "target": "http://data.europeana.eu/item/09102/_UEDIN_214",
  "body": {
    "@graph": {
      "@id": "http://data.europeana.eu/item/09102/_UEDIN_214",
      "dc:type": { "@id": "http://dbpedia.org/resource/Brass_instrument" }
    }
  }
}

Use Case 2: The value "ca. 1840" was suggested by an end-user as replacement for the existing dc:date field with the value "Circa 1840" of the object (http://data.europeana.eu/item/09102/_UEDIN_214 ).

Notes: We did not find a selector that could specifically target a RDF statement so we created a new one pundit:MetadataSelector.

{
  "motivation": "oa:editing",
  "target": {
    "@type": "oa:SpecificResource",
    "source": "http://data.europeana.eu/item/09102/_UEDIN_214",
    "selector" {
      "@type": "pundit:MetadataSelector",
      "rdf:predicate": "dc:date",
      "rdf:value": "Circa 1840"
    }
  },
  "body": {
    "@graph": {
      "@id": "http://data.europeana.eu/item/09102/_UEDIN_214",
      "dc:date": "ca. 1840"
    }
  }
}

Use Case 3: The dc:coverage field of the object (http://data.europeana.eu/item/09102/_UEDIN_214) was found as incorrect by an end-user which suggests it to be disregarded.

Notes: I miss a special motivation that can explicitly state that the purpose of the annotation is to disregard that particular statement. If oa:editing is understood as a good match for the motivation, an option could be to narrower it into the following three actions: oa:adding, oa:changing, oa:removing.

{
  "motivation": "oa:editing",
  "target": {
    "@type": "oa:SpecificResource",
    "source": "http://data.europeana.eu/item/09102/_UEDIN_214",
    "selector" {
      "@type": "pundit:MetadataSelector",
      "rdf:predicate": "dc:coverage",
      "rdf:object": "Probably France"
    }
  },
  "body": {
    "@graph": {}
  }
}

Looking forward for you input!

Thanks in advance!

Kind 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.