Decide on namespace for CPLD documents and schemas

[RinkeHoekstra]

Related to #43

[RinkeHoekstra]

What are the requirements:

• The CPLD namespace should redirect to the CPLD schema and JSON-LD context through content negotiation
• The schema location should be owned and managed by NISO
• The schema location should be permanent.

I think that the easiest approach is to create a permanent URL that redirects to a file-based location online.

• We can create a permanent url using https://w3id.org or https://purl.org. The drawback is that this impacts what the namespace looks like, e.g. https://w3id.org/cpld/ or https://purl.org/niso/cpld/.
• Have a NISO-hosted service redirect to the hosting location; this requires effort and maintenance by NISO.

Hosting-wise, there are multiple options too:

• Have a NISO-hosted permanent page for this, as is e.g. done for the CrediT taxonomy https://credit.niso.org. The drawback is that this requires effort to maintain by NISO (e.g. the CrediT taxonomy is Wordpress-backed... this is costly to maintain).
• Use GitHub-pages off-of the current repository. We can automate some of the documentation-generation using e.g. Jekyll and link directly to the standard.

@mark-donoghue , @dtkaczyk , @dscheftner ... thoughts?

[mark-donoghue]

I would go with the purl.org solution at this stage. The management overhead is lower and purls have been around for a long time.

[RinkeHoekstra]

I think we decided on w3id.org as it was understood that purl.org is only in maintenance mode.