perfsonar development work

[Jason Zurawski <>]

Roman;


> > > ... or if you want we could update datum element of 'nmwg' namespace
> > >
> > > for example:
> > >
> > >    <nmwg:datum value="234567890" valueUnits="octets">
> > >      <nmtm:time type="unix" value="1021119880"/>
> > >    </nmwg:datum>
> > >
> > >
> > > but it should be the same for metrics the we use and store in rrd 
> > > files.
> > The nmwg datum (and most [all?] other tool and characteristic 
> > specific datums should support this already.
> What I had in mind was that we could say what exactly client app could 
> expect to get from MA service in case of utilizationa/errors/discards 
> case.


The client applications should be robust enough to expect any 
representation, that is the goal of defining the standards.  We can do a 
'best practices' specification, but I see no harm in allow the many 
different ways of reporting the datum (via different namespaces) or the 
enclosed time (both the time format, and the element representation).


-jason