perfsonar development work

[Roman Lapacz <>]

Hi Jason, Martin, all

I have something that I'd like to discuss on. I attached example request 
with two logical sub-requests (two data triggers). Both of them use unix 
time format (seconds passed since the Epoch). I'm going to implement the 
support of ISO 8601 time format as well. 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>

but it can refer to the whole request, not to the specific sub-request.

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?

Roman
<?xml version='1.0' encoding='UTF-8'?>

<nmwg:message id="msg"
            type="SetupDataRequest"
            xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
            xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
            xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";
            xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";>


  <nmwg:parameters id="msgparam1">
    <nmwg:parameter name="timeType">unix</nmwg:parameter>
  </nmwg:parameters>


  <!-- 1st logical subrequest -->

  <nmwg:metadata id="meta1">
    <netutil:subject id="iusub1">
      <nmwgt:interface>
        <nmwgt:ifAddress type="ipv4">100.1.2.3</nmwgt:ifAddress>
        <nmwgt:direction>in</nmwgt:direction>
      </nmwgt:interface>
    </netutil:subject>
    <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
  </nmwg:metadata>


  <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>
    </select:parameters>
    <nmwg:eventType>http://ggf.org/ns/nmwg/ops/select/2.0</nmwg:eventType>
  </nmwg:metadata>


  <!-- 2nd logical subrequest -->

  <nmwg:metadata id="meta3">
    <netutil:subject id="iusub3">
      <nmwgt:interface>
        <nmwgt:ifAddress type="ipv4">200.1.2.3</nmwgt:ifAddress>
        <nmwgt:direction>out</nmwgt:direction>
      </nmwgt:interface>
    </netutil:subject>
    <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
  </nmwg:metadata>

  <nmwg:metadata id="meta4select">
    <select:subject id="iusub2" metadataIdRef="meta1"/>
    <select:parameters id="param1">
      <nmwg:parameter name="startTime">1121475000</nmwg:parameter>
      <nmwg:parameter name="endTime">1121909000</nmwg:parameter>
      <nmwg:parameter name="consolidationFunction">AVERAGE</nmwg:parameter>
      <nmwg:parameter name="resolution">60</nmwg:parameter>
    </select:parameters>
    <nmwg:eventType>http://ggf.org/ns/nmwg/ops/select/2.0</nmwg:eventType>
  </nmwg:metadata>


  <!-- data triggers -->

  <nmwg:data id="data1" metadataIdRef="meta2select"/>
  <nmwg:data id="data2" metadataIdRef="meta4select"/>


</nmwg:message>