W3C home > Mailing lists > Public > public-rww@w3.org > November 2012

Re: [WAC] regexps in WebAccessControl

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 19 Nov 2012 10:12:21 +0100
Cc: Ruben Verborgh <ruben.verborgh@ugent.be>, Read-Write-Web <public-rww@w3.org>
Message-Id: <3908C041-0CAA-497A-9C5A-5B7FE74FD67B@bblfish.net>
To: nathan@webr3.org

On 18 Nov 2012, at 22:06, Nathan <nathan@webr3.org> wrote:

> Henry Story wrote:
>>  []  wac:accessToClass [ wac:regex "http://joe.example/blog/.*" ];
> 
> What would [ wac:regex "http://joe.example/blog/.*" ] mean?
> 
> Using OWL 2 we can create a datatype definition, using a datatype restriction, on strings and the like - but that doesn't (anywhere near) cover what's required here.
> 
> I'm unsure how we'd actually create a Class of things based on the lexical form of a URI though, or even, whether it's a good idea to do so - we are basically saying that if a URI has a lexical form which matches the regular expression x, then that URI denotes something which is of the class y. This feels wrong.

That argument has already taken place [1] and has lead to a W3C standard known as POWDER.

  http://www.w3.org/standards/techs/powder

see for example 

  http://www.w3.org/TR/powder-formal/#typeAssertion

( it would be nice if that document were rewritten with Turtle examples )

I should have used POWDER directly, but just wanted to get going very quickly to see
what the use cases would be.

Henry


[1] http://www.w3.org/2001/sw/wiki/POWDER

> 
> Cheers,
> 
> Nathan

Social Web Architect
http://bblfish.net/



Received on Monday, 19 November 2012 09:12:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 19 November 2012 09:12:58 GMT