perfsonar development work

[Fausto Vetter <>]

Hi,

Would it be possible to define this "inteligence" of defining which 
eventType maps to parameters using schemas based on message & eventTypes?

Fausto

Jeff W. Boote wrote:

> Fausto Vetter wrote:
>
> > Hi,
> >
> > I wasnt saying to extend. I just wanted some semantics that would say:
> >
> > for eventType pingStore for example, there must be parameters of type 
> > nmwg and ping.
>
>
> To do what you are saying I would just have a single parameterS 
> element in the md using the pingStore namespace. It can have the full 
> set of parameter elements needed to fully describe the semantics.
>
> It is definitely possible to support groupings of parameters. Murilo's 
> example that we discussed last week already showed a parameterS 
> element as the value of a parameter. But, this is still a function of 
> the semantics of the single eventType defining what namespace is 
> expected for the outer parameterS element. (And what semantics are 
> expected.)
>
> In Murilo's example, the inner parameterS will be defined by the 
> semantics of the eventType as well because the code that reads the 
> parameters will be expecting to handle a parameter with a value of 
> this complex type.
>
> I believe all of this is already currently supported. I'm saying I 
> don't see a need to change anything to represent these relationships. 
> (By adding some new kind of mapping in the general nmwg eventType -> 
> parameters mapping.)
>
> jeff