Notes on content of guide

[BrigetteM]

Hi Nick, I've forked the original repo so that I could make changes in a way that was more comfortable for me.
In going through the introduction, it's occurred to me that there is a distinct lens on these guidelines- being guidelines for creation of URIs for a public dataset. Is this intentional? What is the scope of this document (apologies if it becomes more obvious further down and I perhaps have just not seen it)? If you're envisaging a future where we might have URIs for things that are not necessarily public datasets, and rather are URIs that point to vocabularies or thesauri or models of some kind, then this changes the language required.

[nicholascar]

Hi Brigette, the Guidelines (now moved to https://github.com/AGLDWG/guidelines) cater for URIs for Datasets and Definitional Resources (vocs & onts).

Indeed the focus for now is on public URIs that resolve to public resources but this need not technically be the case as we could mint URIs that only resolve somewhere for people within some security regime, but what would be the point? I recommend sticking to public resources for now and encourage organisations wishing to perhaps use Linked Data / Semantic Web tech for private data to emulate the methods here but the AGLDWG won't really be able to help them with resources, only concepts.

Having said the above, there is already provision in the workflows for URI allocation where a status of 'reserved' is issued for a pattern (see Fig. 4) which means it's no longer available for reallocation but doesn't itself resolve anywhere. This would be appropriate for private resources that might one day become public and seek an easy transition for when they do so.