Adding and editing image annotations

• Adding and editing image annotations
  • Formats supported for importing
    • W3C Web Annotation Data Model (WADM)
    • Common Objects in Context (COCO)
    • VGG Image Annotator (VIA)
• Viewing the resulting annotations

¶Adding and editing image annotations

Image annotations can be added or edited from this page: https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/add. First, upload a file containing annotations (see below for which file formats are supported). Then, confirm that the file was parsed correctly. Afterwards, add metadata to your annotations by describing the work that was done, and adding associated authors and projects.

¶Formats supported for importing

¶W3C Web Annotation Data Model (WADM)

JSON imports following the W3C Web Annotation Data Model are supported, but should conform to the following restrictions, as linked data is not yet supported in full:

• All keys should be prefix-less and follow the @context used in the examples of the W3C specification.
• The top-level value can be an AnnotationCollection object, an AnnotationPage object, or an array or object with individual annotations as values. In the case of AnnotationCollection objects, only the annotations included in the file are imported.
• Individual annotations should have one and only one target. This target should have a source consisting of the URL of the CDLI image you are annotating (e.g. /dl/photo/P123456.jpg). This target should have a single selector of the type SvgSelector. Preferably, use only <polygon>, <circle>, <ellipse>, and <path>, and do not use attributes like transform.
• Individual annotations should have at least one body but may have more. These bodies should have the type TextualBody or SpecificResource. The bodies may have any or no purpose. Bodies may additionally have a value and/or a source.
• Individual annotations may have a license.
• In the case an existing annotation should be updated, the id (@id) should be the URL of the existing annotation (https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/123 where 123 is the numeric ID of the annotation).

The fields created, modified, and creator are not supported for importing, and instead are filled in from the update event(s) associated with the annotations.

{
  "@context": "http://www.w3.org/ns/anno.jsonld",
  "id": "https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/123",
  "type": "Annotation",
  "body": [
      {
          "type": "TextualBody",
          "value": "crudely inscribed",
          "purpose": "commenting"
      },
      {
          "type": "SpecificResource",
          "value": "vase",
          "source": "https://www.wikidata.org/wiki/Q191851",
          "purpose": "tagging"
      }
  ],
  "target": {
    "source": "https://cdli.mpiwg-berlin.mpg.de/dl/photo/P123456.jpg",
    "selector": {
      "type": "SvgSelector",
      "value": "<svg> ... </svg>"
    }
  }
}

¶Common Objects in Context (COCO)

Support for the Common Objects in Context (COCO) data format is pending.

¶VGG Image Annotator (VIA)

Both VIA project files and VIA annotation JSON files can be imported.

• To edit existing annotations, a text field named @id is used containing the full URL of the annotation.
• Four fields are imported, classifying, identifying, describing, and assessing, corresponding to the W3C purposes of the same name. These fields are expected to be radio buttons or checkboxes, with URIs to the Art & Architecture Thesaurus (AAT) vocabulary as the option identifiers. If no term is available, the option identifier should be a non-URI label.
• If a VIA project is uploaded, labels corresponding to the URIs will be extracted from there.

¶Viewing the resulting annotations

When an update event is accepted, you can click on the link in the column titled "Visual asset" to view the image and its associated annotations.