What is the root URL for each AAC Partner?

Priority 2, Best Practice Established

Problem Statement

One of the fundemental questions for Linked Data is what namespace you will use when creating URLs to reference entities that you wish to state.

For the AAC, we need to define what root domain we will use for AAC Partner data.

Best Practice:

Each institution identifies their own domain to use in the RDF.

Pick a domain that you will use for your LOD identifiers. It should be one that you can either manage or delegate, but that you retain control over. This doesn’t mean you need to host the data — but you do need to control the domain. In order for this to work, it needs to be a distinct DNS-routable address for your LOD (not just your main website domain URL). Either:

  • A discrete subdomain (e.g. data.thewalters.org)
  • A completely separate domain (e.g. thedigitalwalters.org)

This allows you to control the DNS (the address, a domain name, and where in the world it is pointing), but delegate the handling of the information. In the short term, the RDF information can be handled, hosted, and managed by ISI — you just create a single DNS entry that points from your address to their server. In future, when your own servers (or some different group/host) hold the information, the address is repointed there. Inside the RDF, the domain remains persistent.

For those institutions with existing LOD URLs (SAAM, YCBA…), they should remain the same — the AAC RDF will use them directly. The goal for this is that if a user dereferences the URL, data is returned: http://collection.britishart.yale.edu/id/object/499 already does this, so we don't need to do anything for the AAC here. For institutions without RDF data, our assumption is that ISI will spin up a HTML/RDF instance for them during the course of this project. What we recommend is those URLs to be owned by the institution, not AAC.

Discussion:

Reference:

Linked Open Data FAQs

Defining Types

How do I specify types for entities?
Priority 1
✔ Best Practice Established
How do I specify types for predicates?
Priority 1
✔ Best Practice Established
What existing extensions to the CIDOC-CRM should I use?
Priority 2
✔ Best Practice Established

Defining URL Structures

What URL should I use for unknown Actors?
Priority 2
✔ Best Practice Established
What is the root URL for each AAC Partner?
Priority 2
✔ Best Practice Established
What is returned when a URL is dereferenced?
Priority 3
✔ Best Practice Established
Which ID is most appropriate for URL construction?
Priority 3
✔ Best Practice Established

Labeling

What are best practices for modeling text strings?
Priority 2
✔ Best Practice Established
What is best practice for labeling external authorities?
Priority 3
✔ Best Practice Established
How do I handle strings in languages other than english?
Priority 4
✔ Best Practice Established

Modeling

How do I handle complexity in knowledge representation?
Priority 1
✔ Best Practice Established
How do I model lists of entities or multiple values?
Priority 2
✔ Best Practice Established
How should I model parts of Actor names?
Priority 2
✔ Best Practice Established

Reconciliation

How do I reconcile objects to authorities?
Priority 2
✔ Best Practice Established
Which entity should I link to in an authority file?
Priority 2
✔ Best Practice Established

Triplestores, RDF, and Inferencing

Which namespace should I use for the CIDOC CRM as LOD?
Priority 1
✔ Best Practice Established
How do I create an RDF representation of an entity?
Priority 3
✔ Best Practice Established
Where should AAC-created vocabularies be hosted?
Priority 3
✔ Best Practice Established
What serialization of RDF should I publish?
Priority 4
✔ Best Practice Established