Semantic query: Difference between revisions
Triadic2000 (talk | contribs) New Article - Upcoming Important Topic in Computer Science and Software Engineering |
Triadic2000 (talk | contribs) Correction of the wiki-link Triplestore |
||
| Line 3: | Line 3: | ||
Semantic queries work on [[Named_graphs|named graphs]] or [[Linked_Data|linked-data]]. This enables the query to process the actual relationships between information and ''infer'' the answers from the ''network of data''. This is in contrast to [[semantic search]], which uses [[semantics]] (the science of meaning) in language to produce a better search result (see [[Natural language processing|Natural language processing]]). |
Semantic queries work on [[Named_graphs|named graphs]] or [[Linked_Data|linked-data]]. This enables the query to process the actual relationships between information and ''infer'' the answers from the ''network of data''. This is in contrast to [[semantic search]], which uses [[semantics]] (the science of meaning) in language to produce a better search result (see [[Natural language processing|Natural language processing]]). |
||
From a technical point of view semantic queries are precise relational-type operations much like a [[SQL|database query]]. They work on structured data and therefore have the possibility to utilize comprehensive features like operators (e.g. >, < and =), namespaces, [[pattern matching]], [[Type_inheritance|subclassing]], [[transitive_relation|transitive relations]], [[Semantic_Web_Rule_Language|semantic rules]] and contextual [[Full-text_index|full text search]]. The [[semantic web]] technology stack of the [[W3C]] is offering [[SPARQL]]<ref name="XML.com">{{cite web|url=http://www.xml.com/pub/a/2005/11/16/introducing-sparql-querying-semantic-web-tutorial.html |title=Introducing SPARQL: Querying the Semantic Web |publisher=XML.com|date=2005}}</ref><ref name="W3C">{{cite web|url=http://www.w3.org/TR/rdf-sparql-query |title=SPARQL Query Language for RDF |publisher=W3C|date=2008}}</ref> to formulate semantic queries in a syntax similar to [[SQL]]. Semantic queries are used in [[ |
From a technical point of view semantic queries are precise relational-type operations much like a [[SQL|database query]]. They work on structured data and therefore have the possibility to utilize comprehensive features like operators (e.g. >, < and =), namespaces, [[pattern matching]], [[Type_inheritance|subclassing]], [[transitive_relation|transitive relations]], [[Semantic_Web_Rule_Language|semantic rules]] and contextual [[Full-text_index|full text search]]. The [[semantic web]] technology stack of the [[W3C]] is offering [[SPARQL]]<ref name="XML.com">{{cite web|url=http://www.xml.com/pub/a/2005/11/16/introducing-sparql-querying-semantic-web-tutorial.html |title=Introducing SPARQL: Querying the Semantic Web |publisher=XML.com|date=2005}}</ref><ref name="W3C">{{cite web|url=http://www.w3.org/TR/rdf-sparql-query |title=SPARQL Query Language for RDF |publisher=W3C|date=2008}}</ref> to formulate semantic queries in a syntax similar to [[SQL]]. Semantic queries are used in [[Triplestore|triplestores]], [[Graph_databases|graph databases]], [[Semantic_wiki|semantic wikis]], natural language and artificial intelligence systems. |
||
== Background == |
== Background == |
||
Revision as of 10:21, 7 December 2014
Semantic queries allow for queries and analytics of associative and contextual nature. Semantic queries enable retrieval of both explicit and implicitly derived information based on syntactic, semantic and structural information contained in data. They are designed to deliver precise results (possibly the distinctive selection of one single piece of information) or to answer more fuzzy and wide open questions through pattern matching and digital reasoning.
Semantic queries work on named graphs or linked-data. This enables the query to process the actual relationships between information and infer the answers from the network of data. This is in contrast to semantic search, which uses semantics (the science of meaning) in language to produce a better search result (see Natural language processing).
From a technical point of view semantic queries are precise relational-type operations much like a database query. They work on structured data and therefore have the possibility to utilize comprehensive features like operators (e.g. >, < and =), namespaces, pattern matching, subclassing, transitive relations, semantic rules and contextual full text search. The semantic web technology stack of the W3C is offering SPARQL[1][2] to formulate semantic queries in a syntax similar to SQL. Semantic queries are used in triplestores, graph databases, semantic wikis, natural language and artificial intelligence systems.
Background
Relational databases contain all relationships between data in an implicit manner only.[3][4] For example the relationships between customers and products (stored in two content-tables and connected with an additional link-table) only come into existence in a query statement (SQL in the case of relational databases) written by a developer. Writing the query demands the exact knowledge of the database schema[5][6].
Linked-Data contain all relationships between data in an explicit manner. In the above example no query code needs to be written. The correct product for each customer can be fetched automatically. Whereas this simple example is trivial, the real power of linked-data comes into play when a network of information is created (customers with their geo-spacial informaion like city, state and country; products with their categories within sub- and super-categories). Now the system can automatically answer more complex queries and analytics that look for the connection of a particular location with a product category. The development effort for this query is omitted. Executing a semantic query is conducted by walking the network of information and finding matches (also called Data Graph Traversal).
Another important aspect of semantic queries is that the type of the relationship can be used to incorporate intelligence into the system. The relationship between a customer and a product has a fundamentally different nature then the relationship between a neighbourhood and its city. The latter enables the the semantic query engine to infer that a customer living in Manhattan is also living in New York City whereas other relationships might have more complicated patterns and "contextual analytics". This process is called inference or reasoning and is the ability of the software to derive new information based on given facts.
Articles
- Velez, Golda (2008). "Semantics Help Wall Street Cope With Data Overload". wallstreetandtech.com.
- Horwitt, Elisabeth (2011). "The semantic Web gets down to business". computerworld.com.
- Zhifeng, Xiao (2009). "Spatial information semantic query based on SPARQL". International Symposium on Spatial Analysis.
- Prudhommeaux, Eric (2010). "SPARQL vs. SQL - Introduction". Cambridge Semantics.
- Sequeda, Juan (2011). "SPARQL Nuts & Bolts". Cambridge Semantics.
- Rodriguez, Marko (2011). "Graph Pattern Matching with Gremlin". markorodriguez.com on Graph Computing.
- Kauppinen, Tomi (2012). "Using the SPARQL Package in R to handle Spatial Linked Data". linkedscience.org.
- Lorentz, Alissa (2013). "With Big Data, Context is a Big Issue". Wired.
- Dworetzky, Tom (2011). "How Siri Works: iPhone's 'Brain' Comes from Natural Language Processing". International Business Times.
- Aquin, Mathieu (2010). "Watson, more than a Semantic Web search engine" (PDF). Semantic Web Journal.
References
- ^ "Introducing SPARQL: Querying the Semantic Web". XML.com. 2005.
- ^ "SPARQL Query Language for RDF". W3C. 2008.
- ^ "Semantic queries in databases: problems and challenges". ACM Digital Library. 2009.
- ^ "Karma: A System for Mapping Structured Sources into the Semantic Web" (PDF). eswc-conferences.org. 2012.
- ^ "A Scalable Approach to Learn Semantic Models of Structured Sources" (PDF). 8th IEEE International Conference on Semantic Computing. 2014.
- ^ "Semantics for Big Data Integration and Analysis" (PDF). AAAI Fall Symposium on Semantics for Big Data. 2013.