perfsonar development work

[Loukik Kudarimoti <>]

Jeff W. Boote wrote:
> <snip>
> The general definition of valid namespaces is defined by the OGF 
> standard found at:
>     http://www.ogf.org/documents/GFD.84.pdf
>
> It looks like I was not complete enough on the wiki. (I should have 
> prefixed the namespace rules with 'http://'.)
>
> Basically, ORG should be a domain name. So, for perfsonar services I 
> believe we should in general use something like:
>
>     schemas.perfsonar.net
>
> We also have some latitude to define the hierarchy under 
> schemas.perfsonar.net in a way that makes sense for us. For example, 
> we can add a sub-dir to that 'org' if we want. So, for administrative 
> support eventTypes like 'echo' perhaps we should come up with our own 
> hierarchy under perfSONAR. How about:
>
> http://schemas.perfsonar.net/tools/admin/echo/ls/2.0
>
> http://schemas.perfsonar.net/tools/admin/echo/2.0 can be a generic 
> version that any service can use, and can be extended by ones at lower 
> levels.
Just to make sure that everyone's on the right page on this, from 
Roman's email, I understand that the implementation is
http://www.perfsonar.net/tools/admin/echo/2.0  (no schemas in the 
perfsonar url)

While I am OK to have it the way it has been implemented currently, I do 
feel that having the schemas in the dns name (like what was proposed by 
Jeff) makes it much clearer that its a schema namespace and also ensures 
our conformance with the OGF specification. (we are the the start of 
doing this implementation, so lets do it thorough)

Loukik.
> jeff