- From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
- Date: Wed, 28 Feb 2007 14:16:20 +0100
- To: ERT group <public-wai-ert@w3.org>
Shadi Abou-Zahra schrieb: > > Hi Johannes, > > I think the idea was to have a "Request-URI" class with predefined > values. The respective property (say requestURI) would then point to the > value in the rdf:resource (analogous to earl:Outcome). Here an example: > > <http:OptionsRequest rdf:ID="req"> > <http:requestURI rdf:resource="&http;#asterisk"/> > ... > </http:OptionsRequest> > > > <rdfs:Class rdf:about="&http;Request-URI"> > <rdfs:label xml:lang="en">Request URI</rdfs:label> > <rdfs:comment xml:lang="en">Request-URI = "*" | absoluteURI | abs_path > | authority</rdfs:comment> > <owl:oneOf rdf:parseType="Collection"> > <owl:Thing rdf:about="&http;#asterisk"> > <rdfs:label xml:lang="en">Asterisk</rdfs:label> > <rdfs:comment xml:lang="en">The value "*"</rdfs:comment> > </owl:Thing> > ... > </owl:oneOf> > </rdfs:Class> > > <rdf:Property rdf:about="&http;#requestURI"> > <rdfs:label xml:lang="en">Has Request URI</rdfs:label> > <rdfs:domain rdf:resource="&http;#OptionsRequest"/> > <rdfs:range rdf:resource="&http;#Request-URI"/> > </rdf:Property> This is possible for asterisk. But what do you think about abs_path, absoluteURI or authority? -- Johannes Koch BIKA Web Compliance Center - Fraunhofer FIT Schloss Birlinghoven, D-53757 Sankt Augustin, Germany Phone: +49-2241-142628 Fax: +49-2241-142065
Received on Wednesday, 28 February 2007 13:17:03 UTC