URI Requirements

[nicholascar]

This issue was created in the Profile Guidance document and is listed in it. Once consensus on addressing it is reached here in comments below, the results will be added to the document and the issue closed.

(Antoine:) I think the URI requirements fits here. In fact I think this section should be the one that acts as a 'cover/teaser' for our conneg doc. I.e. it gives a brief motivation for it, tries to fit it in our general picture/model and point to it as our recommendation.

[kcoyle]

Antoine's comment is in section 3 ". Profile publication (normative)"

[kcoyle]

(some possible text for section 3)

To support the functions of documentation of metadata practice and promotion of interoperability, profiles MUST be made available through publication. Publication on the web requires the use of an IRI as identification and location of the profile.

Publication of profiles can take many different forms from human-readable documents, such as a PDF, to implementable code, such as a SHACL or ShEx file. A single profile may consist of more than one file, for example there may be a documentation file in PDF and one or more implementation files that can be used to define the vocabulary and/or validate instance data that is based on the profile.

[aisaac]

Thanks @kcoyle. I think this message is good. I would wait a bit before including it though, as I'd like to see the Conneg document itself ready before we write a cover for it. There may be some wording like 'profile may consist of more than one file' which we may want to adapt to decisions on the abstract model for profiles. I mean, I agree with the situation described but we may want to use a word different from 'consist' if the model uses another word.

But if you think it's better to include the text, solve the issue and homogenize the text only later, I guess I can live with it :-)

[kcoyle]

No problem with waiting.