Objects: Digital Integration

Table of Contents

Up: Objects

Introduction

It is very unlikely that the descriptions provided in this model are the only digital representations of the objects. For building human readable representations, or just for linking to existing web pages, these other digital resources should be referenced.

Image

The most common scenario is if there are one or more images available of the object. This is described by using the representation property, which has a VisualItem as its value. The id of the image is the URI at which it is available, and additional properties to describe the image should also be given, such as a label and its media type (sometimes called a MIME type) in format. The digital image should be classified as such using aat:300215302.

{
  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/39", 
  "type": "ManMadeObject", 
  "label": "Painting", 
  "classified_as": ["aat:300033618","aat:300133025"], 
  "representation": [
    {
      "id": "http://example.org/images/image.jpg", 
      "type": "VisualItem", 
      "label": "Image of Painting", 
      "classified_as": ["aat:300215302"], 
      "format": "image/jpeg"
    }
  ]
}

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)

Home Page

Another very common scenario is that there is a web page about the object, perhaps managed by a collections management system. For humans, this page is much more useful than the data intended for machines. It can be referenced with the subject_of property, and points to a LinguisticObject which is classified_as a web page, or aat:300264578 as well as being preferred (aat:300404670). As with digital images, the homepage should have a format of "text/html", the media type for HTML.

{
  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/40", 
  "type": "ManMadeObject", 
  "label": "Painting", 
  "classified_as": ["aat:300033618","aat:300133025"], 
  "subject_of": [
    {
      "id": "http://example.org/collection/1/painting", 
      "type": "LinguisticObject", 
      "label": "Homepage for Painting", 
      "classified_as": ["aat:300264578","aat:300404670"], 
      "format": "text/html"
    }
  ]
}

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)

Other Pages

While the publishing organization might have a home page for their object as above, there are likely to be many other web pages about the object as well in different systems. These pages follow the same model of being a LinguisticObject, but without the preferred classification.

{
  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/41", 
  "type": "ManMadeObject", 
  "label": "Painting", 
  "classified_as": ["aat:300033618","aat:300133025"], 
  "subject_of": [
    {
      "id": "http://example.org/journal/article", 
      "type": "LinguisticObject", 
      "label": "Webpage that discusses Painting", 
      "classified_as": ["aat:300264578"], 
      "format": "text/html"
    }
  ]
}

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)

IIIF

IIIF, the International Image Interoperability Framework, is an increasingly common way to make images and descriptions intended to be displayed to humans available. There are two primary alignments with the CRM model, which mirror the above Image and Web Page patterns.

IIIF Images

The IIIF Image API in CRM can be considered a VisualItem, even though it is a service for obtaining them, and can thus be referenced with the same representation property. In order to know that the URI is an Image API endpoint, it should not have a format and instead have a conformsTo property with the value "http://iiif.io/api/image". This follows the protocol pattern in IIIF Image Information documents.

{
  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/42", 
  "type": "ManMadeObject", 
  "label": "Sculpture", 
  "classified_as": ["aat:300047090","aat:300133025"], 
  "representation": [
    {
      "id": "http://iiif.example.org/image/1", 
      "type": "VisualItem", 
      "label": "IIIF Image API for Sculpture", 
      "conforms_to": "http://iiif.io/api/image"
    }
  ]
}

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)

IIIF Manifests

The IIIF Presentation API in CRM can be considered an InformationObject that is about the object. The property used to refer to it from the art object is subject_of. It conformsTo the Presentation API URI, but can be given a format for JSON-LD that includes the context as a profile.

{
  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/43", 
  "type": "ManMadeObject", 
  "label": "Painting", 
  "classified_as": ["aat:300033618","aat:300133025"], 
  "subject_of": [
    {
      "id": "http://iiif.example.org/presentation/1/manifest.json", 
      "type": "InformationObject", 
      "conforms_to": "http://iiif.io/api/presentation", 
      "format": "application/ld+json;profile=\"http://iiif.io/api/presentation/2/context.json\""
    }
  ]
}

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)