Chris Bizer wrote:
>>>Another comment from him was, that he would like to
>>>have a mechanism to say that a URI should be interpreted as an external
>>link
>>>(to an HTML page, SPARQL query, or whatever). Something that we have
>>>discussed and decided to delete from the spec for some reasons. Does
>>anybody
>>>remember the reasons?
>>
>>I'm not sure I see what you are refering to exactly by "interpreted as
>>an external link". Is that about the link behavior (i.e. open in a new
>>window, or in the same window)?
>
> That URI http://www.bizer.de shouldn't be interpreted as a RDF Resource,
> meaning that the browser looks in the repository for information about the
> resource, but as an external UR*L* which is retrieved and displayed.
Isn't the browser smart enough to figure that out by itself?
>>The question is: do we really need to make this information available to
>>XSLT transformations? I'm not convinced it is the case. What would they do
>>with these URIs?
>
>
> I thing we should stay general and not only think about XSLT but also about
> stuff like Haystack display widgets which display and maybe also allow the
> user to edit the data. For being able to write data back to the repository
> later they need to know the resource and property URIs.
Exactly, I was staying general. What I mean is that advanced tools such
as Haystack can handle the NS prefix binding resolution in attribute
values problem. Only "dumb" tools such as XSLT cannot, and I was
wondering if it was necessary to move away from modeling URIs in
attributes just because XSLT-like tools have a hard time handling these,
considering that there is little chance they'll actually exploit this
particular information.
>>I like it, but you're not solving the NS prefix binding expansion
>>problem, as you have URIs in #PCDATA. So I don't understand what is the
>>benefit of writing:
>>
>><inter:Resource>
>> <inter:uri>http://foo.org/Stefano</inter:uri>
>> [...]
>></inter:resource>
>>
>>instead of:
>>
>><inter:Resource uri="http://foo.org/Stefano">
>> [...]
>></inter:resource>
>>
>>
>>You can address attributes in XPath using the _at_ axis (e.g.
>>inter:Resource/_at_uri)
>>
>
>
> No direct benefit for <inter:uri>, but a benefit for <inter:type> because
> you can have several <inter:type> elements but only one type="" attribute.
Yes.
> And as I had to model type that way, I also modelled URI that way.
I understand.
--
Emmanuel Pietriga
INRIA Futurs - Projet In Situ tel : +33 1 69 15 34 66
Bat 490, Université Paris-Sud fax : +33 1 69 15 65 86
91405 ORSAY Cedex http://www.lri.fr/~pietriga
Received on Tue May 03 2005 - 13:17:05 EDT