Semantic Web based Collaborative Knowledge Management LSL, ECS Feng (Barry) Tao A generic SOA for managing semantics driven domain knowledge
Collaborative Knowledge Management Process/Methodologies –Identify conceptualization through ontology KA within the domain Ontological engineering –semantically enrich data using ontology Automatic annotation Manual annotation wizard –manage knowledge through reusing semantically enriched data Query RDF triples for knowledge Inference and Reasoning Architecture –Distributed (over more than one nodes) –Service Oriented –User orientation at different granularities (Web service, Portlet service, portal) –Ontology Driven Technologies –Semantic Web –Web Service –J2EE, JSF and portlets Domains –E-Science (Engineering design of optimization) –Learning (Learning through community knowledge management and sharing)
Ontology Engineering
Semantic web enriched data Ontology –Explicit definitions Concepts Relations –Richer constraints in OWL Cardinality Semantic Annotation –Create instance representing entities in the application data –Fulfill definition/constraints through controlled annotation –Store as RDF triple statements
RDF Triples of the Semantic Annotation Subject predicate object
Technical Architecture Business Logic of the semantic management functions Based on Jena RDF API Tomcat Axis Web service Interface described in WSDL Oriented to service consumers J2EE JSF/Portlet Web service proxy (reusing services) Oriented to customizable GUI designers Delivered as WAR files Portal (reusing portlets) End users oriented 3 rd party applications
Semantic Management Services Tomcat Axis web service Managing ontology Semantically annotating resources Semantic query of the annotated resource
Sequence Diagram of using the semantic management services
Example usages of the SMS // semantic query // query the semantic annotations as triples (subject, predicate, object) SemanticQuery.querySubject(subjectURI, ontologyName) subjectURI = tom ontologyName = photophoto results: <sparql xmlns:rdf=" xmlns:xs=" xmlns=" > <head> <variable name="subjectURI"/> <variable name="predicateURI"/> <variable name="objectURI"/> </head> <results ordered="false" distinct="false"> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> </results> </sparql> table representation: |subjectURI| predicateURI | objectURI | =============================================================================================================================================================== | | < | NS:photo1 | | | < | "Hanks"^^< | | | < | | | | < | NS:barry | | | < | "tom66test"^^< | | | < | "Tom"^^< | | | < | < | <sparql xmlns:rdf=" xmlns:xs=" xmlns=" > <head> <variable name="subjectURI"/> <variable name="predicateURI"/> <variable name="objectURI"/> </head> <results ordered="false" distinct="false"> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <literal datatype=" </binding> </result> <result> <binding name="predicateURI"> <uri> </binding> <binding name="objectURI"> <uri> </binding> </result> </results> </sparql> table representation: |subjectURI| predicateURI | objectURI | =============================================================================================================================================================== | | < | NS:photo1 | | | < | "Hanks"^^< | | | < | | | | < | NS:barry | | | < | "tom66test"^^< | | | < | "Tom"^^< | | | < | < | another example is subjectURI = tom ontologyName = elegiProjectelegiProject result is: table represenation: | subjectURI| predicateURI | objectURI | ==================================================================================================================================================================== | | | NS:WP5 | | | | NS:john | | | | | | NS:UoS | | | | NS:WP7 |
Example usage of the SMS - 2
Portlet development Business Logic of the semantic management functions Based on Jena RDF API Tomcat Axis Web service Interface described in WSDL Oriented to service consumers J2EE JSF/Portlet Web service proxy (reusing services) Oriented to customizable GUI designers Delivered as WAR files Portal (reusing portlets) End users oriented 3 rd party applications
Query result in XML format (direct from the web service call)
Aggregating portlets for customizable Portal Business Logic of the semantic management functions Based on Jena RDF API Tomcat Axis Web service Interface described in WSDL Oriented to service consumers J2EE JSF/Portlet Web service proxy (reusing services) Oriented to customizable GUI designers Delivered as WAR files Portal (reusing portlets) End users oriented 3 rd party applications