1 / 14

A Query Language for WSML-Flight

A Query Language for WSML-Flight. Sti jn Heymans, Cristina Feier, Jos de Bruijn, Stephan Zöller (IBIS), Emilia Cimpian. Formal Languages Component. Lead: Stijn Heymans Active Members: Stijn Heymans, Cristina Feier, Jos de Bruijn

ilario
Download Presentation

A Query Language for WSML-Flight

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. A Query Language for WSML-Flight Stijn Heymans, Cristina Feier, Jos de Bruijn, Stephan Zöller (IBIS), Emilia Cimpian

  2. Formal Languages Component • Lead: Stijn Heymans • Active Members: Stijn Heymans, Cristina Feier, Jos de Bruijn • Meetings take place ad hoc, driven by project requirements (e.g., SUPER) as well as requirements from other components (Reasoning).

  3. Motivation for a Query Language

  4. Motivation for a Query Language SUPER

  5. What is a Query Language? • In general: A query language is used to make queries to a certain knowledge base. • In SUPER: e.g., process mining („what business processes allow me to travel to Antwerp?“) • Criteria: • Compatible with the used knowledge base language („ontology language“) • Efficient querying processing possible, • Conformant to the use case requirements

  6. One step closer to a query language... • SUPER ontology language: WSML-Flight • Efficient reasoning possible • Expressive enough • Consequently, SUPER query language needs to be compatible with WSML-Flight

  7. Query Language coming up... • Use case requirement: Aggregates • Counting the number of processes that started • Listing only the first 10 processes that match a condition

  8. Even closer to a query language... • SQL is nice

  9. Even closer to a query language... • SQL is nice, • And people are used to write SQL queries,

  10. Even closer to a query language... • SQL is nice, • And people are used to write SQL queries, • And it has aggregates.

  11. Here we go: Simple queries SELECT ?pe FROM _"http://www.somewhere.org/somedomain\#someBusinessProcess" WHERE ?pe[generatedBy hasValue ?actor] memberOf evo#successfulExecutionEvent

  12. Ordering, Limiting, Offset, Pattern Matching SELECT ?pe, ?actor FROM _"http://www.somewhere.org/somedomain\#someBusinessProcess" WHERE ?pe[generatedBy hasValue ?actor] memberOf evo#successfulExecutionEvent ORDER BY ?actor LIMIT 2 OFFSET 2 SELECT ?pe, ?actor LIKE A% FROM _"http://www.somewhere.org/somedomain\#someBusinessProcess" WHERE ?pe[generatedBy hasValue ?actor] memberOf evo#successfulExecutionEvent ORDER BY ?actor

  13. Operators: Count, Sum, Max, Min, Avg SELECTCOUNT(?pe), ?actor FROM _"http://www.somewhere.org/somedomain\#someBusinessProcess" WHERE ?pe[generatedBy hasValue ?actor] memberOf evo#successfulExecutionEvent GROUP BY ?actor SELECT ?department, SUM(?sales) FROM o WHERE Q GROUP BY ?department HAVING SUM(?sales) wsml#LessThan 1000;

  14. A Final Word • Development of an easy to use query language • Example of how „Formal Languages“ interacts with „Reasoning“: Prototype implementation ready.

More Related