Specifications

OpenDiscovery relies on the mutual reference between the public record of a legal entity in its authoritative business register and a URL providing self-asserted or third party validated information about the entity and its services.

So far the national business registers of Denmark, Norway, Finland, and New Zealand have enabled legal entities to reference a URL in their public records.

The default OpenDiscovery method for an entity to refer back to its official records and to voluntarily provide further reference to its services is using .well-known [RFC5785] with the requested IANA URI suffix "opendiscovery" to locate the files:

host.json referencing the internationalized BusinessID
(example: https://www.peercraft.com/.well-known/opendiscovery/host.json)

[BusinessID].json containing (reference to) self-asserted and/or third party validated information about the entity
(example: https://www.peercraft.com/.well-known/opendiscovery/DK33755341.json)

Websites with pages representing different legal entities, may insert the HTTP header-field X-OpenDiscovery-ID with the respective BusinessID's as field value to override the BusinessID provided in host.json for these pages.

The purpose of OpenDiscovery is to facilitate the creation of a new data driven ecosystem for exchange of products and services.

An important foundation for this is the use of standardized schemas and taxonomies for the description of businesses and their services. Fortunately most of these are readily available. Examples of standards, schemas, and data sources that will be used to the extent possible are listed in the wiki for the Publisher component.

As the work progresses, this page will be extended to become a specification overview and placeholder for relevant links to individual more specific parts of the OpenDiscovery specifications.