We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There seems to be a few things that deviate from the spec:
In the "Data Interfaces" section of the spec (https://rdf.js.org/data-model-spec/#data-interfaces) Quad is does not extend term, however, in the typings it does: https://github.com/rdfjs/types/blob/master/data-model.d.ts#L13
Quad
In the "Quad Interface" section of the spec (https://rdf.js.org/data-model-spec/#quad-interface) a Quad is the parameter for equals, but in the typings, Term is the parameter (https://github.com/rdfjs/types/blob/master/data-model.d.ts#L13)
The text was updated successfully, but these errors were encountered:
All of this is actually intentional, see rdfjs/data-model-spec#165
Sorry, something went wrong.
Okay then, I guess this is more about inconsistencies in the spec then. Is there a reason the places I linked say Quad rather than Term?
Is there a reason the places I linked say Quad rather than Term?
Not really, just needs an update I guess. Feel free to submit a PR! :-)
No branches or pull requests
There seems to be a few things that deviate from the spec:
1. BaseQuad is not a Term
In the "Data Interfaces" section of the spec (https://rdf.js.org/data-model-spec/#data-interfaces)
Quad
is does not extend term, however, in the typings it does: https://github.com/rdfjs/types/blob/master/data-model.d.ts#L132. Quad equals accepts Term instead of Quad
In the "Quad Interface" section of the spec (https://rdf.js.org/data-model-spec/#quad-interface) a
Quad
is the parameter for equals, but in the typings, Term is the parameter (https://github.com/rdfjs/types/blob/master/data-model.d.ts#L13)The text was updated successfully, but these errors were encountered: