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] Slight proposed revision to XDI visual graph notation

On Tue, Jan 27, 2015 at 11:50 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
I think this works, but you should probably also draw how a relational arc would point to a literal, e.g. when you have an operation like this:


No problem. The literal node is represented by the value, so the arc just goes to the value (in Powerpoint and most other drawing programs, the text box will have its own connection points).

Worst case, we would say you draw an open rounded box around the literal.

Hmm now I wonder can you have one literal pointing to another? E.g.


We've debated that several times. My own intuition is that it is not necessary, i.e., it is the attribute that should be pointing at the attribute, e.g.:


Your diagram needs to be symbol shifted, e.g. +tel -> #tel and +friend -> #friend

Doh! I can't believe I missed that. Done. New version inserted below.


On Wed, Jan 28, 2015 at 7:56 AM, =Drummond Reed <drummond.reed@xdi.org> wrote:
As I'm working on the "How XDI Builds on RDF" paper, I need to include some visual XDI graphs. I'm doing these in Powerpoint because I need the precision.

As I began preparing the examples, it struck me that because we no longer have value nodes, it would be far more intuitive to:
  1. Just use one dedicated geometric shape for each of our major node types:
    1. Circle (open) for root nodes (suggestive of the parentheses used for roots in XDI syntax)
    2. Square (solid) for entity nodes
    3. Diamond (solid) for attribute nodes (suggestive of the angle brackets used for attributes in XDI syntax)
  2. Don't use any geometric shape for a literal node, rather just have the literal arc point to the JSON value exactly as it would appear in JSON, e.g.,
    1. "string" for a JSON string (including "" for the empty string)
    2. 123 for a JSON number
    3. true
    4. false
    5. null
    6. [1,2,3] for a JSON array
    7. { "key": "value" } for a JSON object
Inline image 2

Inline image 1

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