perfsonar development work

[Roman Lapacz <>]

Hi Martin, Jason, Jeff, others,

I've got one more observation related with parameters in our schema. Now 
only one parameters element is allowed to be in the metadata. What do 
you think to allow existence of more than one. This would be useful to 
keep in the same metadata (or other element, for example the key) 
parameters representing more then one namespace.

Example for the key:

 <nmwg:key>
     <nmwg:parameters id="params1">
         <nmwg:parameter 
name="file">/home/romradz/test.rrd</nmwg:parameter>
         <nmwg:parameter name="dataSource">pkts</nmwg:parameter>
         <nmwg:parameter name="valueUnits">Bps</nmwg:parameter>
     </nmwg:parameters>
     <select:parameters id="params2">
         <nmwg:parameter name="startTime">1121472000</nmwg:parameter>
         <nmwg:parameter name="endTime">1121904000</nmwg:parameter>
         <nmwg:parameter 
name="consolidationFunction">AVERAGE</nmwg:parameter>
         <nmwg:parameter name="resolution">60</nmwg:parameter>
     </select:parameters>
     <timetrans:parameters id="params3">
         <nmwg:parameter name="ConvertTo">unix</nmwg:parameter>
         <nmwg:parameter name="ConvertFrom">iso</nmwg:parameter>
     </timetrans:parameters>
 </nmwg:key>


This is just en example and there might be other situations when using 
parameters of different namespaces could be needed.

It's possible to overcome this problem without using above solution if I 
had enhanced parameter elements. I put example below but I think it's 
just a trick and the above is more suitable.


 <nmwg:key>
     <nmwg:parameters>
         <map:parameter name="http://ggf.org/ns/nmwg/base/2.0/";>
             <collection:item 
name="file">/home/romradz/test.rrd</collection:item name>
             <collection:item name 
name="dataSource">pkts</collection:item name>
             <collection:item name 
name="valueUnits">Bps</collection:item name>
         <map:parameter>
         <map:parameter name="http://ggf.org/ns/nmwg/ops/select/2.0/";>
             <collection:item name="startTime">1121472000</collection:item>
             <collection:item name="endTime">1121904000</collection:item>
             <collection:item 
name="consolidationFunction">AVERAGE</collection:item>
             <collection:item name="resolution">60</collection:item>
         </map:parameter>
         <map:parameter 
name="http://schema.perfonar.net/tools/transform/utilization/unixtime/2.0/";>
             <collection:item name="ConvertTo">unix</collection:item>
             <collection:item name="ConvertFrom">iso</collection:item>
         </map:parameter>
     <nmwg:parameters>
 </nmwg:key>

(I'm still using map and collection namespaces because I haven't seen 
the minutes from related discussion in Brasil yet so treat them here as 
temporary. I just wanted to show the idea of workaround).


What do you think?

Roman