using a sparql URI as a webid

FROM <http://rdf-translator.appspot.com/parse?url=https%3A%2F%2Frapstr1.blob.core.windows.net%2Fods%2Fuser.ttl&if=n3&of=xml>
FROM <http://rapstr1.blob.core.windows.net/ods/user.ttl>
FROM <https://id.myopenlink.net/dataspace/person/home_pw>
FROM <http://yorkporc2.blogspot.com>

 

 

As a practical matter, RDFa seems unhappy to host a data URI (i.e. cert blob).  But turtle seems happier. Thus we see that rapstr1 can be the same as the cert blog. but the same is NOT true for yorkporc2. But, yorkporc2 is the sameAs rapstr1. So, presumably one can infer now that yorkporc2 is the sameAs  the cert.

First we see the extant statements of equivalency:

Our goal is to prove that yorkporc2 is currently refers to the same thing as does cert (which is to itself, since it’s a data URI). Then, a secondary goal is to add a relation to the myopenlink profile so my webfinger ready account URI is also the same reference and thus same thing as the cert (since a cert is a data URI).

When we take the advice of experts, and simply describe yorkporc2

The material part of the response shows both problems are already addressed. And, furthermore, yorkporc2 can be described by either of the two certs stored in the ODS profile.

We can rerun the query in /isparql, with its integrated viewers for the result-set.

DEFINE input:same-as “yes”
#DEFINE sql:describe-mode “SPO”
PREFIX owl: <http://www.w3.org/2002/07/owl#&gt;
PREFIX : <http://www.w3.org/ns/auth/cert#&gt;
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#&gt;

DESCRIBE <http://yorkporc2.blogspot.com/#me&gt;
FROM <http://rdf-translator.appspot.com/parse?url=https%3A%2F%2Frapstr1.blob.core.windows.net%2Fods%2Fuser.ttl&if=n3&of=xml&gt;
FROM <http://rapstr1.blob.core.windows.net/ods/user.ttl&gt;
FROM <https://id.myopenlink.net/dataspace/person/home_pw&gt;
FROM <http://yorkporc2.blogspot.com/&gt;
WHERE {

     ?s cert:key ?o
} 

The result is, in a linked data web viewer:

 

 

Tis view happens to describe how the resulting entry (with its inferences) is referenced – which includes the sparql query that generated it (all nicely url-encoded).

Lets steal that URI , and put it into our cert’s SAN URI.

 

The query can be viewed here and then executed.