data-model-spec
data-model-spec copied to clipboard
rdfjs
RDF/JS: Data model specification – A specification of a low level interface definition representing RDF data independent of a serialized format in a JavaScript environment.
It should be allowed to pass a `Term` to `Quad#equals` given our recent RDF* changes. Right now, only `Quad` is allowed to be passed.
It came to my attention in #124 that we don't really have a way of talking about triples without implying that they're part of a graph. Since #124 is about...
We may/should add some explanation for RDF* to the spec. Also, a link should be added. Should we add the [blog post](https://blog.liu.se/olafhartig/2019/01/10/position-statement-rdf-star-and-sparql-star/) or the [paper](https://arxiv.org/abs/1406.3399) as a link? When will...
As proposed in #136 new features should get it's own spec. Maybe it would be good if we define a standard way for feature detection in this spec, as it...
Would it be possible for us to add Semantic Versioning to the spec? (It would help when looking at various `rdf-ext` etc libraries, to know which version of the spec...
Variable support is optional. Can we just say variables are not supported if the constructor is undefined?
Following https://lists.w3.org/Archives/Public/public-rdfjs/2017Sep/0003.html, I suggest we make the language more strict and only allow those 5 values.
During a discussion about cloning terms with new values came up that it should be more clear that the factory is the only entry point to creates new objects. Maybe...
Are objects created by the `DataFactory` immutable? How should we write that in the spec? I think we said we don't define the properties read-only to avoid forcing the usage...
A test suite should be implemented to test code for compliance. Examples of test suites: [rdf-test-graph](https://github.com/rdf-ext/rdf-test-graph) or [Promises/A+ Compliance Test Suite](https://github.com/promises-aplus/promises-tests)