W3C home > Mailing lists > Public > public-wai-ert@w3.org > May 2005

Ensuring Assertions are identified

From: Charles McCathieNevile <chaals@opera.com>
Date: Tue, 10 May 2005 14:20:15 +0200
To: "public-wai-ert@w3.org" <public-wai-ert@w3.org>
Message-ID: <op.sqj671knwxe0ny@pc048.qadoc.oslo.opera.com>

Hi folks,

it seems that there is nothing in OWL, RDFS or RDF that lets us enforce a  
constraint that an Assertion is identifiable.

We can find Assertions that don't have an identifier by using a SPARQL  
query with the filter isBlank(). Then there is a question of how to deal  
with this.

It may be possible in OWL to say that the class of ValidAssertions is  
disjoint with the class of things that can be found by a SPARQL query, by  
defining our own terms. We could also perhaps use the log:uri property  
developed by TimBL for CWM

	This allows one to look at the actual string of the URI which identifies  
this. (Cwm can get the URI of a resource or get the resource from the  
URI.) This is a level breaker, breaking the rule of not looking inside a  
URI. Use (eg with string:match) to replace RDF's old "aboutEach"  
functionality. Use to implement the URI spec and protocol specs, etc.
]] - http://www.w3.org/2000/10/swap/doc/CwmBuiltins

I think that we should just suggest that doing this is a best practice,  
and tools MAY provide a warning (for example something like the  
interoperability analyser of Libby's that Jim pointed to last week.



Charles McCathieNevile                              chaals@opera.com
                  se habla español - nous parlons français
   Here's one we prepared earlier:   http://www.opera.com/download
Received on Tuesday, 10 May 2005 12:20:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:52:49 UTC