This document defines two namespaces of URNs, based on using a
timestamp with an (encoded) URI. The results are namespaces in which names
are readily assigned, offer the persistence of reference that is
required by URNs, but do not require a stable authority to assign
the name. The first namespace ("duri") is used to refer to
URI-identified resources as they appeared at a particular time. The
second namespace ("tdb") is useful as a way of creating URNs that
refer to physical objects or even abstractions that are not
themselves networked resources.

The definition of these namespaces may reduce the need to define new
URN namespaces merely for the purpose of creating stable
identifiers.

Scalable Highly Expressive Reasoner

A technology that provides ontology analytics (OWL-DL without nominals) over highly expressive ontologies.

The Neurocommons project seeks to make all scientific research
materials - research articles, annotations, data, physical materials - as available and as useable as they can be.
We do this by both fostering practices that render information in a form that promotes uniform access by computational agents - sometimes called "interoperability". We want knowledge sources to combine meaningfully, enabling semantically precise queries that span multiple information sources.

Our work covers general data and knowledge sources used in computational biology as well as sources
specific to neuroscience and neuromedicine.
The practices that we develop and promote are designed to play well on the Semantic Web. We view our technical work not as creating a new service or content library, although we do both, but rather as helping to promote the growth of semantically linked scientific information.

How should one go about finding documentation that will explain what a URI names, in cases where this is needed and it is not already at hand? HTTP was not designed to help out here, so the following is not as elegant as would be a protocol designed with this in mind.

If you're doing bulk processing of URI documentation, you may be better off doing bulk downloads or SPARQL queries on an appropriate SPARQL endpoint, as large numbers of probes will be inefficient and will load servers, usually unnecessarily.

The following protocol is designed to be forgiving enough to grandfather many URIs already in use on the Semantic Web, such as those in the RDF Schema vocabulary and Dublin Core, while strict enough to support our URI requirements. It coincides with HTTP in the absence of overrides, responses containing a Location: header, and 200 responses.