This is the resolvable JSON-LD namespace URI for the Art/Official protocol — what @context points to. It is deliberately kept stable, minimal, and boring. A machine request (Accept: application/ld+json or similar) receives the JSON-LD document itself; a browser receives this page.

/ns/

art-official: namespace — stub, version 0.1

Status: stub

This namespace is newly live and intentionally minimal. It currently documents the term set already in use in the bernardbolter.com reference implementation, under the old artism: prefix, which is being renamed to art-official: now that this URI resolves. That migration (“Phase 4” of the schema reconciliation, described on the schema page and in the updates log) is in progress. Terms below may still gain formal definitions, ranges, and examples; treat this as versioned, working documentation, not a frozen spec.

Content negotiation

Requesting this path with an Accept header of application/ld+json or application/json returns the machine-readable context document below as JSON. Any other Accept header (a normal browser request) returns this human-readable page. Try it:

curl -H "Accept: application/ld+json" https://art-official.org/ns/

Terms in this namespace

Everything below is art-official:-prefixed. Where an adequate schema.org term already exists, it is used instead and does not appear here — see the schema page’s interoperability section for what that split looks like in practice.

Term	Applies to	What it holds
`intent`	Artwork	Artist-stated intent, captured through dialogue — never inferred.
`makingNote`	Artwork	The experience of making this specific piece, kept distinct from intent and inspiration.
`directInspiration`	Artwork	The work’s immediate seed, elicited through specific visual observation rather than direct questioning.
`consciousRejections`	Artwork	Paths deliberately not taken in making the work.
`encounterNote`	Artwork	The blind-description / re-description gap captured near the close of a cataloguing session.
`formalContributionAssessment`	Artwork	A significance assessment, arrived at indirectly rather than asked for directly.
`workContext`	Artwork	Raw evidence of a threshold moment in the practice — a shift, a recognition, a connection surfacing. Evidence only, never a self-assessed claim.
`ProjectEvent`	Practice (proposed)	Corpus readings, threshold recognitions, published dialogues — each requires a statement of exactly what the witness had access to (blind or conditioned, and with what).
`provenanceConfidenceLayer`	Ownership event	Four-level confidence enum (`documented-fact` \| `credible-inference` \| `institutional-assertion` \| `speculation`) attached to a specific claim, not a whole record. See known vocabulary drift noted on the schema page.
`unresolved`	Vision analysis pass	Mandatory field on every blind vision pass — “I don’t know what this is doing but I keep coming back to it,” treated as signal, not gap.
`participationContext`	Corpus / event record	Named in the white paper’s open questions as a proposed mediation-tracking field; not yet implemented in the reference site.
`corpusBiasStatement`	Corpus-level	Named in the white paper’s open questions as a proposed field for stating known corpus-selection bias explicitly; not yet implemented in the reference site.

The JSON-LD context document

This is what a machine Accept: application/ld+json request receives from this same path: an @context block (the term-to-IRI mappings, for anything pointing its own @context at this URI) plus an @graph of RDFS-style self-description — a label, a comment, and (where the reference implementation actually types it that way) a domainIncludes — for every term below. Reproduced here for readability:

{
  "@context": {
    "art-official": "https://art-official.org/ns/",
    "schema": "https://schema.org/",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "label": "rdfs:label",
    "comment": "rdfs:comment",
    "domainIncludes": "schema:domainIncludes",
    "intent": "art-official:intent",
    "makingNote": "art-official:makingNote",
    "directInspiration": "art-official:directInspiration",
    "consciousRejections": "art-official:consciousRejections",
    "encounterNote": "art-official:encounterNote",
    "formalContributionAssessment": "art-official:formalContributionAssessment",
    "workContext": "art-official:workContext",
    "ProjectEvent": "art-official:ProjectEvent",
    "provenanceConfidenceLayer": "art-official:provenanceConfidenceLayer",
    "unresolved": "art-official:unresolved",
    "participationContext": "art-official:participationContext",
    "corpusBiasStatement": "art-official:corpusBiasStatement"
  },
  "@graph": [
    {
      "@id": "art-official:intent",
      "@type": "rdf:Property",
      "label": "intent",
      "comment": "(applies to: Artwork) Artist-stated intent, captured through dialogue — never inferred.",
      "domainIncludes": "schema:VisualArtwork"
    }
    /* ...one entry per term above; full document is served live at this path */
  ]
}

This same term set is also embedded directly as a schema.org DefinedTermSet in this page’s <head> (and on /schema/), as a <script type="application/ld+json"> block — so it’s visible to any crawler reading the HTML normally, not only to a client that sends an Accept: application/ld+json header.

Versioned and dated: v0.1, published alongside this site’s launch. Changes to this namespace will be logged in /updates/, not silently edited.