W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2004

Re: PS-8: Query with Datatype Value Comparison & Support for Arbitrary Datatypes in Query

From: Patrick Stickler <patrick.stickler@nokia.com>
Date: Fri, 2 Apr 2004 11:20:53 +0300
Message-Id: <A864BCE2-847E-11D8-B128-000A95EAFCEA@nokia.com>
Cc: public-rdf-dawg@w3.org
To: "ext Janne Saarela" <janne.saarela@profium.com>


On Apr 02, 2004, at 10:49, ext Janne Saarela wrote:

>
>
> Following yesterday's teleconference I would like to continue
> discussion on this support for arbitrary datatypes in a query.
>
> I suggested that if the support is really for any arbitrary
> datatype, for a DAWG recommendation compatible RDF query
> processor we need to lay a set of minimal datatypes it needs
> to support. This would enable us to lay a minimal set of
> operators that operate on these datatypes.
>
> I suggest the minimal set of datatypes would be a
> subset of all XML Schema datatypes. I leave it up to
> further discussion to see which ones are truly necessary.

I support both of these requirements.

1. Any typed literal value which can be expressed in RDF/XML must
    also be expressible in the DAWG QL in terms of the same datatype
    URI and lexical form. There are thus no restrictions on the
    datatypes that one can use to express a query.

If a given datatype expressed in a query is not recognized/supported,
the query either fails, since no comparisions can be made, or (my
preference) a warning/error is issued about the unsupported datatype).

2. A core set of datatypes, ideally based on the XML Schema predefined
    datatypes, will be specified as manditory.

As for the latter, the list should be as short as possibly. Perhaps 
only:

xsd:string
xsd:decimal, and some/all its derived subtypes
xsd:date
xsd:dateTime
xsd:anyURI
xsd:base64Binary
xsd:boolean


Patrick



>
> Janne
>
>> A client wishes to discover all resources which are of rdf:type
>> ex:Person, and have an ex:ageInYears which is between "16"^^ex:count
>> and "18"^^ex:count, inclusive.
>> The client is aware of a knowledge source from which such
>> resources might be discovered.
>> Following the DAWG recommendation, the client formulates a query
>> which expresses the desired characteristics to match and submits
>> the query to the knowledge source.
>> The knowledge source returns zero or more resource descriptions
>> describing the matched resources.
>> -- 
>> I deliberately used unknown datatypes in this example to illustrate
>> the need to be able to allow arbitrary datatypes in input queries,
>> regardless of what datatypes a particular query resolution engine
>> may be able to handle.
>> Note that if the client is able to include auxiliary knowledge
>> which may be relevant to resolution of the query along with
>> the query itself (e.g. in a single input RDF graph) this would allow
>> the client to provide information about the terminology used
>> in the query, such as about the nature of particular datatypes,
>> their relationship to other datatypes, and even references to
>> formal definitions of the datatypes which could be used by the
>> knowledge source to evaluate typed literals and perform comparisons.
>> E.g. the auxiliary knowledge could indicate an XML Schema which
>> defines the datatype in question, and if the knowledge source is
>> able to understand XML Schemas, could load and utilize to deal
>> with values of that datatype.
>> -- 
>> Patrick Stickler
>> Nokia, Finland
>> patrick.stickler@nokia.com
>
>
> -- 
> Janne Saarela <janne.saarela at profium.com>
> Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland
>
>

--

Patrick Stickler
Nokia, Finland
patrick.stickler@nokia.com
Received on Friday, 2 April 2004 03:23:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:19 GMT