SQL HQL: Because SQL Was Already Taken - PowerPoint PPT Presentation

1 / 20
About This Presentation
Title:

SQL HQL: Because SQL Was Already Taken

Description:

Leave VxO Interfaces Intact - Translate between Query Language and VxO interface ... If not - Qterm is flagged in response message. Current Status ... – PowerPoint PPT presentation

Number of Views:122
Avg rating:3.0/5.0
Slides: 21
Provided by: haoU
Category:
Tags: hql | sql | already | flagged | taken

less

Transcript and Presenter's Notes

Title: SQL HQL: Because SQL Was Already Taken


1
SQL HQLBecause SQL Was Already Taken
  • Tom Narock
  • Todd King
  • Jan Merka

2
NASA VxO Data Environment
  • Astronomical Community Forms VO

3
NASA VxO Data Environment
  • Astronomical Community Forms VO
  • Solar Community Forms VSO

4
NASA VxO Data Environment
  • Astronomical Community Forms VO
  • Solar Community Forms VSO
  • Beginnings of a VHO effort

5
NASA VxO Data Environment
VSO
VITMO
VHO
ViRBO
VMO/G VMO/U
6
NASA VxO Data Environment
VSO
VITMO
VHO
ViRBO
VMO/G VMO/U
7
NASA VxO Data Environment
VSO
VITMO
VHO
ViRBO
VMO/G VMO/U
8
Query Language Solution
  • Heliophysics Query Language - HQL
  • Standardize How to ask Questions
  • Develop Software to Implement Query Language
  • Leave VxO Interfaces Intact - Translate between
    Query Language and VxO interface

9
Query Language Solution
  • Leave VxO Interfaces Intact - Translate between
    Query Language and VxO interface

Query Language Interface
Conversion to VxO query mechanism
Query Language Interface
Conversion to VxO query mechanism
VxO 1
VxO 2
10
  • International Collaboration to Develop Space
    Physics data model
  • Can Serve as Standard for how to ask questions
  • Converted to OWL-DL ontology for query language

11
Approach
  • Formalize an XML Schema using SPASE
  • Transport using SOAP or REST
  • Compare query with VxO to see if it can be
    answered
  • Return standardized response

12
Query Message
  • ltHQLgt
  • ltResourceType
  • xsitype"xsdstring"gtNumericalData
    lt/ResourceTypegt
  • ltQterm ID0gt
  • ltSPASE
  • xsitype"xsdstring"gtHeliosp
    here.NearEarthlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtMagneticF
    ieldlt/SPASEgt
  • lt/Qtermgt
  • ltQterm ID1gt
  • ltSPASE xsitype"xsdstring"gtComponent
    .Zlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtGSElt/SPAS
    Egt
  • ltQueryUnits xsitype"xsdstring"gtnTlt/
    QueryUnitsgt
  • ltLT xsitype"xsdint"gt0lt/LTgt
  • lt/Qtermgt
  • lt/HQLgt

13
Query Message
  • ltHQLgt
  • ltResourceType
  • xsitype"xsdstring"gtNumericalData
    lt/ResourceTypegt
  • ltQterm ID0gt
  • ltSPASE
  • xsitype"xsdstring"gtHeliosp
    here.NearEarthlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtMagneticF
    ieldlt/SPASEgt
  • lt/Qtermgt
  • ltQtermgt
  • ltID xsitype"xsdint"gt1lt/IDgt
  • ltSPASE xsitype"xsdstring"gtComponent
    .Zlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtGSElt/SPAS
    Egt
  • ltQueryUnits xsitype"xsdstring"gtnTlt/
    QueryUnitsgt
  • ltLT xsitype"xsdint"gt0lt/LTgt
  • lt/Qtermgt
  • lt/HQLgt

Divide query into components and are able to
distinguish which parts we can and can not answer
14
Query Message
  • ltHQLgt
  • ltResourceType
  • xsitype"xsdstring"gtNumericalData
    lt/ResourceTypegt
  • ltQterm ID0gt
  • ltSPASE
  • xsitype"xsdstring"gtHeliosp
    here.NearEarthlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtMagneticF
    ieldlt/SPASEgt
  • lt/Qtermgt
  • ltQtermgt
  • ltID xsitype"xsdint"gt1lt/IDgt
  • ltSPASE xsitype"xsdstring"gtComponent
    .Zlt/SPASEgt
  • ltSPASE xsitype"xsdstring"gtGSElt/SPAS
    Egt
  • ltQueryUnits xsitype"xsdstring"gtnTlt/
    QueryUnitsgt
  • ltLT xsitype"xsdint"gt0lt/LTgt
  • lt/Qtermgt
  • lt/HQLgt

Ask for data using standardized terms
15
Processing Query
Provides Description of VxO capabilities in SPASE
terms
OWL-S
VxO
Software Library uses ontology to compare query
with VxO OWL-S file(s)
OWLS-MX
SPASE ontology
Klusch, M. et. al. 2006.
16
Implementing Query
  • If OWLS-MX finds match we pass information to be
    translated and executed
  • If not - Qterm is flagged in response message

17
Current Status
  • Nearly Complete Prototype Implementation
  • Will be validating using VHO and VMO
  • Will collaborate with other VxOs

18
Current Status
  • Nearly Complete Prototype Implementation
  • Will be validating using VHO and VMO
  • Will collaborate with other VxOs

The least flexible component of any system is the
user. -Lowell Jay Arthur
19
Future Directions
  • OWLS-MX capable of working with more than one
    ontology simultaneously
  • Allows for use of additional data models in
    addition to SPASE
  • This can allow for query language to be used by
    non-SPASE speaking VxOs

20
Take Home Message
  • This is not a final solution
  • Start a dialogue within our community and explore
    what other groups are doing
Write a Comment
User Comments (0)
About PowerShow.com