perfsonar development work

[ulisses <>]

Hi Jason!

On 2006-09-06 09:41:25, Jason Zurawski wrote:
[...]
> In the past some developers have used:
> 
> <nmwg:parameter name="time">now</nmwg:parameter>

then, it will be "now", definitly more explicit


> >>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.
> >
> >  
> 
> 
> Yes, I don't see a problem with this.  I was referring more to defining 
> the parameter portion (how many possible things can appear in the select 
> parameters) more than what the initial subject can be:
> 
>  <nmwg:metadata id="meta2">
>    <select:subject id="sub2" metadataIdRef="meta1"/>
>    <select:parameters id="param1">
>      <nmwg:parameter name="Time">0</nmwg:parameter>
> 
>      <!--   List of other things that can be selected on besides time  -->
> 
>    </select:parameters>
>    <nmwg:eventType>select</nmwg:eventType>
>  </nmwg:metadata>

for now other things might be the domain_id only, it's something work in 
progress

> >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".
> >
> >  
> 
> 
> I am not sure I understand what you mean here, do you mean to include 
> node/link information as parameters in the select?  Could you please 
> make a more descriptive example of what you intend to do?

for example If I want to select all links with interfaces that have a 
capacity of 155Mbps, I will insert:

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

and for not having to handle may cases only data childs of the root element 
are
accepted in the "selection"... afterwards I'm going to post complete/concrete 
examples 

Thanks
        Ulisses