GitHub user afs added a comment to the discussion: StreamRDF RIOT and
generalized RDF
> * Should there be a way for `StreamRDF` producers to inform the consumers
> that there may/may not be generalized RDF in the stream?
`StreamRDF` is a general low level plumbing, to plug RDF processing together,
focused on parser output. It separates producer and consumer implementation
choices. It is not arbitrary plug-and-play though. For example, e.g. in many
cases, there is no quad support.
To provide context/options, I would suggest a layer on top of StreamRDF that
focuses on being a processing framework.
> * Should RIOT implementations expose an API telling whether they support
> generalized RDF or not?
Jena is not offering a generalized RDF processing platform. The assumptions of
proper RDF runs deep.
("generalized" is particularly hard because the predicate position is general -
e.g. triple terms).
> * Should the N-Triples RIOT support only writing of generalized RDF (like
> right now), reading and writing, or neither?
The parsers are RDF, not generalized RDF. Uses expect errors on "bad RDF".
There is no reason why new languages can't be added but redefining standard
languages would be bad.
GitHub link:
https://github.com/apache/jena/discussions/3079#discussioncomment-12978672
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
