Function | invoke the Apache Jena ontology framework |
Distribution | Jena-bin- |
Jar files | JenaModule.jar JenaCommon.jar |
Modules | jena |
Namespace | http://dassault-aviation.com/jena |
Provided services | sendInstance owlRequest http://dassault-aviation.com/jena:owlObjectRequest http://dassault-aviation.com/jena:getProperty http://dassault-aviation.com/jena:getDataProperty http://dassault-aviation.com/jena:getProperties http://dassault-aviation.com/jena:getGeoSPARQLGeometry http://dassault-aviation.com/jena:setGeoSPARQLGeometry http://dassault-aviation.com/jena:applyOperations http://dassault-aviation.com/jena:appliedOperations http://dassault-aviation.com/jena:getGraph http://dassault-aviation.com/jena:getStatistics http://dassault-aviation.com/jena:getObjectStatistics |
Required services | addInstance getInstance addPropertyToInstance getPropertyOfInstance addDataPropertyToInstance updateDataPropertyToInstance addInverseProperty saveSchema |
Mandatory properties | name (per schema)owlData (per schema)prefixNS (per schema)owlNS (per schema) |
Optional properties | owlSchema (per schema)defaultNS (per schema)prefix (per schema)geosparql (per schema)owlTime (per schema)ontologyModel (per schema)imports debug sendRequestInfo yield commit customFunctions |
reqSchema
key in the requestsowlSchema
is not present, it will also contain the associated schema<application name="jena"> <module name="jena"> <moduleArrayGroupProperty key="schemas"> <moduleArrayValue> <moduleProperty key="name" value="sitac"/> <moduleProperty key="owlData" value="19-02-25-SITAC.owl.rdf"/> <moduleProperty key="prefixNS" value="sitac:"/> <moduleProperty key="owlNS" value="http://localhost/SITAC#"/> </moduleArrayValue> </moduleArrayGroupProperty> <moduleProperty key="debug" value="warning"/> <moduleArrayProperty key="imports" /> <value value="dublin_core_elements.rdf"/> </moduleArrayProperty> </module> </application>
<application name="jena"> <module name="jena"> <moduleArrayGroupProperty key="schemas"> <moduleArrayValue> <moduleProperty key="name" value="sitac"/> <moduleProperty key="owlData" value="19-02-25-SITAC.owl.rdf"/> <moduleProperty key="prefixNS" value="sitac:"/> <moduleProperty key="owlNS" value="http://localhost/SITAC#"/> </moduleArrayValue> </moduleArrayGroupProperty> <moduleProperty key="debug" value="warning"/> </module> </application>In this case only warnings are shown.
<application name="jena"> <module name="jena"> <moduleArrayGroupProperty key="schemas"> <moduleArrayValue> <moduleProperty key="name" value="sitac"/> <moduleProperty key="owlData" value="19-02-25-SITAC.owl.rdf"/> <moduleProperty key="prefixNS" value="sitac:"/> <moduleProperty key="ontologyModel" value="OWL_MEM" /> <moduleProperty key="owlNS" value="http://localhost/SITAC#"/> </moduleArrayValue> <moduleArrayValue> <moduleProperty key="name" value="pizza" /> <moduleProperty key="owlData" value="pizza.owl.rdf" /> <moduleProperty key="prefixNS" value="pizza:" /> <moduleProperty key="owlNS" value="http://www.co-ode.org/ontologies/pizza/pizza.owl#" /> </moduleArrayValue> </moduleArrayGroupProperty> <moduleProperty key="yield" value="100"/> </module> </application>
sendInstance
: provides one event Service which returns a list of instances instance when answering to the getInstance
service[2]
getInstance
and sendInstance
services could have been one request-response Service insteadsendInstance
: provides one event Service which returns a list of instances instance when answering to the getInstance
service[3]
getInstance
and sendInstance
services could have been one request-response Service insteadhttp://dassault-aviation.com/jena:applyOperations
: this service allows to chain a list of update or creation operations in the underlying database in only one transaction. See Jena operations for more informationhttp://dassault-aviation.com/jena:appliedOperations
: this service specifies which element have been created by the previous applyOperations
service. See applied operations for more informationhttp://dassault-aviation.com/jena:getGraph
: this service allows to get the graph of the ontology structurehttp://dassault-aviation.com/jena:getStatistics
: this service allows to get statistics about the ontology content (number of definition and individuals objects)http://dassault-aviation.com/jena:getObjectStatistics
: same as the precedent service, but returns an object rather than a structureowlRequest
: this service answers to SPARQL requests to the Jena frameworkhttp://dassault-aviation.com/jena:owlObjectRequest
: this service answers to SPARQL requests to the Jena framework and return the rsults as objectsreqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesinstanceNames
: the array specifying the list of instancesowlRequest
Service is a request-response Service Service which answers to SPARQL requests to the Jena framework. The request returns formatted or XML results.
http://dassault-aviation.com/jena:owlObjectRequest
service is a request-response Service which answers to SPARQL requests to the Jena framework. The request returns the results as a org.da.protoframework.jena.common.QueryResult
object.
http://dassault-aviation.com/jena:requestInfo
service is an event Service which is sent by the Jena module after it has received owlRequest
or http://dassault-aviation.com/jena:owlObjectRequest
service. This service contains several informations about the request and its processing by the module:reqSchema
: The key of the OWL schema used for the requestrequest
: The full SPARQL request string as used by the Jena module, including the prefixrequestStatus
: The return status of the requesterrorMessage
: The error message if the request was not validaddInstance
: add an instance to an OntologyaddPropertyToInstance
: add a property to an instance to an OntologyaddDataPropertyToInstance
: add a Data property to an instance to an OntologyaddInverseProperty
: allows to add an inverse property to an OntologygetInstance
: allows to ask for a list of instances. Upon reception of this service, the Jena module will invoke the sendInstance
service[3]
getInstance
and sendInstance
services could have been one request-response Service insteadsaveSchema
: allows to save the content of the ontology to a fileaddInstance
Service is an event Service Service which allows to add an instance.reqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesinstanceName
: the name of the instance to createparentName
: the name of the parent class of the instanceaddPropertyToInstance
Service is an event Service Service which allows to add a property to an instance.reqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesinstanceSubjectName
: the name of the instance for which to add the propertypropertyName
: the name of the propertypropertyValue
: the value of the propertyaddDataPropertyToInstance
Service is an event Service Service which allows to add a Data property to an instance.reqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesinstanceSubjectName
: the name of the instance for which to add the propertydataPropertyName
: the name of the data propertydataPropertyValue
: the value of the data propertyaddInverseProperty
Service is an event Service Service which allows to add the inverse of a property.reqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesproperty1
: the name of the existing propertyproperty2
: the name of the inverse property to create relative to the existing propertygetInstance
Service allows to ask for a list of instances for a list of classes. Upon reception of this service, the Jena module will invoke the sendInstance Service to send the list of instances.reqSchema
: the key of the OWL schema to use for the request, must correspond to the name
of one of the owlSchema
s in the propertiesinstanceType
: the array specifying the list of classesname
: (mandatory) the key of the Schema, to be used in the requests and responsesowlData
: (mandatory) the files for the RDF dataowlSchema
: (optional) the files for the OWL schema[4]
prefixNS
: (mandatory) the prefixes for the OWL queryowlNS
: (mandatory) the namespaces for the OWL querydefaultNS
: (optional) the default namespaceprefix
: (optional) an additional array of prefix / namespacesowlRequest
service.
owlRequest
service.<module name="userInputs" id="1" > <interfaces> <requestSend service="owlRequest" timeOut="300ms" /> </interfaces> </module>
reqSchema
: The Owl Schema keyquery
: The Owl queryresponseType
: The desired response type, which can be:respSchema
: The Owl Schema key which was used for the requestresponse
: The Owl responserequestStatus
: The Owl response status. The values can be:addInstance
service.<module name="userInputs" id="1" > <interfaces> <eventSend service="addInstance" /> </interfaces> </module>
addPropertyToInstance
service.<module name="userInputs" id="1" > <interfaces> <eventSend service="addPropertyToInstance" /> </interfaces> </module>
getInstance
and sendInstance
services could have been one request-response Service insteadgetInstance
and sendInstance
services could have been one request-response Service insteadCopyright 2017-2020 Dassault Aviation. All Rights Reserved. Documentation and source under the LGPL v3 licence