perfsonar development work

[Jason Zurawski <>]

Hey Roman;

> How could we indicate that the first filtering parameters 
> (meta2select) use unix time type and the second one (meta4select) use 
> ISO 8601. Now we have high level parameter timeType (see attachment)
>
>  <nmwg:parameters id="msgparam1">
>    <nmwg:parameter name="timeType">unix</nmwg:parameter>
>  </nmwg:parameters>


I see from the example that this is at the message level, which works 
but in my opinion is not ideal. 


> We might add new parameter into filtering parameters' metadata, example:
>
>  <nmwg:metadata id="meta2select">
>    <select:subject id="iusub2" metadataIdRef="meta1"/>
>    <select:parameters id="param1">
>      <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>
>      <nmwg:parameter name="timeType">unix</nmwg:parameter>
>    </select:parameters>
>    <nmwg:eventType>http://ggf.org/ns/nmwg/ops/select/2.0</nmwg:eventType>
>  </nmwg:metadata>
>
>
> what do you think? Maybe there is more general approach?

I think this is a good use of a parameter (and because it is specific 
for this particular implementation it shouldn't affect any other 
service).  I am not sure if it should be in the select parameter block, 
along with other RRD specific parameters however.  The time type is an 
external modification to the data presentation, the CF, resolution and 
start/end times are sent to the RRD libraries.  It could be in a 
seperate parameter block:

<nmwg:parameters>
 <nmwg:parameter name="timeType">unix</nmwg:parameter>
</nmwg:parameters>
<select:parameters>
 <select:parameter ... />
</select:parameters>



-jason

--

Jason Zurawski, Software Engineer
Internet2

office: +1-302-230-1197

Make high-performance connections in person:
The Spring 2007 Internet2 Member Meeting
http://events.internet2.edu/2007/spring-mm/