Add new top level namespace - ksoc

[mateuszdyminski]

Request namespace for KSOC Inc. ecosystem

Name: ksoc Description: Namespace for use by KSOC Inc. Administered By: KSOC Taxonomy: https://github.com/ksoclabs/kbom/blob/main/docs/taxonomy.md

For now we would like to use ksoc:kbom namespace as this taxonomy is used by kbom tool, but in the future we would like to extend it and use more generic ksoc:

[jkowalleck]

your taxonomy https://github.com/ksoclabs/kbom/blob/main/docs/taxonomy.md (#65) is bringing Kubernetes(k8s) to the table.

The community is currently working on a general k8s related taxonomy. #59 To join efforts, instead of having everybody reinventing the wheel, I would like you to contribute to this, instead of pushing a 14th standard.
Maybe we can make it happen to have only one k8s taxonomy. Lets try :-)

How does this sound to you?

[mateuszdyminski]

your taxonomy https://github.com/ksoclabs/kbom/blob/main/docs/taxonomy.md (#65) is bringing Kubernetes(k8s) to the table.

The community is currently working on a general k8s related taxonomy. #59 To join efforts, instead of having everybody reinventing the wheel, I would like you to contribute to this, instead of pushing a 14th standard. Maybe we can make it happen to have only one k8s taxonomy. Lets try :-)

How does this sound to you?

Of course we would like to contribute to the k8s taxonomy. Our plan was to start from something and then iterate to the place where we can help to build k8s taxonomy. We have following plan:

• Add our own taxonomy prefix ksoc
• Add support for CycloneDX in our KBOM tool - https://github.com/ksoclabs/kbom - based on existing k8s taxonomy
• Extend existing k8s taxonomy with custom fields - https://github.com/ksoclabs/kbom/blob/main/docs/taxonomy.md - still with ksoc:kbom: prefix
• If CycloneDX support in the kbom tool with our custom taxonomy will be warmly welcomed by the community we would like to add it to the https://github.com/CycloneDX/cyclonedx-property-taxonomy/issues/59

So answering your question - we don't want to reinvent the wheel, but rather build something internally, test, get feedback and discuss the standard with you