I40KG
I40KG copied to clipboard
i40-Tools
Contains the development for the Industry 4.0 standards knowledge graph (I40KG). Its current collaborative development is driven by VoCol - http://vocol.iais.fraunhofer.de/sto/
Can I use this library in protege? if not, in which software can I use this? Could you please elaborate?
Please verify the updates to the w3id configuration: https://github.com/sebbader/w3id.org/commit/a4994cec4e8be107ba1f1b2e4cb64288cd2001cc
The standard described [here](https://github.com/i40-Tools/StandardOntology/blob/96401ec2ee7f93e671edc9bbc8a5139a0a2ade2b/sto.ttl#L5243) has a serious issue. It is basically the same than [here](https://github.com/i40-Tools/StandardOntology/blob/96401ec2ee7f93e671edc9bbc8a5139a0a2ade2b/sto.ttl#L5217) and both are pointing to the same dbpedia resource. In addition, they don't have relation...
The URL http://voag.linkedmodel.org/schema/voag# and http://voag.linkedmodel.org/owl/schema/voag# do not exist
[Here](https://github.com/i40-Tools/StandardOntology/blob/96401ec2ee7f93e671edc9bbc8a5139a0a2ade2b/sto.ttl#L6098) the standard contains, quite clear in the description that it is mapped to other standards but no relation is encoded.
Just by realizing a simple check with [OPPS](http://oops.linkeddata.es/response.jsp) you can see how many errors we have. This graph just can't simply continue growing with such errors. Please @sebbader and @PriyankaNanjappa...
ISO 14040:2006 Environmental management -- Life cycle assessment -- Principles and framework
The recent updates on frameworks and concerns are not reflected by the current state of the website at http://i40.semantic-interoperability.org/. Either a new page (Github page?) or an update at semantic-interoperability.org...
One of the main objectives of this work is to connect this knowledge graph with existing ones. Thus, in every case that links to wikipedia exist, there will be a...
The range of `dcterms:license` is the class `dcterms:LicenseDocument`. Values used with this property have to be instances of the class `LicenseDocument` and therefore non-literal values as in the following example....