The Website Is A DigitalObject
The public site is not a container for the artwork. It is one form of the artwork, so the Linked Art layer models it as a DigitalObject with an HTML access point and a human page alternate.
Inspect record →Technical note
A short note on why this project models the website, movement, provenance, collection, and evidence profile the way it does.
Modeling decisions
The technical layer is not backstage infrastructure. It is part of the work's claim: art can be made from the conditions that make art visible, referenceable, collectible, and machine-readable.
The public site is not a container for the artwork. It is one form of the artwork, so the Linked Art layer models it as a DigitalObject with an HTML access point and a human page alternate.
Inspect record →Metaconceptual Art is not represented as if Wikidata or Getty had already canonized it. It is modeled as a local Linked Art Type, then connected outward to broader public authorities.
Inspect record →The records distinguish studio formation, movement origin, early evidence, and the 2026 public linked-data layer. Publication metadata does not overwrite origin chronology.
Inspect record →The project publishes a reusable profile, schema, SHACL shape, fixtures, and validator so future claims can be evaluated rather than merely believed.
Inspect record →Pattern
The project uses local identifiers for its own works and claims, then links outward to Wikidata, Getty vocabularies, IIIF, DCAT, VoID, and Linked Art. This keeps the boundary clear: external authorities are lineage and context, not borrowed certification.
That boundary is especially important for living art. The record can grow as new works, citations, exhibitions, or reception appear without rewriting the past or overstating the present.
Exports
The same modeling logic appears in multiple forms: Linked Art records for cultural heritage systems, schema.org for web agents, VoID/DCAT for dataset discovery, and a small Turtle dump for RDF readers.
Open RDF dump →