- From: Hugh Glaser <hugh@glasers.org>
- Date: Mon, 14 Jul 2014 13:44:24 +0100
- To: Victor Porton <porton@narod.ru>
- Cc: SW-forum Web <semantic-web@w3.org>
Hi Victor,
I think that if you are creating a world where URIs intentionally no longer identify things uniquely you have moved into a world that is no longer relevant to this list.
The only SemWeb-consistent reading I can make of your brief document about the Alex example is that you are using :Alex to be the set of people that have the URI :Alex (by construction).
I think I might understand what you want if you could elaborate what the Alex example looks like in your new language, please?
The example gets too complicated compared with the :Alex motivation, for me to work through.
In fact an RDF rendering of what I think you want is:
@prefix : <http://www.example.org/rdf#>.
:Alex :hasObject [
:sex :male ;
:age 10 ].
:Alex :hasObject [
:sex :female ;
:age 15 ].
You could of course define a new language as being the syntax for such an RDF graph, where perhaps URIs in the subject position always have an implied predicate of :hasObject, or whatever you want.
Hugh
On 14 Jul 2014, at 07:28, Ruben Verborgh <ruben.verborgh@ugent.be> wrote:
>> I've started to write about my new format alternative to RDF:
>
> I'm afraid that your new format is not only different from RDF,
> but also different to practice on the Web in general:
>
> "Now it is clear that these are two different Alexes
> (even despite they share the same object URL :Alex)."
> — http://freesoft.portonvictor.org/binaries/NLang.pdf
>
> Having two different things identified by the same URL
> will be very hard to retrofit on today's Web.
> If I GET Alex' URL, which of two Alexes will I receive?
>
> How would you make this compatible with the rest of the Web?
>
> Ruben
--
Hugh Glaser
20 Portchester Rise
Eastleigh
SO50 4QS
Mobile: +44 75 9533 4155, Home: +44 23 8061 5652
Received on Monday, 14 July 2014 12:45:40 UTC