perfsonar development work

[Jason Zurawski <>]

Roman;
> 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:
<snip>

I believe this has been brought up before in previous conversations, I 
don't see a problem with allowing multiple parameters blocks, as long as 
they have a different namespace designation (in your example 
nmwg/select/transform is ok).  But this is not even a hard requirement, 
we could just 'merge' blocks with a similar namespace (although it will 
be important to document the behavior). 

> 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.
<snip>

This way does not seem as natural to me, and it forces a specific 
parameter element when we have tried to keep this very general.  It may 
also complicate searching via the standard search mechanisms:

/nmwg:key/select:parameters/nmwg:parameter[@name="startTime"]
vs
/nmwg:key/nmwg:parameters/nmwg:parameter[@name="http://ggf.org/ns/nmwg/ops/select/2.0/"]/collection:item[@name="startTime"]

This is not the most compelling of reasons, but the mapping is not as 
direct as in the former scheme.

-jason