afs commented on pull request #759: URL: https://github.com/apache/jena/pull/759#issuecomment-651154292
> am I missing something? `RDFParser` is not limited to HTTP. RDF parsing is a process of fetching syntax bytes and converting to RDF. There are several steps in doing that. The user/application task should be simple and natural. `RDFDataMgr` provides single function calls for the majority of use cases and provides convenience. The main set of functions are around "Get RDF from URI" - for files and HTTP. It calls `RDFParser`, hiding the details. If the application wants control it can: * Use `RDFParser` directly - the builder pattern makes setting the many aspects of a request much easier that APIs for every variation. * Provide some steps itself, for example, get the InputStream and determine the syntax then pass to a parser (bytes to triples) * Do something else. > we want to use our own HTTP API across the board, including `OntDocumentManager` If you mean JAX-RS, it is a whole application approach and runtime. It is remote only. Not everyone will want to their applications done that way. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: pr-unsubscr...@jena.apache.org For additional commands, e-mail: pr-h...@jena.apache.org
