RE: Semantic content negotiation (was Re: expectations of vocabulary)

--Richard,

>    The hash-or-slash debate *is* relevant here. Dereferencing
> 
>      http://example.com/ontology#myProperty
> 
>    fetches
> 
>      http://example.com/ontology
> 
>    which is the base ontology URL, and looks at the fragment 
> ID on the client side. Dereferencing
> 
>      http://example.com/ontology/myProperty
> 
>    tries to fetch an entirely different URL, which in my case 
> is highly likely to be a 404. If you choose slashes, you 
> either need a smart server (e.g., URIQA) or a smart crawler 
> on the client. I prefer the former, but Apache ain't it.

We are talking about IF a resource is dereferencable but not HOW a resource
can be dereferenced.  Whehter using fragment identifier is irrelevant, don't
you think?  Again, let's not steer away the direction.  Otherwise, we will
have endless debate on anything.

Xiaoshu