perfsonar development work

[Jason Zurawski <>]

Maciej;

> In the summarizaton example you used a list of event types with the 
> same name. In the current implementation of NMWG all parameter must 
> have unique names. To be honest I followed the same direction in 
> ps-base2...
>
> =======================================================================
> <summary:parameters id="summmary.md.1">
>     <nmwg:parameter
>        name="eventType"
>        value="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"; />
>     <nmwg:parameter
>        name="eventType"
>        value="http://ggf.org/ns/nmwg/characteristic/discards/2.0/"; />
>     <nmwg:parameter
>        name="eventType"
>        value="http://ggf.org/ns/nmwg/characteristic/errors/2.0/"; />
>     <nmwg:parameter
>        name="eventType"
>        value="http://ggf.org/ns/nmwg/tools/snmp/2.0/"; />
> </summary:parameters>
> =======================================================================
>
> Is it intentional or can be done in different way?

This was intentional and I was under the impression that this was fixed 
some time ago for the 'supportedEventType' parameter. 

It is necessary to support these multiple parameters since a single LS 
will no doubt be submitting many eventTypes in each summary (same thing 
will apply for multiple elements of the same name such as the network 
element).  I would much rather take this approach that trying something 
rather arbitrary such as:

<parameters>
 <parameter name="eventType1">first one</parameter>
 <parameter name="eventType2">second one</parameter>
</parameters>

If you have an elegant solution please suggest, but I currently don't 
see another way.

-jason