[
Lists Home |
Date Index |
Thread Index
]
[Jonathan Borden]"
> For RDF/OWL applications, we can assume that when property URIrefs are
> dereferenced it will be with Accept: application/rdf+xml
>
> In that case, there is no confusion at all. RDF/OWL applications will get
> back an OWL description of the property. An OWL application understands
> exactly that the following URIref:
>
> http://www.w3.org/TR/2003/WD-owl-guide-20030331/wine.owl#TableWine
>
> which dereferences to:
>
> <owl:Class rdf:ID="TableWine">
> <owl:subClassOf>
> <owl:Class>
> <owl:intersectionOf rdf:parseType="Collection">
> <owl:Class rdf:about="#Wine" />
> <owl:Restriction>
> <owl:onProperty rdf:resource="#hasSugar" />
> <owl:hasValue rdf:resource="#Dry" />
> </owl:Restriction>
> </owl:intersectionOf>
> </owl:Class>
> </owl:subClassOf>
> </owl:Class>
>
> means the class of TableWine. To the RDF/OWL appliction this DOES NOT mean
> the XML element owl:Class[@rdf:ID="TableWine"] because the RDF and OWL
model
> theories define this piece of XML to be interpreted as an OWL class. That
is
> to say RDF and OWL have a very definite semantics defining an
interpretation
> of the XML and/or N-Triples syntax on which they might be based.
OK, no problem here. And
http://www.w3.org/TR/2003/WD-owl-guide-20030331/wine.owl#TableWine would
mean the same class even if it were not dereferenceable, would it not? Of
course, then the app would have to find that out some other way without
loading it from the network.
Now how about plain RDF without OWL, which (as I now realize) is more what I
was thinking of? I do not recall that plain RDF has any conventions about
this. I have to admit, though, that restricting Accept to be
application/rdf+xml is rather a nice trick.
Cheers,
Tom P
|
