perfsonar development work

[Loukik Kudarimoti <>]

Martin, you assured us that there weren't any schema changes for us to 
worry about. But the changes below clearly alters the schema that we 
have agreed with the JRA4 guys to use for lightpath status monitoring. 
So, if we continue working with the latest code, our SQL MA won't be 
able to talk to JRA4 analysis tools right?

These improvements are for the good. I agree with them. For me, the only 
question is how we bring out these changes (we haven't discussed it 
openly) and at what time (we are close to a software release).

Also, is it not possible to use the nmwg base versioning and produce a 
different version so that we can continue using the old one for the 
purpose of JRA4?

Loukik.



Jason Zurawski wrote:
> All;
>
> As suggested on topology calls about a month ago I implemented a 
> change that placed all 'location' oriented elements inside of a 
> location element, consider these examples:
>
> old way:
>    <nmtopo3:node xmlns:nmtopo3=http://ggf.org/ns/nmwg/topology/base/3.0/
>                              id="node1">
>          <nmtopo3:city>Newark</nmtopo3:city>
>          <nmtopo3:country>USA</nmtopo3:country>
>          <nmtopo3:institution>University of 
> Delaware</nmtopo3:institution>        </nmtopo3:node>
>
> new way:
>    <nmtopo3:node xmlns:nmtopo3=http://ggf.org/ns/nmwg/topology/base/3.0/
>                              id="node1">
>          <nmtopo3:location>
>                <nmtopo3:city>Newark</nmtopo3:city>
>                <nmtopo3:country>USA</nmtopo3:country>
>                <nmtopo3:institution>University of 
> Delaware</nmtopo3:institution>                   <!-- plus new things 
> as well (zipcode, state,
>                         streetAddress, floor, room, cage, rack,
>                         shelf, etc.)
>                -->
>          </nmtopo3:location>           </nmtopo3:node>





> I reinserted the functions that are causing errors w/ Roman's code 
> (related to the city, country, and institution elements), so now these 
> elements can remain as direct children of the node.   Sorry for any 
> confusion or errors that were caused because of this change. 
> -jason