Print

Print


That is correct. For more see:

http://www.w3.org/TR/2014/REC-rdf11-mt-20140225/#shared-blank-nodes-unions-and-merges
On Nov 18, 2014 12:38 PM, "Thomas Berger" <[log in to unmask]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 18.11.2014 um 18:06 schrieb Simon Spero:
>
>
>
> > Suppose we have the following file:
> > ---------------
> > _:x rdf:type :Weasel.
> > _:x :favoriteEggType :Chicken .
> > ----------------
> >
> > This says that there is something that is a Weasel and whose favorite
> type
> > of egg is Chicken.
> >
> > If we see this twice, we cannot tell how many chicken pickin Weasels we
> > have.
>
> I found that statement of yours a bit ambiguous and hope you don't mind
> me trying to clarify:
>
> It depends on /where/ we see this...
>
> In the file you mentioned there is /one/ anonymous chicken pickin weasel
> temporarily referred to as (named) _:x
>
> Any repetition of the statement and any other statement using _:x in
> subject or object position would refer to the very same weasel, *as
> long as stated in the same file*.
>
> (It's exactly as in your usage of "the following file": You don't
> give it a name and if you use the same words in another mail I
> couldn't know whether it is the one from this mail or a completely
> new one...)
>
>
> > A different file could use _:x to refer to some Chicken.
>
> There the differences start as we can never tell whether _:x in
> the different file is the same one or a different one anonymous
> animal.
>
> In practice this matters when one wants to add or remove individual
> statements or subgraphs from graphs: When the graphs or subgraphs
> have blank nodes as their origin, you usually can't.
>
> viele Gruesse
> Thomas Berger
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iJwEAQECAAYFAlRrg5oACgkQYhMlmJ6W47MuxgP9GF9yjeuwXSyQmZsmDYwZXhXS
> tnK8uoVFn+ifljgYZkyYOJH2c5SekEGvnOR/49QCHcrLiOA9H1ZdFPXHJoEyj3vV
> z+lBUw4qq6EdridiZ6sG/ZLmvjdrdL439te9hzJ/jWiYRWrv19MBkKwcBgc4p1WN
> CDZIA1Hv8JsyVGyG7Kw=
> =5L/V
> -----END PGP SIGNATURE-----
>