Decouple semantics from data model

[dbooth-boston]

"allow different profiles that plug in different semantics.
Open world assumption doesn't fit your use case? Use a profile that has
NAF or WFS, or answer-sets, or production rules, or probabilistic, or
some kind of procedural hybrid. Or just ignore this part as I guess the
vast majority of triplestores currently do."
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0045.html

"practices like closing the world to validate anything you let in/out of your system is a perfectly fine thing and to me at least a total no-brainer. Such practices should be supported more fluidly through e.g. a more powerful graph naming mechanism (and better meta modeling facilities in general)"
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0276.html
"[Semantic should] be decoupled in a future version. Those who find
these semantics useful should continue to use them, but there are plenty
of use cases where the given semantics are not just unnecessary but also
an obstacle (performance of inferencing, merging of blank nodes etc). . . .
IMHO a better stacking of RDF would have a simplified RDF (maybe called
Graph Data Framework) at its very bottom, i.e. a definition of graphs
that consist of triples that consist of subject, predicate and object,
and (hopefully) better support for reified statements, named graphs and
lists. These can be formalized entirely as a data structure/API".
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0215.html

"I think the most reasonable evolution is to restructure the layers
so that RDFS/OWL can continue to work as now, while providing a standard
foundation for those who prefer closed world semantics etc. One way to
approach this would be to have a core model that just describes the
syntax of graphs but very little semantics. The JavaScript API comes pretty close to how such a core specification could look like (including the treatment of bnodes): https://rdf.js.org/
https://lists.w3.org/Archives/Public/semantic-web/2018Nov/0268.html