About Shared Structures

Introduction

These data structures are shared between many endpoints, within the main response.

Data Structures

Activities - Creations, Publications, Births/Deaths and other activities which are embedded in the main entity's record
Digital Links - Links to other digital content such as web pages and images
Dimensions - Dimensions of the resource with a given unit and type (e.g. 20 inches wide)
Identifiers - Identifiers for the resource (e.g. Accession Number of 1997-1234)
Monetary Amounts - Monetary amounts in a given currency (e.g. 10000 US Dollars)
Names - Names in a human language that have been given to the resource (e.g. Mona Lisa in English)
Rights - Structured rights assertions for licenses or property rights
References - References to another entity in the system (e.g. the reference from a painting to the artist's information)
Statements - Human readable texts that describe the resource (e.g. a Materials statement)
TimeSpans - Spans of time, with fuzziness at each end (e.g. 1950 to 1955)
Types / Concepts - References to types that further clarify the entity (e.g. Painting rather than Object)
Relationships - Relationship assignments between entities (e.g. related works, family relations)

Contexts and URIs

Note that data structures embedded within the records available from endpoints do not have their own @context entries, as they use the context document from the main record. If the data structure is shared separately using the linked art format, then it MUST have the @context reference added.

If there is a data structure which is typically completely embedded within another record, such as a Dimension or a Name (not a reference to another record), that has its own URI given in id at which data can be retrieved, and there is more information there about the entity, then the structure in the linked art record MUST have a property called _complete with the value of false. This will enable consumers of the data to know that it could be valuable to retrieve the data from the URI given in the id field. Otherwise, the expectation is that the URI in id is informational only.

{
  "@context": "https://linked.art/ns/v1/linked-art.json",
  "id": "https://linked.art/example/object/3",
  "type": "HumanMadeObject",
  "identified_by": [
    {
      "id": "https://linked.art/example/Name/0",
      "type": "Name",
      "classified_as": [
        {
          "id": "http://vocab.getty.edu/aat/300404670",
          "type": "Type",
          "_label": "Primary Name"
        }
      ],
      "content": "Hacha",
      "language": [
        {
          "id": "http://vocab.getty.edu/aat/300389311",
          "type": "Language",
          "_label": "Spanish"
        }
      ]
    }
  ]
}

graph TD classDef object stroke:black,fill:#E1BA9C,rx:20px,ry:20px; classDef actor stroke:black,fill:#FFBDCA,rx:20px,ry:20px; classDef type stroke:red,fill:#FAB565,rx:20px,ry:20px; classDef name stroke:orange,fill:#FEF3BA,rx:20px,ry:20px; classDef dims stroke:black,fill:#c6c6c6,rx:20px,ry:20px; classDef infoobj stroke:#907010,fill:#fffa40,rx:20px,ry:20px classDef timespan stroke:blue,fill:#ddfffe,rx:20px,ry:20px classDef place stroke:#3a7a3a,fill:#aff090,rx:20px,ry:20px classDef event stroke:#1010FF,fill:#96e0f6,rx:20px,ry:20px classDef literal stroke:black,fill:#f0f0e0; classDef classstyle stroke:black,fill:white; O1(object/3) class O1 object; O1-- type -->O1_0[HumanMadeObject] class O1_0 classstyle; O2(Name/0) class O2 name; O2-- type -->O2_0[Name] class O2_0 classstyle; O3(aat:300404670) class O3 type; O3-- type -->O3_0[Type] class O3_0 classstyle; O3-- _label -->O3_3("''Primary Name''") class O3_3 literal; O2-- classified_as -->O3 O2-- content -->O2_4("''Hacha''") class O2_4 literal; O4(aat:300389311) class O4 type; O4-- type -->O4_0[Language] class O4_0 classstyle; O4-- _label -->O4_3("''Spanish''") class O4_3 literal; O2-- language -->O4 O1-- identified_by -->O2

Other Representations: JSON-LD (raw) | JSON-LD (playground) | Turtle (raw) | Turtle (styled)