[ 
https://issues.apache.org/jira/browse/STANBOL-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169739#comment-13169739
 ] 

Alessandro Adamou commented on STANBOL-422:
-------------------------------------------

As of rev. #121434 there are two such OntologyInputSource classes. 

Note that now the interface uses generics: OntologyInputSource<O> where O is 
the managed ontology:

- OntologyContentInputSource parses an OWLOntology from an InputStream. 
Optionally, you can provide your own OWLOntologyManager to use for the process, 
otherwise it creates its own. This implementation is less efficient 
storage-wise due to the Clerezza <--> OWL API bridging, but it does not require 
any conversion if you need to manage it axiom-wise.

- GraphContentInputSource parses a Clerezza Graph from an InputStream. Note 
that it is a SimpleGraph created in-memory: to store it, you must copy its 
triples to a MGraph managed by the TcManager. If you would like an alternative 
constructor where you can provide a custom TcProvider (including the TcManager 
itself) to avoid copying it over, just ask.


                
> Create an OntologyInputSource based on an InputStream
> -----------------------------------------------------
>
>                 Key: STANBOL-422
>                 URL: https://issues.apache.org/jira/browse/STANBOL-422
>             Project: Stanbol
>          Issue Type: New Feature
>          Components: Ontology Manager
>            Reporter: Stephen Bayliss
>            Priority: Minor
>
> It would be useful to have an OntologyInputSource that takes an InputStream 
> in its constructor.
> One use-case is HTTP-accessible content that requires authentication - an 
> HTTP client can then be used to generate an InputStream, with the HTTP client 
> handling the authentication.  The InputStream could then be wrapped in an 
> OntologyInputSource and then be added to an OntoNet custom space.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to