chore(migrate repository): migrate repository from ng to tractus-x

[stephanbcbauer]

Description

This PR add content from a repostory product-ontology which was managed in a different organisation, catenax-ng including the history

Since we need this content in tractus-x and the catenax-ng will be deleted soon, we want to migrate the content to tractus-x.

Therefore, this initial PR was created.

It contains all the content and history of the repository.

A review Eclipse IP Ticket was already approved with the current content, but it didn't include new legal docs, header a.s.o.

So in this case we will create a new review request, after we are finished with our work, before the PR is merged

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[stephanbcbauer]

Converted to DRAFT … after the Header, and legal docs are updated … @jSchuetz88 and I will change the status again.

[AngelikaWittek]

@stephanbcbauer
Also do the changes from: https://github.com/eclipse-tractusx/sldt-ontology-model

• NOTICE file is the wrong template
• CONTRIBUTING file -> update header, references to Catena-X, use new template
• CODE of Conduct -> Use new template

[stephanbcbauer]

@stephanbcbauer Also do the changes from: https://github.com/eclipse-tractusx/sldt-ontology-model

• NOTICE file is the wrong template
• CONTRIBUTING file -> update header, references to Catena-X, use new template
• CODE of Conduct -> Use new template

Thanks @AngelikaWittek , @jSchuetz88 will update the repository/pr as soon as possible.

[arnoweiss]

Can you briefly state the reasoning for transfering governance of this repository (and thus implicitly the https://w3id.org/catenax namespace) to Eclipse Tractus-X? I've always thought of this as very common to the policy constrains - all of which are managed in the catenax-ev organization.

cc @obalandi

[stephanbcbauer]

Can you briefly state the reasoning for transfering governance of this repository (and thus implicitly the https://w3id.org/catenax namespace) to Eclipse Tractus-X? I've always thought of this as very common to the policy constrains - all of which are managed in the catenax-ev organization.

cc @obalandi

@jSchuetz88

[stephanbcbauer]

@obalandi @jSchuetz88 dont want to stress anybody, but i think we should finalize this PR?

What's missing?

• Answering the last questions @obalandi
• review by committees
• create new IP Ticket @stephanbcbauer

After these steps, i think we are good to merge the big PR and we are able to delete the fork.

THX

[obalandi]

@stephanbcbauer, we (@jSchuetz88 and @obalandi) discussed this with @arnoweiss. And the decision is that all vocabularies in the taxonomy that are used in an application configuration will have a special attribute so that they are protected and will not be changed in a normal modelling session. How this works will be defined in the modelling guidelines in TC4M.

[stephanbcbauer]

@stephanbcbauer, we (@jSchuetz88 and @obalandi) discussed this with @arnoweiss. And the decision is that all vocabularies in the taxonomy that are used in an application configuration will have a special attribute so that they are protected and will not be changed in a normal modelling session. How this works will be defined in the modelling guidelines in TC4M.

OK, thank you very much. So in this case, we are ready for review by committers, correct? Meanwhile, I will create the Eclipse IP Ticket, cause of the big number of changes.

[stephanbcbauer]

@stephanbcbauer, we (@jSchuetz88 and @obalandi) discussed this with @arnoweiss. And the decision is that all vocabularies in the taxonomy that are used in an application configuration will have a special attribute so that they are protected and will not be changed in a normal modelling session. How this works will be defined in the modelling guidelines in TC4M.

OK, thank you very much. So in this case, we are ready for review by committers, correct? Meanwhile, I will create the Eclipse IP Ticket, cause of the big number of changes.

@obalandi @jSchuetz88 ip ticket was approved.