OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xdi] Proposed revisions to XDI graph notation

+1 to omitting a shape for the literal node. This makes it very clear that the literal itself doesn't have an address in the graph (only its value context does).

One thing I will say about the new shapes is that there is now a lot of redundant information in your graph (syntax AND shapes).

Somehow I feel this is not a good idea, I know you wanted to avoid complexity, but this still looks quite overloaded to me.
From the syntax alone I can already tell what kind of context node I'm dealing with, I don't need the shapes for that.
Also, with the new shapes it is now less obvious that they are all contexts. It makes them look like they're something fundamentally different.

Are we now saying "collections and members" instead of "classes and instances"?
This I think is a good idea, even though it seems semantically less precise.


On Wed, Sep 11, 2013 at 8:57 AM, Drummond Reed <drummond.reed@xdi.org> wrote:

As I get down into the details of editing XDI Core Working Draft 01, the time has come to propose some long-discussed updates to our XDI graph notation.

I have been noodling on this ever since our syntax simplification work last spring. At first I was trying to come up with new shapes for all the different node types (root, entity singleton, entity collection, entity member, attribute singleton, attribute collection, attribute member, value). It was always too complex.

Then I hit on the idea of keeping the symbols to a very small set, and using a single character inside the symbol to indicate the multiplicity. That seemed to work much better, and to quickly teach the concept of multiplicity without a lot of explanation.

In terms of the symbols, it seemed obvious to keep using the open circle for root nodes and the closed circle for entities. Due to our choice of syntax, it also seemed intuitive to use the closed diamond for attribute nodes and the open diamond for value nodes -- essentially the mirror of root/entity nodes.

After playing with it, I also realized that because we now have value nodes, explicitly showing another shape for a literal node seems redundant and overly complex. Much simpler to just show the literal arc going to the value itself (since now there is ALWAYS a value if there is a literal arc, even if the value is null).

The result is below -- both a summary of the graph notation and a simple example graph.

Please do post your comments/suggestions.


Inline image 3

Inline image 4

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]