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] XDI graph model node type diagram


I think I would do the following:

1. Rename Graph to Root (or Start)

2. Put Variable one level up as you suggested.

I agree a variable can stand for pretty much anything. I'd like to spend some time on working out the syntax for constraining variables.

Markus

On Monday, November 25, 2013, Drummond Reed <drummond.reed@xdi.org> wrote:
> On Sun, Nov 24, 2013 at 11:12 AM, Markus Sabadello <markus.sabadello@xdi.org> 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 <drummond.reed@xdi.org> 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 
>>>
>>> </mail/u/0/s/?view=att&th=1428f9d75eb5d5db&attid=0.1&disp=emb&realattid=ii_1428aa72603a1ba6&zw&atsh=1>
>>>
>>>
>>
>
>

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