perfsonar development work

[ulisses <>]

Hi Jason

I'm very sorry for not attending to the conf call. I hope 
we meet personaly in short time so I can personaly apologize for my fault.

On 2006-09-05 09:51:03, Jason Zurawski wrote:
> Ulisses;
[...]

please take a note at the text enclosed between <here> and </here>

> >A full example could be:
> >
> >  <nmwg:metadata id="meta1">
> >    <netutil:subject id="sub1">

<here>

> >     <nmwgtopo3:link>
> >           <nmwgtopo3:interface>
> >                   <nmwgtopo3:capacity>155000000</nmwgtopo3:capacity>
> >        </nmwgtopo3:interface>
> >    </nmwgtopo3:link>

</here>

> >    </netutil:subject>
> >  </nmwg:metadata>
> >  
> 
> The namespace of subject is wrong here (it should be just nmwg, or 
> something else generic), but the idea is correct. 

ok

> >  <nmwg:metadata id="meta2">
> >    <select:subject id="sub2" metadataIdRef="meta1"/>
> >
> >    <select:parameters id="param1">
> >      <nmwg:parameter name="Time">0</nmwg:parameter>
> >    </select:parameters>
> >
> >    <nmwg:eventType>select</nmwg:eventType>
> >
> >  </nmwg:metadata>
> >
> >
> >  
> 
> I am not sure what you mean by:
> 
> <nmwg:parameter name="Time">0</nmwg:parameter>
> 
> in this example.  You are trying to get all link elements, with that 
> capacity, that start after time 0?

it is my way of specifying "now", I could be a the "now" string if you prefer.

> Your example is more or less correct, and we did intend for the 
> parameters to be used in this fashion when interacting with databases 
> and other backend storage.  It will be necessary (as you are designing 
> your service) to define what possible 'fields' can be selected upon 

because the fields are for not very fixed (many are missing) and the storage 
schema is going to change. The way I have thought to solve it is to
allow between the <here>/</here> marks any partial definition of the child 
of root of the document of a full database download: that will allow to select
all elements that can match the elements partially defined.

A conceptual example follows. Currently a full database download is more or 
less:

root --- Nodes: Node 1, Node 2, etc...
     --- Links: Link 1, Link 2, etc...

of course Nodes and Links have childs.

in the case of requesting a Node, the parameter would be a partial node 
definition. That
would mean "select all nodes that match this partial definition of a node".

is this right for you?

Thanks

        Ulisses

> (for 
> example the rrd ma can specify a startTime, endTime, 
> consolidationFunction, or resolution; these have some sort of meaning to 
> the backend and need to be well described in the instance documents). 


> 
> 
> -jason
>