Closed sebbader closed 2 years ago
Furthermore, the new MediaTypes and IANAMediaTypes as "Enums" kills the currently running applications as well. We need to step back here, too.
Hi @JohannesLipp,
Your changes introduce a lot of commented-out code, which is bad practice. Better remove it instead?
While this is in principle right, we do actually need the commented lines soon. Just not this week, because the tooling is not yet ready. Next week that will - hopefully - happen, then we will create a new PR with the "proper" statements. For now however the current state of master
means all projects using the IAIS libs are breaking, which we must solve.
I know: Tooling after specification, and not the other way around. But here broken tooling actually means "no one can use it anymore", which is even worse.
So, I am asking here for an exception, regarding that this is only for a few days.
… both URI or RDF Entity.
We have just discovered that this switch is completely breaking in the tools (not in the plain ontology though). Nevertheless, many project partners asked us to revert this update, so here we are.
Major problem: IDS entities (let's call them E_0) have been loaded to a triplestore before, now the new Information Model with this features are added, and as a result the E_0 triples are lacking rdf:type triples for Participants. Participants are now not URIs anymore --> The Applications do not know whether an old instance (inserted as a anyURI) is now of which class (rdf:type triple was never added).