Making SOAP web services semantically understandable Luis Bermudez - PowerPoint PPT Presentation

1 / 26
About This Presentation
Title:

Making SOAP web services semantically understandable Luis Bermudez

Description:

WFS : requests for geo-features based on XML-based GML (is a REST type) UDDI WSDL and SOAP ... strings that contain RDF/XML Dublin Core Metadata. MMI Extension ... – PowerPoint PPT presentation

Number of Views:53
Avg rating:3.0/5.0
Slides: 27
Provided by: LUISBE8
Category:

less

Transcript and Presenter's Notes

Title: Making SOAP web services semantically understandable Luis Bermudez


1
Making SOAP web services semantically
understandableLuis Bermudez
ltMMI /gt
  • OOSTech Baltimore Oct, 25 2005

2
http//marinemetadata.org
3
Ingests from instruments
Data Source
processes formats/archives
sends
gets
Community
gets
Guides Tools
sends
Technology
processes formats/archives
processes uses/analyzes
gets
publishes
Data User
Data Provider
4
MMI Demo Tethys
5
Web service
  • W3C A software system designed to support
    interoperable machine-to-machine interaction
    over a network.
  • Types
  • SOAP-WSDL follow special standard schemas
    http//schemas.xmlsoap.org/wsdl/
  • REST anything accessible through an HTTP GET
    request.
  • WFS requests for geo-features based on
    XML-based GML (is a REST type)

6
UDDI WSDL and SOAP
TOOLS APACHE TOMCAT AXIS
7
MMI Tethys
8
2
1
9
?
AXIS invocation of a web service method
10
MMI Tethys
11
(No Transcript)
12
Call returns strings that contain RDF/XML Dublin
Core Metadata
13
?
?
MMI Extension to DCMI
14
Tools Helper class to read write RDF/XML
Dublin Core Metadata
15
getASCII method
We get the id of the dataset (parameter and
source) with getMetadata call.
Similar to the getMetadata method why? Uses
stateless Protocol - The system doesnt know
anything about the previous call.
16
ASCII example
?
Simplifications only one parameter per call,
same order of columns, format of time ISO 8601
etc
17
Solving semantic issues
18
Harmonization
HTML
Comma Separated Values
DTD
Tab Separated Values
XML/XSD
OWL
Relational Database
RDF
19
VOC2OWL
20
VINE (Vocabulary Integration Environment tool)
21
Ontology web services
  • http//marinemetadata.org9600/mmiws/servlet/AxisS
    ervlet
  • http//marinemetadata.org9600/mmiws/jsp/

22
Tying it all together
23
Conclusion - possible path
  • Implement two methods and make them available
    using SOAP web services.
  • Convert the parameters, sources, and units used
    in their system to an ontology.
  • (tool VOC2OWL ascii to OWL)
  • Map the terms used in the system to the MMI
    preferred ontology Standard vocabulary for
    discovery (GCMD) and for usage (CF).
  • http//marinemetadata.org/tethys

24
Credits
  • National Science Foundation1
  • SURA, the Southeastern Universities Research
    Association (http//www.sura.org),
  • NOAA (including the Coastal Services Center),
  • ONR, the Office of Naval Research
    (http//www.onr.navy.mil),
  • OceanUS and regional IOOS systems.
  • 1 NSF Grant ATM-0447031

25
Steering Committee Members
  • John Graybeal, MBARI. PI. (ExecComm) graybeal_at_mbar
    i.org
  • Stephanie Watson, CeNCOOS. (ExecComm) swatson_at_mbar
    i.org
  • Philip Bogden, SURA/SCOOP. (ExecComm) bogden_at_gomoo
    s.org
  • Stephen Miller, Scripps. (ExecComm) spmiller_at_ucsd.
    edu
  • Robert Arko, LDEO
  • Julie Bosch, NOAA
  • Francisco Chavez, MBARI
  • Ben Domenico, Unidata
  • Karen Stocks, SDSC
  • Steve Hankin, NOAA - Ocean.US/DMAC
  • Roy Lowry, BODC
  • Mark Musen, Stanford Univ
  • Michael Parke, Univ of Hawaii
  • Lola Olsen, NASA Goddard
  • Dawn Wright, Oregon State Univ
  • Bob Weller, WHOI

26
Thank you !bermudez_at_mbari.org
Write a Comment
User Comments (0)
About PowerShow.com