A USGIN profile of the IETF RFC 3986 (URI) standard.

USGIN URI Management

Implementation Type: 

This web-application intends to make it easy to create, update and manage an online registry of URIs that conform to the USGIN URI Scheme. The application provides resolution of the URIs to web-accessible URLs, and in the future, we intend to allow for full content-negotiation through HTTP headers (accept). The application is built using Django, and the code behind the application as well as simple instructions for installation into an existing Django project are available for free at GitHub:

While the application is still in development, a sample server is running at It will resolve some simple URIs listed below:

USGIN URI recommendations v1.0

Document Information
Profile Version: 
Implementation Specification
Document ID: 

First public release of the USGIN URI Policies document.

This document presents a proposal for minting of dereferenceable http URIs for use in interoperable web ser-vices. The design approach is to explicitly distinguish the dereferencing host from the name authority, recognizing that these may be decoupled. Content negotiation and url redirection that are invisible to the user violate the requirement for URI transparency. One of the objectives of this URI scheme is to define a syntax that makes clear the distinction between an identifier for a non-information resource, information resource and specific representation resource to address the issues raised by Booth (2003-01-28). Another important design criterion is that the http URIs should be dereferenceable using standard web server resource path conventions on any commonly used operating system, in order to make implementation of dereferencing as simple as possible. The ABNF syntax can be summarized as:

ginURI = "http:" "//" uriHost “/” URIscheme “/” nameAuthority “/”

resourcePath [“/” resourceSpecificString] [( “/” / “/” representationPart )]

USGIN Uniform Resource Identifier

Recommendations for usage and coining of Uniform Resource Identifiers (URI) in the U.S. Geoscience Information Network.


More links: URI discussion

Commentary on identifying wells

Discussion of concept identifier vs. document (representation) identifier

URL Design (Kyle Neath), and follow up from Jeni Tennison. Most of this discussion applies to any http URI.

UK guidance on creating URIs

Syndicate content