Proposal to register CNCF persistent identifier namespace


Noel MacLochlainn
 


On Mon, Jan 17, 2022 at 5:37 PM Chris Aniszczyk <caniszczyk@...> wrote:
The mailing list isn't the best place for this topic, can you open up a github issue here for CNCF staff to investigate:

On Mon, Jan 17, 2022 at 11:34 AM Noel MacLochlainn <noel.mcloughlin@...> wrote:
Hello TOC,

I wish to ask the CNCF Technical Oversight Committee to consider registering CNCF as a persistent identifier namespace on the Web.

Web applications dealing with Linked Data often need URLs that are very stable. Registering CNCF as a persistent identifier namespace allows member projects to leverage the service to register their own sub-namespaces, vocalabaries, and glossaries. For example, CNCF projects publish their vocabulary at: https://w3id.org/cncf/<project>, and potentially in machine readable format in future. The following are examples of persistent identifiers namespaces which could be used today.


The use cases and business value is derived from W3C Linked Data initiatives, and makes CNCF data more accessible on the Semantic Web.

Since I am not TOC member I hope someone on the committee might pick up on this proposal and have it discussed at TOC.

kind regards
Noel Mc Loughling
Open Source Engineer and SRE






--
Cheers,

Chris Aniszczyk
https://aniszczyk.org


Chris Aniszczyk
 

The mailing list isn't the best place for this topic, can you open up a github issue here for CNCF staff to investigate:


On Mon, Jan 17, 2022 at 11:34 AM Noel MacLochlainn <noel.mcloughlin@...> wrote:
Hello TOC,

I wish to ask the CNCF Technical Oversight Committee to consider registering CNCF as a persistent identifier namespace on the Web.

Web applications dealing with Linked Data often need URLs that are very stable. Registering CNCF as a persistent identifier namespace allows member projects to leverage the service to register their own sub-namespaces, vocalabaries, and glossaries. For example, CNCF projects publish their vocabulary at: https://w3id.org/cncf/<project>, and potentially in machine readable format in future. The following are examples of persistent identifiers namespaces which could be used today.


The use cases and business value is derived from W3C Linked Data initiatives, and makes CNCF data more accessible on the Semantic Web.

Since I am not TOC member I hope someone on the committee might pick up on this proposal and have it discussed at TOC.

kind regards
Noel Mc Loughling
Open Source Engineer and SRE






--
Cheers,

Chris Aniszczyk
https://aniszczyk.org


Noel MacLochlainn
 

Hello TOC,

I wish to ask the CNCF Technical Oversight Committee to consider registering CNCF as a persistent identifier namespace on the Web.

Web applications dealing with Linked Data often need URLs that are very stable. Registering CNCF as a persistent identifier namespace allows member projects to leverage the service to register their own sub-namespaces, vocalabaries, and glossaries. For example, CNCF projects publish their vocabulary at: https://w3id.org/cncf/<project>, and potentially in machine readable format in future. The following are examples of persistent identifiers namespaces which could be used today.


The use cases and business value is derived from W3C Linked Data initiatives, and makes CNCF data more accessible on the Semantic Web.

Since I am not TOC member I hope someone on the committee might pick up on this proposal and have it discussed at TOC.

kind regards
Noel Mc Loughling
Open Source Engineer and SRE