Keep in mind not to use service endpoint URLs (WHY NOT?)

Read [DWBP] Best Practice 11: Use persistent URIs as identifiers within datasets for general discussion on why persistent URIs should be used as identifiers for data entities. Using URIs means the data can be referenced using standard Web mechanisms; making them persistent means the links won't get broken. Note that ideally the URIs should resolve, however, they have value as globally scoped variables whether they resolve or not.

For guidance about how to create persistent URIs, read [DWBP] Best Practice 10: Use persistent URIs as identifiers. Keep in mind not to use service endpoint URLs, as these are usually dependent on technology, implementation, and/or API version and will probably change when the implementation changes..


I've seen more changes in vocabulary URIs recently than any change in service endpoints (certainly for OGC standard interfaces).  For example changes from use of URNs to HTTP-URIs forced a whole load of changes in our datasets, then we've had changes in identifying concepts by name over number in HTTP-URIs, then in to and fro decisions to add a date version or not in the URI then in INSPIRE deciding to not use the CGI URIs in favour of its own; it's been constant change.  The OGC web service interfaces have been constant over the same period, it's just incorrect to imply that the standard OGC service interfaces (especially the endpoints) are more liable to change.

James


________________________________
 This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
________________________________

Received on Wednesday, 20 January 2016 14:10:16 UTC