Re: [dxwg] A short token to specify a profile may be used as long as there is a discoverable mapping from it to the profile's identifying URI [ID5] (5.5) (#290)

OK here's one (separate from the one I will implement)

  https://github.com/UKGovLD/ukl-registry-poc/wiki/Api

The OGC definitions server is based on a thing called the Linked Data API 
which is also deployed on UK and Australian infrastructures:
https://documentation.ands.org.au/display/DOC/Linked+Data+API

Nick can point to Australian Government Linked Data WG practices which are different again.

Taking a slightly wider scope beyond simple URI based mechanisms, many Web Services support something similar.  A Case in point are OGC Web Services - which offer a GetCapabilities method which return a list of resources that can be asked for by token.  (Map layer, Feature Type) etc.  One of the limitations of these is that they dont usefully distinguish between when these tokens respresent different objects or alternative views of the same object - and improving that situation is a key motivation for profiles description work, and the use of conneg to map such tokens to URIs means we can make such services self-describing without forcing rewrite of those specifications which are adopted as standards in ISO, EU legislation etc,





-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-526421320 using your GitHub account

Received on Friday, 30 August 2019 01:38:11 UTC