W3C home > Mailing lists > Public > semantic-web@w3.org > May 2017

Re: I am.

From: Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk>
Date: Fri, 19 May 2017 16:57:08 +0100
Message-ID: <20170519165708.GB24674@biggiebuntu>
To: Sarven Capadisli <info@csarven.ca>
Cc: W3C Semantic Web IG <semantic-web@w3.org>
On Wed, 17 May 2017 11:24:11 +0200, Sarven Capadisli <info@csarven.ca> wrote:
> Philosophers and Semantic Web junkies gather around.
> Use the the RDF language to represent the following statement:
> "I am."

(Turtle notation):

  _:I a [] .

We don't know who "I" is - that is contextual, so a bnode. 

I see some suggest <#I> to lock that context, I guess that would
be OK within an email? But then we get different "I"s, 
as <http://orcid.org/0000-0001-9842-9718> is the author of THIS email,
that would be different from Sarven's statement, where "I" could be
<http://csarven.ca/#i> (context *his* email)
or some unknown "I" (context the "sentence")

So "I" is something - we just don't know what, it might not be a Person.
(perhaps just a rdfs:Resource).

Basically my attempt reduces "I am" to just "something exists".
Permitting OWL we can say that as:

  _:I a owl:Thing .

..but that means "I" can't (easily) be a construct of the OWL language :)

The second part of "I am" is that "I" also said that statement. I
guess that why we some of the other people suggesting FOAF/schema
statements that comes down to instead saying "I wrote this".

Nanopublications [1] makes it easier to separate the pointless statement and
the fact the statement is uttered by the same "I". TriG notation:

@prefix this: <http://purl.org/np/RAc8Mzud0BGGchNwT2-eA1usfvh3bgRXYhGasGG9Q1Vx4> .
@prefix sub: <http://purl.org/np/RAc8Mzud0BGGchNwT2-eA1usfvh3bgRXYhGasGG9Q1Vx4#> .
@prefix np: <http://www.nanopub.org/nschema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix pav: <http://purl.org/pav/> .

sub:head {
	this: np:hasAssertion sub:assertion ;
		np:hasProvenance sub:provenance ;
		np:hasPublicationInfo sub:pubInfo ;
		a np:Nanopublication .

sub:assertion {
	sub:I a sub:_1 .

sub:provenance {
	sub:assertion pav:importedFrom <https://lists.w3.org/Archives/Public/semantic-web/2017May/0045.html> ;
		prov:wasAttributedTo sub:I .

sub:pubInfo {
	this: pav:contributedBy <http://csarven.ca/#i> ;
		pav:createdBy <http://orcid.org/0000-0001-9842-9718> ;
		pav:importedFrom <https://lists.w3.org/Archives/Public/semantic-web/2017May/0045.html> ;
		prov:wasAttributedTo <http://orcid.org/0000-0001-9842-9718> .

Here we can distinguish between sub:assertion, the statement itself (which just
says that sub:I is something) and this: - the nanopublication that captures the
statement and its provenance.

We can see in sub:provenance the assertion is attributed to sub:I (so the I
is capable of making such a statement). Also the statement was imported from
Sarven's email message.    

This is captured in the nanopublication this: aka
http://purl.org/np/RAc8Mzud0BGGchNwT2-eA1usfvh3bgRXYhGasGG9Q1Vx4 - which we see
was created by *me*, and also imported from Sarven's message.

Therefore I aka <http://orcid.org/0000-0001-9842-9718> (who created this
*serialization* of the nanopublication) claim Sarven as a contributor (not
necessarily an author, I don't know) of the *knowledge* contained in this

PAV's "importedFrom" here means we have preserved some of the *knowledge* of
that email message, but put it in a different format (in this case an RDF

Note that the NanoPub server had to "lock" the blank nodes to sub:I and sub:_1
to make the Trusted URI [2] -- you can generate that RAc8...Vx4 bit of the URI
using the nanopublication statements.  So this nanopublication, and the "I" in
it, is the same wherever it is published, for instance at

I used [3] and [4] to publish this - thanks to Tobias Kuhn!

[1] http://nanopub.org/guidelines/working_draft/
[2] https://arxiv.org/abs/1401.5775
[3] https://github.com/tkuhn/nanopub-server
[4] https://github.com/Nanopublication/nanopub-java

Stian Soiland-Reyes
The University of Manchester
Received on Friday, 19 May 2017 15:57:46 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 May 2017 15:57:50 UTC