W3C home > Mailing lists > Public > www-mobile@w3.org > September 2002

Re: CC/PP and UAProf implementation experiences

From: Janne Saarela <janne.saarela@profium.com>
Date: Mon, 23 Sep 2002 17:18:55 +0300
Message-ID: <3D8F22CF.5020803@profium.com>
To: Art.Barstow@nokia.com
CC: www-mobile@w3.org

Hello again

Ah, this is something I did not indicate in my test report:

Profium has developed support for typed literal nodes
in the RDF data model in our SIR platform.

This is accomplished using URI references to XML Schema
basic data types in the range predicate.

Here's an example:

<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#double" />

This is something RDF Core WG should be deciding upon soon
enough I hope. Otherwise Profium is building on top of an
unstandard approach.

This partly helps us validate data types of various predicates.
By default we expect the literal nodes to be of type

So yes, the type: in the comments is something we can
support in an unstandard fashion at the moment. Resolution
strategy is something we have not needed yet.


> Currently, the schema uses the rdfs:comment property like this:
> <rdfs:comment>
>     Description: Indicates whether the device's display 
>       supports color. "Yes" means color is supported. "No" 
>       means the display supports only grayscale or black and white. 
>     Type: Boolean 
>     Resolution: Override 
>     Examples: "Yes", "No"
> </rdfs:comment> 
> Note important information (e.g. Type) is actually embedded in the
> contents of the rdfs:comment property (rather than for example being
> a separate property).  I presumed an application that did profile validation 
> via the schema would need to micro-parse the contents of this property
> to determine Type information.

Janne Saarela <janne.saarela@profium.com>
Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland
Tel. +358 (0)9 855 98 000 Fax. +358 (0)9 855 98 002
Mob. +358 (0)40 508 4767  Internet: http://www.profium.com
Received on Monday, 23 September 2002 10:18:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:03 UTC