Re: TMQL, next round

--===============1979918571==
Content-Type: multipart/alternative; 
	boundary="----=_Part_164293_22325399.1173177105017"

------=_Part_164293_22325399.1173177105017
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello Robert,

Before you are going to talk too much too yourself and listing the issues
one by one..

For the second issue (see here below) I have something. I think there should
be several functions and predicates be included in TMQL. For instance a
SUMMATION function on financial data is very essential. Customers need to
see the ROI of Topic Maps :)
The only question is then which pretty basic functions and predicates do we
need and which one are more typically in the direction of an 'ontology
definition language'.

By the way very cool work on TMQL and impressive issue list.. lot of high
impacts ;)

Gabriel

Issue 2 is:

TMQL Issue: TM paradigmatic functions, predicates, templates, ontologies
Impact on Language: very high

Background
TMQL uses the TM paradigm not hypocritically in that it offers querying of
data according to the TM paradigm; TMQL also
tries to exploit the paradigm for language features which are traditionally
not seen as topic-mappish.
In this sense language constructs such as functions, predicates, but also
namespace prefixes are interpreted as subjects,
represented in a map by topics of certain predefined TMQL types, such as
tmql:function.
A function is a systematic functional dependency over particular sets of
values. The age of a person is functionally
dependent on (a) the person's birthdate and (b) the current time.
Similarily, a predicate is a constraint on a constellation of
particular values.
Accordingly, both are expressing additional knowledge about a problem
domain. As the modelling of an application domain
is usually done via an ontology definition language, one can argue that
functions and predicates should NOT be part of
TMQL, which is meants as a data access language.
Structured Discussion
? Should Functions and Predicates be included into TMQL
- both are ontological information, should go into an ontology language
- yes, but TMCL will not offer them, neither does CTM, ...
+ they are EXTREMELY useful to organize the query, uhm knowledge
- SPARQL does not have function declarations or predicate declarations


On 2/26/07, Robert Barta <[email protected]> wrote:
>
> Hi all,
>
> You may have noticed that the latest TMQL draft was submitted
> recently
>

------=_Part_164293_22325399.1173177105017
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello Robert,<br>
<br>
Before you are going to talk too much too yourself and listing the issues one by one..<br>
<br>
For the second issue (see here below) I have something. I think there
should be several functions and predicates be included in TMQL. For
instance a SUMMATION function on financial data is very essential.
Customers need to see the ROI of Topic Maps :)<br>
The only question is then which pretty basic functions and predicates
do we need and which one are more typically in the direction of an
&#39;ontology definition language&#39;.<br>
<br>
By the way very cool work on TMQL and impressive issue list.. lot of high impacts ;)<br>
<br>
Gabriel <br>
<br>
Issue 2 is:<br>
<br>
TMQL Issue: TM paradigmatic functions, predicates, templates, ontologies<br>
Impact on Language: very high<br>
<br>
Background<br>
TMQL uses the TM paradigm not hypocritically in that it offers querying of data according to the TM paradigm; TMQL also<br>
tries to exploit the paradigm for language features which are traditionally not seen as topic-mappish.<br>
In this sense language constructs such as functions, predicates, but also namespace prefixes are interpreted as subjects,<br>
represented in a map by topics of certain predefined TMQL types, such as tmql:function.<br>
A function is a systematic functional dependency over particular sets of values. The age of a person is functionally<br>
dependent on (a) the person&#39;s birthdate and (b) the current time. Similarily, a predicate is a constraint on a constellation of<br>
particular values.<br>
Accordingly, both are expressing additional knowledge about a problem domain. As the modelling of an application domain<br>
is usually done via an ontology definition language, one can argue that functions and predicates should NOT be part of<br>
TMQL, which is meants as a data access language.<br>
Structured Discussion<br>
? Should Functions and Predicates be included into TMQL<br>
- both are ontological information, should go into an ontology language<br>
- yes, but TMCL will not offer them, neither does CTM, ...<br>
+ they are EXTREMELY useful to organize the query, uhm knowledge<br>
- SPARQL does not have function declarations or predicate declarations<br>
<br><br><div><span class="gmail_quote">On 2/26/07, <b class="gmail_sendername">Robert Barta</b> &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>You may have noticed that the latest TMQL draft was submitted<br>recently<br></blockquote></div>

------=_Part_164293_22325399.1173177105017--

--===============1979918571==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tmql-wg mailing list
[email protected]
http://www.isotopicmaps.org/mailman/listinfo/tmql-wg

--===============1979918571==--