Next in thread →
Next in month →
Re: [xdi] XDI TC Notes Unofficial Telecon Monday 2016-08-22
Yes you are right of course.
On 08/22/2016 10:08 PM, =Drummond Reed wrote:
Markus, thanks for sending this. It was indeed
lightly attended today (I feared that would be the case given
August vacation conflicts), but it was still a good discussion.
One correction: your notes on the RDF graph topic said, "...
then the XDI graph model could be implemented “on top” of the
XDI graph model".
I think you meant, ".."on top" of the RDF graph model", yes?
On Mon, Aug 22, 2016 at 1:05 PM, Markus
Sabadello <>
wrote:
XDI
TC Notes
Following
are the notes of the unofficial telecon of the XDI TC
held on:
Date:
Monday, 22 August 2016 USA
Time:
10:00AM - 11:30AM Pacific Time (17:00-18:30 UTC)
The
TC operates under a
standing rule approved 17 July 2008
under which the TC does not hold regular official
meetings and conducts all business by electronic
ballot only. Unofficial weekly meetings are held to
enable discussion among members but no business is
conducted nor actions taken.
ATTENDING
Drummond
Reed
Markus
Sabadello
REGRETS
NOTES
Github
Repository Support
We
did not discuss this topic due to limited call
attendance.
XDI
Android App
Markus
reported that he continues to make progress on the XDI
Android app he has been working on, which demonstrates
the functionality of XDI link contracts, data sharing,
and messaging. Markus is currently focusing on
improving the app’s user interface.
DIDs
(Decentralized Identifiers), DID Objects, and their
Relevance to XDI
We
did not discuss this topic due to limited call
attendance.
RDF
/ XDI Compatibility
Markus
explored an idea about how to adapt the XDI graph
model to RDF in cases where the constraint is to start
with the RDF graph model. Markus pointed out that we
have always assumed that the mapping of an XDI graph
to an RDF graph is:
XDI
literals are RDF literals
XDI
relations are RDF properties
XDI
contexts are RDF resources with a specific
relationship.
Markus
had the idea that if the constraint is that an
implementation must use the RDF graph model, then the
XDI graph model could be implemented “on top” of the
XDI graph model.
For
example, =markus would be a resource and
<#email> would be a resource and then the
literal would be the email value.
Markus
suggested that you can define a profile of RDF that
consisted of several key mappings:
A
constraint that an RDF graph could have only one
predicate for a literal (to maintain the unique
addressability).
A
single URI representing context.
A
single URI representing unique instances (to
replace blank nodes).
The
end result of this thought process could be a graph
model that is 100% compatible with RDF but still makes
it possible to use XDI identifiers and XDI syntax.
NEXT
REGULAR CALL
The
next call will be the following week at the usual time
(Monday 10AM PT). The link to where agenda items can
be posted for the next meeting is:
https://docs.google.com/document/d/19oDl0lbb56Grehx2a5flZnhrgnua5l8cVvC_dJ8fTXk/edit?usp=sharing
Next in thread →
Next in month →