perfsonar development work

[Roman Lapacz <>]

Murilo Vetter wrote:
> Hi,

Hi Murilo, all

> Another changes to have more flexible parameters. The message is 
> defined this way:
>
> ----------
>
> <nmwg:message type="TopologyRequest"
>    id="msg1"
>    xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
>    xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";>
>
> <nmwg:metadata id="11">
>
>    <nmwgtopo3:subject id="YYY">
>    </nmwgtopo3:subject>
>      
> <nmwg:eventType>http://ggf.org/ns/nmwg/topology/actions/list</nmwg:eventType> 
>
>      <nmwgtopo3:parameters id="YYY">
>        <nmwg:parameter name="include">
>            <nmwg:parameter name="1">node</nmwg:parameter>
>            <nmwg:parameter name="2">link</nmwg:parameter>
>        </nmwg:parameter>
>        <nmwg:parameter name="level">
>            <nmwg:parameter name="1">detail</nmwg:parameter>
>        </nmwg:parameter>
>    </nmwgtopo3:parameters>
>
> </nmwg:metadata>
>
> <nmwg:data id="data0" metadataIdRef="11"/>
>
> </nmwg:message>
>
> -------------
>
> > Is empty subject is really needed? I think eventType is enough in 
> > this request.
>
> About the subject, it is optional. Roman is right.
> Now, I can define in a Kind hash structure. For example, I have 
> parameter names
> include and level. Inside I have another parameters, name with 
> numbers, or whatever
> symbol you want, But this names must be unique. So, you can match each 
> include element
> to the level element associating them with the unique name.
> The level parameter is going to appear just when we have the include 
> node. for the others
> it is not necessary.
>
> I think this is better now.

Hmm, parameter element inside parameter element looks a little bit 
strange in xml document.


I have a proposal to create new namespaces to embrace map, list, and 
maybe other container structures for parameter element


xmlns:list="http://ggf.org/ns/nmwg/base/2.0/parameter/collection/list/";
xmlns:map="http://ggf.org/ns/nmwg/base/2.0/parameter/collection/map/";
xmlns:collection="http://ggf.org/ns/nmwg/base/2.0/parameter/collection/";


      <list:parameter name="listXYZ">
          <collection:item name="X">xxx</collection:item>
          <collection:item name="Y">yyy</collection:item>
      </list:parameter>

      <map:parameter name="mapXYZ">
          <collection:item name="X">xxx</collection:item>
          <collection:item name="Y">yyy</collection:item>
      </map:parameter>



I would insert this topic into 'to discuss' list for Brasil meeting. We 
need the solution and its implementation so it would be good to have the 
final agreement on this after that meeting.


Roman