You are here: OGC Public Wiki>Ideas4OGC Web>TopicsTable>TopicOGCNA (revision 2)EditAttach

Topic:OGC Naming Authority:

"Who maintains common infrastructure: the OGC NA registry and resolvers?"

The OGC NA is responsible for many shared identifiers used in OGC work. This critically includes identifiers for conformance classes and identifiers for Coordinate Referencing Systems and Coordinate Transforms. The former are now a required part of OGC standards and may soon become a critical part of service interfaces (wherein services identify their functionality by conformance class identifiers not SERVICE/VERSION pairs.) Thus the OGC NA is becoming a fundamental resource for OGC work, that is 'mission critical infrastructure'.

The OGC NA needs work to successfully act as a name registration authority. Also, the OGC operates the web service as a resolver system; that resolver system needs to be improved. The OGC NA has done amazing work, has done exceedingly professional work, and has a core that is probably very healthy. It appears that the issues are only at the margins, in the documentation of the process, in the access facades, and in the monitoring of the system. The registry system must be clear, the status of the registry documented, the operation of any regsitry service monitored. Similarly, the resolver system must be clear, the cascade of resolvers documented, and the orperation of the resolvers monitored. Critically, there is functionality the OGC promissed to maintain as part of its application to become an IANA approved NA that no longer works. This extra work is no one's formal responsiblity so it is our shared responsibility.

This has been discusssed in the mailing list thread "The use and resolution of HTTP URI at the OGC" on the TC-Discuss list. See and subsequent months.

Note The OGC NA has a plan for a work session during the Frascati TC in the fall of 2013.

Relations to other topics

Related to Topic..., since ...

Possible Actions

=> ACTION: The Board or President should decide if the OGC NA is part of "work critical infrastructure". If it is, the Board and President should work towards ensuring its limitations are addressed by putting resources, that is funds, staff time, or requests to sponsors for work or funds, to address the issues which have not been addressed.

=> ACTION: The OGC must fix the links in the RFC and fix the urn resolver service to honor its committments to IANA and IETF.

=> ACTION: The OGC must put in place a process to maintain these links and resolvers. The OGC should check periodically that the registries contain known URNs of the different types stored in the system. The OGC should monitor that the resolvers are working. Both could be automated.

=> ACTION: Clarify the state of the registry (the tree of responsiblity, the number and type of all identifiers in the registry, the work still to do). The registry must be searchable for a class of identifiers. The proces of responsiblity for entry of new items or fixes of old items should be made clear. If there is a registry service as opposed to a hand operated system, the status of that service should be automatically monitored.

=> ACTION: Complete the registry, notably for the core, legacy elements which are no longer used but must now be maintained.

=> ACTION: Clarify the state of the resolvers (the tree of responsiblity, the cascade of services, the completeness of each). Monior the operational status of the resolver chain.




The Leadership group has not yet discussed this topic.
Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | View wiki text | Edit WikiText | More topic actions...
Topic revision: r2 - 30 Jul 2013, AdrianCuster

This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback