What is it
AKOMA NTOSO 1.0 Schema
Technical Documentation
Document Actions
8.1. Absolute and relative URIs.
| 8 |
Naming Conventions
|
At all levels, the Akoma Ntoso URI belong to the http:// scheme and are normally resolved using mechanisms widely available in browsers and web servers.
All http:// URIs are divided into absolute and relative forms. An absolute form of these URIs starts with the “http://”, which is then followed by an officially registered domain name, and the local part that starts off the first individual “/” character. A relative form of the same URI, on the other hand, has no indication of the scheme, no indication of the domain name, and may have further missing parts at the beginning of the whole string (no missing parts on the end, though). Browsers are able to build the absolute URI corresponding to the relative URI specified in a base resource by adding at the beginning of the provided URI the missing parts that are taken from the URI of the base resource.
In XML manifestations of Akoma Ntoso documents, URIs shall always be expressed in relative forms. This makes all URIs independent of the actual resolution mechanism, and allows for very flexible storage, access and reference mechanisms. This means that all resolution mechanism used to access an Akoma Ntoso document off another Akoma Ntoso document will rely on the same resolution mechanism as the original one, regardless of the resolution mechanism employed to generate the documents themselves.
In particular, we can observe two possible uses of relative URIs:
- References at the WORK and EXPRESSION and MANIFESTATION level need to be specified as relative URIs grounded on the top level. This means that they must start with the “/” character, and must omit only the URI schema and domain name). These references include all legislative references and amendments (e.g., URIs specified in ref or mod elements), all reflective URIs (i.e., the uri elements within the identification elements), all ontology elements (e.g., all elements in the references element).
- Reference at the ExpressionComponent and ManifestationComponent level need to be specified as relative URIs grounded on the corresponding Expression and Manifestation level. This means that they must contain just the name of the resource or (in case of multimedia attachments, see section 5.3) the string “media/” followed by the name of the resource. These references include all specification of schedules and attachments in the attachments section, and all specification of multimedia elements with the img and object elements.