perfsonar development work

[Sven Ubik <>]

Hi Jason,

the schema file is in perfSONAR-CMP.tgz package in client/schema directory 
and it is also attached to this message. Some example requests and 
responses are also in client/schema/example-instances directory.

Regards,

Sven

On Mon, 26 Mar 2007, Jason Zurawski wrote:

> Sven;
>
>
> Is there a schema file or instance files anywhere in svn for this?  If there 
> isn't, we would like to work with you to make one, the procedure for this is 
> written up here:
>
> https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/README.txt
# ##############################################################
# 
# File:         command.rnc - Specialized schema for the command 
#                          tool
# Version:      $Id: command.rnc,v 1.1 2007/03/25 11:50:16 ubik Exp $
# Purpose:      Describes specific elements to be used in the
#               representation and handling of command
#               measurements.
# Reference:    http://books.xmlschemata.org/relaxng/page2.html
#                       
# ##############################################################


# ##############################################################
# Namespace definitions
# ##############################################################
namespace nmwg = "http://ggf.org/ns/nmwg/base/2.0/";
namespace command = "http://ggf.org/ns/nmwg/tools/command/2.0/";


# ##############################################################
# Include additional functionality from other files
# ##############################################################
include "nmtopo.rnc"
include "nmbase.rnc" {
        Metadata |= CommandMetadata
} 



# ##############################################################
# Metadata is the 'data' that describes physical measurements. 
# Metadata can be something such as a physical address, or 
# a geographical location; any form of static, re-usable 
# designation.  It is important to note that the subject
# namespace and parameters namespace MUST match (or the parameters
# can be a generic NMWG) or bad things will occur.
#
# Example: 
# 
# <nmwg:metadata id="REQUIRED_ID" 
#                metadataIdRef="OPTIONAL_REFERENCE_ID"
#                xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
# 
#   <!-- TBD OPTIONAL SUBJECT -->
# 
#   <!-- TBD OPTIONAL PARAMETERS -->
#
#   <!-- TBD OPTIONAL EVENTTYPE -->
# 
#   <!-- TBD OPTIONAL KEY -->
#  
#   <!-- ANY OPTIONAL (MULTIPLE) ELEMENT IN ANY NAMESPACE --> 
#
# </nmwg:metadata>
# 
# ##############################################################
        
CommandMetadata = 
        element nmwg:metadata {
                Identifier &
                MetadataIdentifierRef? &
                CommandMetadataContent
        }
        
CommandMetadataBlock = 
        CommandSubject? &
        (
                Parameters
        )?      
        
CommandMetadataContent = 
        (
                CommandMetadataBlock |
                FilterMetadataBlock             
        ) &     
        EventType? &
        Key?    


# ##############################################################
# Redefined command subject allows only an endPointPair or
# interface, and the two id attributes.    
#
# Example: 
# 
# <command:subject id="REQUIRED_ID" 
#               metadataIdRef="OPTIONAL_REFERENCE_ID"
#               xmlns:nmwg="http://ggf.org/ns/nmwg/tools/command/2.0/";>
# 
#   <nmwgtopo:endPointPair 
xmlns:nmwgtopo="http://ggf.org/ns/nmwg/topology/2.0/";>
# 
#     <nmwgtopo:src type="REQUIRED_TYPE" value="REQUIRED_VALUE" 
#                   port="OPTIONAL_PORT"/>
# 
#     <nmwgtopo:dst type="REQUIRED_TYPE" value="REQUIRED_VALUE" 
#                   port="OPTIONAL_PORT"/>
#  
#   </nmwgtopo:endPointPair>
#  
# </command:subject>
#
# Example 2: 
#
# <command:subject id="REQUIRED_ID" 
#               metadataIdRef="OPTIONAL_REFERENCE_ID"
#               xmlns:nmwg="http://ggf.org/ns/nmwg/tools/command/2.0/";>
#
#   <nmwgtopo:interface xmlns:nmwgtopo="http://ggf.org/ns/nmwg/topology/2.0/";>
#
#     <nmwgtopo:ipAddress type='REQUIRED_TYPE'> TEXT </nmwgtopo:ipAddress>
#
#     <nmwgtopo:hostName> TEXT </nmwgtopo:hostName>
#
#     <nmwgtopo:ifName> TEXT </nmwgtopo:ifName>
#
#     <nmwgtopo:ifDescription> TEXT </nmwgtopo:ifDescription>
#
#     <nmwgtopo:ifAddress type='REQUIRED_TYPE'> TEXT </nmwgtopo:ifAddress>
#
#     <nmwgtopo:ifHostName> TEXT </nmwgtopo:ifHostName>
#
#     <nmwgtopo:ifIndex> TEXT </nmwgtopo:ifIndex>
#
#     <nmwgtopo:type> TEXT </nmwgtopo:type>
#
#     <nmwgtopo:direction> TEXT </nmwgtopo:direction>
#
#     <nmwgtopo:authRealm> TEXT </nmwgtopo:authRealm>
#
#     <nmwgtopo:classOfService> TEXT </nmwgtopo:classOfService>
#
#     <nmwgtopo:capacity> TEXT </nmwgtopo:capacity>
#
#   </nmwgtopo:interface>
#  
# </command:subject>
#
# ##############################################################

CommandSubject =
        element command:subject {
                Identifier &
                MetadataIdentifierRef? &                        
                (
                        EndpointPair |
                        Interface
                )
        }