On Sun, Nov 24, 2013 at 11:12 AM, Markus Sabadello <> wrote:
Can you give an example where a variable includes an entire graph?
I was thinking about that when I drew the diagram. Here's one:
(=drummond){()}<$uri>
That's an example of a query that uses a typed variable {()} to indicate that nodes satisfying the variable must be a graph—in this case a peer graph of (=drummond).
Maybe it would be more appropriate to say it is a placeholder for (part of) a subject, predicate or object in a statement?
I agree a variable can be all of that. But what does that mean about where Variable should appear in the taxonomy? Should it be where I have it now, or should it move up a level and be on the line with Graph and Subgraph?
=Drummond
On Sun, Nov 24, 2013 at 4:18 PM, Drummond Reed <> wrote:
Another project on my trip was to draw the diagram illustrating the taxonomy of node types in the XDI graph model that I plan to include in the XDI Core 1.0 spec. The outcome is below. Notes:
This reflects all the same types as on https://wiki.oasis-open.org/xdi/GraphModelStructure except the classification is slightly different.
The only interesting new placement is Variable. Before I had just classified it as a different type of context. But a variable syntax (curly brackets) has more in common with graph syntax (parentheses) than anything else. And a variable can include an entire graph. So it seems to make sense to include it in the graph tree.
Thoughts before I move forward with publishing this?
=Drummond
