perfsonar development work

["Jeff W. Boote" <>]

While working with Guilherme on how to extend the CLMP to output multiple 
formats of owamp data - I realized that we have not been setting the eventType 
names like we should.

We discussed this back in Ann Arbor (and I think even before in Cambridge), but 
eventType names need to follow the same naming conventions as the schema itself. 
In other words, the eventType name should match the namespace of the 
subject/parameters in the metadata.

Currently eventTypes are far too generic, and don't adhere to any naming scheme. 
This will be a problem as we get more and more of them. (We will have clashes of 
eventType names and the meaning will not be clear.)

I bring this up more for new event types that are being created. It will take 
some time to figure out how to migrate the current ones since they are 
referenced throughout the code.

Therefore, eventTypes should really look like they do in the following example 
(Martin, Jason - please correct me if I'm wrong.):

<nmwg:message id="msg1" type="MetadataKeyRequest"
        xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
        xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
        xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";>

    <nmwg:metadata id='m1'>

        <nmwg:eventType>
            http://ggf.org/ns/nmwg/characteristic/utilization/2.0/
        </nmwg:eventType>

        <netutil:subject id="subj1">
            <nmwgt:interface>
                <nmwgt:ifAddress type="ipv4">198.32.8.34</nmwgt:ifAddress>
                
<nmwgt:hostName>atlang-hstnng.abilene.ucaid.edu</nmwgt:hostName>
            </nmwgt:interface>
        </netutil:subject>

    </nmwg:metadata>

</nmwg:message>

jeff