1 / 16

AHDIT: Ad Hoc Data Interoperability Tool

AHDIT: Ad Hoc Data Interoperability Tool. Dr. Bruce A. Scharlau Dept. of Computing Science University of Aberdeen scharlau@csd.abdn.ac.uk. Outline. The Problem Potential Solution XML, XML Schema & RDF AHDIT Development Future Development Conclusion. The Problem. Sept 11 2001

eara
Télécharger la présentation

AHDIT: Ad Hoc Data Interoperability Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AHDIT: Ad Hoc Data Interoperability Tool Dr. Bruce A. Scharlau Dept. of Computing Science University of Aberdeen scharlau@csd.abdn.ac.uk Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  2. Outline • The Problem • Potential Solution • XML, XML Schema & RDF • AHDIT Development • Future Development • Conclusion Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  3. The Problem Sept 11 2001 Exchange data on: Suspects Victims Potential Victims Philippines France NYPD Washington DC UK 50 Other States How can so many different organisations exchange information? Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  4. Current Practice Word Doc Word Doc • Exchange MS Word documents: • 1. Enter data into own system • 2. Export report to other party • 3. Recipient then enters data into own system • Potential for error as data re-entered • Requires more clerical staff • Creates a bottleneck at the start of investigations. • The problem occurs when common data procedures and agreements are not already present between the parties involved. Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  5. Current State of Affairs • Organisations have problems communicating internally as evidenced by knowledge management applications • problems finding experts in organisations • problems sharing information in organisations • Organisations communicate externally even less well • Governments implementing interoperability progammes • Some governments setting standards for XML use with XML Schema. • UK & US working towards standard XML policies Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  6. Potential Solution • Semantic Web offers solution • Give meaning to and extending the WWW • Machine processable, not human readable • Built upon structured collections of data and inference rules • Use of XML and related languages • AHDIT builds upon the Semantic Web: • use structured data of the XML and XML Schema to create RDF models that can be compared • work with standard practices of organisations Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  7. Semantic Web Layers • AHDIT works with XML, XML Schema and RDF, RDF Schema layers • XML & XMLS are being deployed by governments today • AHDIT lifts this to next level of RDF & RDFS Source: Tim Berners Lee http://www.w3.org/2000/Talks/1206-xml2k-tbl/slide10-0.html Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  8. XML- Extensible Markup Language • W3C Standard of human readable text • Provides structured content - still need to know what citizen means <egif:CitizenNameStructure> <egif:CitizenNameTitle>Mr</egif:CitizenNameTitle> <egif:CitizenNameForename>Jonathan </egif:CitizenNameForename> <egif:CitizenNameSurname>Doe </egif:CitizenNameSurname> <egif:CitizenNameRequestedName>Jon </egif:CitizenNameRequestedName> </egif:CitizenNameStructure> Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  9. XML Schema • The XML Schema file (xsd) defines whether an XML document is valid or not. • The XML file could also be labelled as an instance of an XSD file. <xsd:complexType name="CitizenNameStructure"> <xsd:sequence> <xsd:element name="CitizenNameTitle" type="egif:CitizenNameTitleType" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="CitizenNameForename" type="egif:CitizenNameForenameType" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="CitizenNameSurname" type="egif:CitizenNameSurnameType"/> ... </xsd:sequence></xsd:complexType> Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  10. RDF- Resource Definition Framework • Aimed at providing information about meta-data for WWW resources. • AHDIT builds this up from the XML Schema using Jena … <rdf:Description rdf:about='citizen'> <NS0:CitizenNameSurname rdf:resource='#CitizenNameSurname'/> …<NS0:CitizenName rdf:resource='#CitizenName'/> </rdf:Description> </rdf:Description> <rdf:Description rdf:about='http://www.w3.org/2000/01/rdf-schema#Class'> <NS0:CitizenNameSurname>:CitizenNameSurnameType </NS0:CitizenNameSurname> …</rdf:Description> …<rdf:Description rdf:about='#CitizenNameSurname'> <rdfs:label>CitizenNameSurname</rdfs:label> … </rdf:Description> … Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  11. AHDIT Development The Goal: Direct application to application communication State A State B Application Application Export report Import or type report Email or post report We want to move from the email route to the direct route Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  12. Phase 1 Solution • Mixed Method : • export report • send to second party • convert to XML • run through AHDIT • import modified report DB 1 App 1 App 2 DB 2 Export report Import report State A State B Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  13. AHDIT Phase 1 Solution • Application takes in two XSD files, and the new XML file to be integrated • User determines what is changed in ‘RDF not B’ to create ‘Modified State A XML’ file. State B RDF State B XSD AHDIT Modified State A XML State A XSD RDF not B State A XML State A data ready For import into State B data State A RDF Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  14. Future Development • Phase 1 - parse and compare the documents • Phase 2 - establish community methods • local server with knowledge of partner organisations • maps to convert to their data structures stored • Phase 3 - develop agent facilities to automate methods • Aim towards less human intervention • Security needs to be incorporated • Ontology tools to manage knowledge and the data • Language tools to manage diverse users and contente • German vs, French, vs English issues, etc • Communication method between parties • Possibly RPC or SOAP for the first two phases • Probably need agent communication languages for phase 3 Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  15. Possible Phase 3 Solution App 3 AHDIT AHDIT DB 3 XML XML A 2 DB 1 App 1 App 2 DB 2 Negotiate A 1 AHDIT - create app to integrate data into current systems - would need search, find and bind procedures State A State B Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

  16. Summary • Organisations need to exchange information • Current methods are laborious, repetitious, and error prone • Movement towards XML & XML Schema • Today methods and concepts are available to allow for ad hoc interoperability between applications and organisations Dr. Bruce A. Scharlau, AHDIT, ES2002 E-Business Workshop

More Related