[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xdi] Posted page with XDI metagraph predicate examples
Markus, very good point about that particular choice of phrase. How about if we change it to the following two statements: 1) "Every node in the XDI RDF graph can be addressed by at least one XRI representing an XDI address, and every XDI address identifies a unique node in the XDI RDF graph." 2) "Every XDI RDF statement whose object is not a literal can be expressed as an XRI, and every XDI address that includes a subject, predicate, and object represents at least one XDI RDF statement." =Drummond > -----Original Message----- > From: markus.sabadello@gmail.com [mailto:markus.sabadello@gmail.com] On > Behalf Of Markus Sabadello > Sent: Thursday, January 08, 2009 2:40 AM > To: Drummond Reed > Cc: OASIS - XDI TC; XRI TC > Subject: [xdi] Re: [xri] Posted page with XDI metagraph predicate examples > > I think this brings us back to the question "literals part of the > address?" > > In "Design Principles" you write: > "Every XDI RDF statement can be expressed as an XRI representing an > XDI address". > > So if I have the XDI RDF statement > > =markus > +name > "Markus" > > Then what's the "XRI representing an XDI address" of that statement? > > The way I usually think of it is that an XDI address identifies a node > in the graph (not a statement in the graph). And if you do a $get on > that XDI address, you get all statements rooted on the node identified > by the XDI address. But I'm not sure if that's quite the right way to > look at it. > > Markus > > On Thu, Jan 8, 2009 at 1:05 AM, Drummond Reed > <drummond.reed@cordance.net> wrote: > > Per my action item from both the XRI and XDI TCs, I have posted a page > with > > a substantial portion of the proposed content for the first XDI 1.0 > spec, > > the XDI RDF Graph Model. > > > > > > > > http://wiki.oasis-open.org/xdi/XdiOne/RdfGraphModel > > > > > > > > Besides preparing this content for the first Working Draft (to be > assembled > > after our editor's telecon next week with Mary McRae), the main goal was > to > > document the XDI metagraph predicates and XDI addressing rules to help > XRI > > TC members who wanted to better understand the XDI requirements for XRI > 3.0 > > syntax. > > > > > > > > I spent 2.5 hours going over this last night with Nick Nicholas, whose > > analysis and insights into the model have been very helpful in > clarifying > > and illustrating some of the key concepts. > > > > > > > > For the XDI TC's part, reviewing this page will be the main topic of our > > telecon tomorrow. > > > > > > > > For the XRI TC's part, the next step is to use this input to complete > > analysis of the two main XRI 3.0 syntax proposals: > > > > > > > > http://wiki.oasis-open.org/xri/XriThree/GcsDelimiter > > > > http://wiki.oasis-open.org/xri/XriThree/XrefDelimiter > > > > > > > > We'll discuss setting up a special telecon for this on the XRI TC > telecon > > tomorrow. > > > > > > > > Agendas for tomorrow's telecons coming out next. > > > > > > > > =Drummond > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]