MathQL

From: Ferruccio Guidi Date: Wed, 30 Jul 2003 15:29:52 +0000 (+0000) Subject: - information about the database map added in whatsnew.html X-Git-Tag: LucaOK~10 X-Git-Url: http://matita.cs.unibo.it/gitweb/?a=commitdiff_plain;h=686e22323249fbfdaf21f53b5a11fe73df52f3b9;p=helm.git - information about the database map added in whatsnew.html - spell checked --- diff --git a/helm/mathql/homepage/authors.html b/helm/mathql/homepage/authors.html index 16661199a..222216cdb 100644 --- a/helm/mathql/homepage/authors.html +++ b/helm/mathql/homepage/authors.html @@ -76,7 +76,7 @@ 2002.

Ferruccio Guidi obtained a Master degree in Mathematics -at the Univerity of Padova and a PhD in Computer Science at the University +at the University of Padova and a PhD in Computer Science at the University of Bologna. His research interests include computer-assisted proof development, Martin-Löf type theory and substructural logic. He is a member of the HELM Working Group and @@ -84,8 +84,8 @@ of the "Paulus Venetus" Research Group in Logic.

Irene Schena obtained a Master Degree in Computer Science -and a Ph.D. in Computer Science at the Univerity of Bologna. Her research -interests include Linear Logic and Web Tecnologies. She is a member of the +and a Ph.D. in Computer Science at the University of Bologna. Her research +interests include Linear Logic and Web Technologies. She is a member of the HELM Working Group and of the W3C Math Working Group.

diff --git a/helm/mathql/homepage/documentation.html b/helm/mathql/homepage/documentation.html index 7c00983d2..45edae9d3 100644 --- a/helm/mathql/homepage/documentation.html +++ b/helm/mathql/homepage/documentation.html @@ -106,7 +106,7 @@ Retrieving in Content-based Repositories of Formal Mathematical Knowledge - Papers concerning the erlier versions of MathQL-1:
+ Papers concerning the earlier versions of MathQL-1:

F. Guidi and I. Schena: A Query Language for a Metadata diff --git a/helm/mathql/homepage/features.html b/helm/mathql/homepage/features.html index 12a6d7a50..46701166a 100644 --- a/helm/mathql/homepage/features.html +++ b/helm/mathql/homepage/features.html @@ -123,7 +123,7 @@ what part of a solution should be preserved or discarded.

MathQL-1 query results have a 4-dimensional geometry whereas other languages assume that query results are returned in 1-dimensional -structures (ie lists of resources) or 2-dimensional structures (ie relational +structures (i.e. lists of resources) or 2-dimensional structures (i.e. relational database tables). This allows to get better outcomes from queries returning structured results.

diff --git a/helm/mathql/homepage/implementation.html b/helm/mathql/homepage/implementation.html index 2d774a953..5b41f9d08 100644 --- a/helm/mathql/homepage/implementation.html +++ b/helm/mathql/homepage/implementation.html @@ -100,7 +100,7 @@ near future. href="http://www.cs.unibo.it/cgi-bin/cvsweb/helm/ocaml/mathql_generator/">mathql_generator) allows to build specific kinds of MathQL-1 queries, which are meaningful in the context of HELM, starting from a high-level description of the wanted - results. These queries are descibed at an abstract level in the following + results. These queries are described at an abstract level in the following paper: @@ -117,7 +117,7 @@ near future.

The testing software for the MathQL-1 Suite (mathql_test) - providides three textual interfaces (one for the basic package, one for + provides three textual interfaces (one for the basic package, one for the interpreter and one for the query generator) with specific features meant for testing.

@@ -125,7 +125,7 @@ the interpreter and one for the query generator) with specific features meant
The current version of the Suite, realized entirely by F. Guidi, implements MathQL-1 version 3 (i.e. MathQL-1.3). The newly implemented features, which - are not included in the ufficial documentation + are not included in the official documentation yet, are reported in the What's new section.

The latest MathQL - + - + - + - +
MathQL-1
- +
A query language for RDF metadata
- + - - - + + - + - - - +
+ Other languages to be developed in the context of the MathQL proposal + will be suitable for queries about the semantic structure of mathematical + data: this will include content-based pattern-matching (MathQL-2) and possibly + other forms of formal matching involving for instance isomorphism, unification + and definitions expansion (MathQL-3).
+ + + +
+
- +
-
Forward
-
+
Forward
+
- +
- +
-
Features
+
Features
- +
- +
-
What's new
- +
What's new
+
- +
-
Documentation
+
Documentation
- +
- +
-
Implementation
-
+
Implementation
+
- +
- +
-
The authors
-
+
The authors
+
- +
- +
-
Links
-
+
Links
+
- +
-
- - +
+ +
Forward
-
-
- The MathQL proposal rises in the context of the HELM project, which aims at the -development of a suitable technology for the creation and maintenance -of a virtual, distributed, hypertextual library of structured mathematical - knowledge based on XML technology, -through the integration of the current proof assistants and logical frameworks -with the most recent technologies for the development of Web applications -and electronic publishing.
-
- The objective of the MathQL proposal is the development of a -set of query languages enabling the retrieval of formalized mathematical -Web resources on the basis of content-aware requests. The first of these - languages, MathQL-1, is focused on querying an arbitrary - RDF database because RDF is the - W3C standartd for describing Web - resources at the general-purpose content level.
-
- As an RDF query language, MathQL-1 provides the main features -required by the RDF community while complying with the needs of HELM. -The peculiar aspects of this language concern the query results, which -are highly structured and possess their own syntax, formally explained -by a rigorous semantics.
+ +
+ The MathQL proposal rises in the context of the HELM project, which aims at the development +of a suitable technology for the creation and maintenance of a virtual, +distributed, hypertextual library of structured mathematical knowledge +based on XML technology, through the + integration of the current proof assistants and logical frameworks with +the most recent technologies for the development of Web applications and +electronic publishing.
+
+ The objective of the MathQL proposal is the development of a +set of query languages enabling the retrieval of formalized mathematical +Web resources on the basis of content-aware requests. The first of these + languages, MathQL-1, is focused on querying an arbitrary + RDF database because RDF is +the W3C standard for describing +Web resources at the general-purpose content level.

- MathQL-1 is particularly helpful in distributed systems where - query engines are implemented as stand-alone units, because in this -situation the query results are exchanged between the system components -as well as the queries, and thus both the queries and the query results + As an RDF query language, MathQL-1 provides the main features + required by the RDF community while complying with the needs of HELM. + The peculiar aspects of this language concern the query results, which + are highly structured and possess their own syntax, formally explained + by a rigorous semantics.
+
+ MathQL-1 is particularly helpful in distributed systems where + query engines are implemented as stand-alone units, because in this +situation the query results are exchanged between the system components +as well as the queries, and thus both the queries and the query results need to be encoded in a clearly defined format.
-
- Other languages to be developed in the context of the MathQL proposal - will be suitable for queries about the semantic structure of mathematical - data: this will include content-based pattern-matching (MathQL-2) and possibly - other forms of formal matching involving for instance isomorphism, unification - and definitions expansion (MathQL-3).
-

-
-
- +
+
+
This site is maintained by Ferruccio Guidi, last update: July -10, 2003.
-
-
+30, 2003.
+
+ +

diff --git a/helm/mathql/homepage/links.html b/helm/mathql/homepage/links.html index a56faa15d..878c68174 100644 --- a/helm/mathql/homepage/links.html +++ b/helm/mathql/homepage/links.html @@ -3,91 +3,94 @@ MathQL - + - + - + - +
MathQL-1
- +
A query language for RDF metadata
- + - - - + + - + - - - + + +
The developers wishing to have their RDF query language + listed here may contact the authors.
+
+ + + +
- +
+
-
Forward
-
+
Forward
+
- +
- + +
-
Features
- +
Features
+ +
- + +
-
What's new
- +
What's new
+
- +
-
Documentation
+
Documentation
- +
- +
-
Implementation
-
- +
Implementation
+
+
- +
-
The authors
-
+
The authors
+
- +
- +
-
Links
-
- +
Links
+
+
-
- - +
+ +
Links
-
- + +
-
HELM Project homepage, +
HELM Project homepage, MOWGLI Project homepage
- +
- +
-
W3C XML resources, +
W3C XML resources, W3C RDF resources
- +
- +
-
Some RDF query languages having a homepage
- -
+
Some RDF query languages having a homepage
+ +
DAML+OIL rdfDB RDFPath TRIPLE SquishQL XDD
-
- -
The Developers wishing to have their RDF query language -listed here may contact the authors.
-
-

-
+
+

diff --git a/helm/mathql/homepage/whatsnew.html b/helm/mathql/homepage/whatsnew.html index 72b12ff7c..e00096b64 100644 --- a/helm/mathql/homepage/whatsnew.html +++ b/helm/mathql/homepage/whatsnew.html @@ -3,139 +3,267 @@ MathQL - + - + - + - +
MathQL-1
- +
A query language for RDF metadata
- + - - - + + - + - - - + +
+
The property operator now accepts more than one isfalse + clause to increase the complexity of the constraint condition used to filter + the raw query results. This feature is exploited in the queries produced +by the HELM query generator.
+ +
+
+
+
+
The PostgreSQL database map:
+
+The PostgreSQL database map is a file describing how the MathQL-1 +interpreter must interact with the underlying PostgreSQL database, when it +is run in Postgres mode. Currently this file contains the following information:
+
+
the database connection string to be used when the interpreter +opens a connection with the database;
+
+
+
the map describing the correspondence between the metadata +access paths used by the property operator and the fields of the database +tables.
+
+The format of the file is textual and line oriented, but a corresponding +XML syntax will be provided soon.
+The first line must contain the database connection string and the subsequent +lines contain the map with the following syntax:
+
+
blank lines: ignored (used for separation);
+
+
+
lines starting with a # followed by a space: ignored (used for +comments);
+
+
+
+
<table_name> <field_name> "<-" +[ <path_component> ]*
+
+
+
the information about the metadata denoted by the given +path is found in the given field of the given table in the database. For +example the line:
+
+refobj h_occurrence <- refObj h:occurrence
+
+tells that the metadata denoted by the path /"refObj"/"h:occurrence" +is found in the field "h_occurrence" of the table "refobj" in the database, +while:
+
+refobj source <-
+
+tells that the metadata denoted by the path / is found in the field +"source" of the table "refobj" in the database;
+
+
+
<table_name> <field_name> "<+" +[ <path_component> ]*
+
+
+
same as the previous but defines a default table and field +for the given path. This is used to force the interpreter to query a particular +table when the information denoted by a path can be found in more than one +table and field. For example:
+
+objectname source <+
+refobj      source <-
+refrel      source <-
+refsort     source <-
+
+tells that the metadata denoted by the path / is found in the "source" +field of the "objectname", "refobj", "refrel" and "refsort" tables, and that +the first choice is preferred;
+
+
+
<table_name> "<-" [ <path_component> ]*
+
+
the given path denotes a structured metadata whose components +are found in the fields of the given table. For example:
+
+refobj <- refObj
+
+tells that the path /"refObj" denotes a structured metadata whose +components are found in the fields of the table "refobj";
+
+
+
<table_name> "<+" [ <path_component> ]*
+
+
same as the previous but tells that this is a default correspondence; +
+
+
+
<virtual_table_name> "->" <concrete_table_name>
+
+
defines a correspondence between a virtual table name an +a concrete table name. All the <table_name> entries represent virtual +table names that are mapped to concrete table names using the identity function +unless a particular mapping is defined for them using the above construction. +This mechanism allows to define several set of metadata on the same database +table as in:
+
+refobj      source      + <-
+refobj      h_occurrence <- + refObj       h:occurrence
+backpointer source       + <- backPointer h:occurrence
+backpointer h_occurrence <-
+backpointer + -> refobj
+
+
which defines four path accessing two virtual tables ("refobj" +and "backpointer") and then maps these tables in a single concrete table;
+
+
+
"->"
+
+
+
a line like this must end the map file.
+
+Here you can find the current +version of PostgreSQL database map for HELM.
+
+ How does the interpreter use the map? The map file is read during +the interpreter initialization process from the file pointed by the MATHQL_DB_MAP +environment variable and is used during the execution of each property +operation in the issued queries.When executing a property operation, +the interpreter uses the map to find the smallest set of database tables +containing the information required by the given access paths and then queries +these tables to obtain the wanted information.
+ + + +
- +
+
-
Forward
-
+
Forward
+
- +
- + +
-
Features
- +
Features
+
- +
-
What's new
-
- +
What's new
+
+ +
- + +
-
Documentation
+
Documentation
- +
- +
-
Implementation
-
- +
Implementation
+
+
- +
-
The authors
-
+
The authors
+
- +
- +
-
Links
-
- +
Links
+
+
-
- - +
+ +
What's new
-
-
- This page reports the newly implemented - features of MathQL-1 that are not included in the ufficial + + This page reports the newly implemented + features of MathQL-1 that are not included in the official documentation yet.
-
- Changes and additions to MathQL-1 operators:
- +
+
+
+
Changes and additions to MathQL-1 operators:
+
+
-
The add operator now accepts a syntax extension allowing -to specify more than one explicit attribute group.
- +
The add operator now accepts a syntax extension allowing + to specify more than one explicit attribute group.
+
- +
The syntax now is:
- -
<query> := "add" [ "distr" ]? [ <groups> | <avar> -] "in" <query>
- <groups> := <group> [ ";" <group> ]*
- <group> := <attribute> [ "," <attribute> ]*
- <attribute> := <value> "as" <path>
-
- Examples:
- the query add "1" as "a", "2" as "b" in subj "A" gives the result - "A" attr {"a"="1"; "b"="2"} while
- the query add "1" as "a"; "2" as "b" in subj "A" gives the result - "A" attr {"a"="1"}, {"b"="2"}.
-
- -
-
The new align operator takes an integer i (represented -as a string), a multiple string value v and returns the same v -where each string with length n < i is prefixed with i - n -spaces. The syntax of the add operator is:
- -
- + +
<query> := "add" [ "distr" ]? [ <groups> | +<avar> ] "in" <query>
+ <groups> := <group> [ ";" <group> ]*
+ <group> := <attribute> [ "," <attribute> ]*
+ <attribute> := <value> "as" <path>
+
+ Examples:
+ the query add "1" as "a", "2" as "b" in subj "A" gives the result + "A" attr {"a"="1"; "b"="2"} while
+ the query add "1" as "a"; "2" as "b" in subj "A" gives the result + "A" attr {"a"="1"}, {"b"="2"}.
+
+ +
+
The new align operator takes an integer i (represented + as a string), a multiple string value v and returns the same v + where each string with length n < i is prefixed with i - n + spaces. The syntax of the add operator is:
+ +
+
<value> := "align" <string> "in" <value>
-
- This operators aligns strings containing numbers so that their alphabetic -order agrees with their numeric order.
-
- -
-
The intersect operator now intersects the attribute groups -of the mathing subject strings set-theoretically rather than making their -"Cartesian product". This semantics reduces the computational costs and makes -intersection the dual of union.
- -
- -
-
The property operator now accepts more than one isfalse -clause to increase the complexity of the constraint condition used to filter -the raw query results. This feature is exploited in the queries produced -by the HELM query generator.
-
- + This operators aligns strings containing numbers so that their alphabetic + order agrees with their numeric order.
+ + +
+
The intersect operator now intersects the attribute +groups of the matching subject strings set-theoretically rather than making +their "Cartesian product". This semantics reduces the computational costs +and makes intersection the dual of union.
+
-

-
-
+