perfsonar development work

Author: zurawski
Date: 2007-05-02 14:16:45 -0400 (Wed, 02 May 2007)
New Revision: 225

Modified:
   trunk/nmwg/schema/rnc/nmbase.rnc
   trunk/nmwg/schema/rnc/nmtime.rnc
Log:
Update after Editing pass.

-jason



Modified: trunk/nmwg/schema/rnc/nmbase.rnc
===================================================================
--- trunk/nmwg/schema/rnc/nmbase.rnc    2007-05-02 18:16:15 UTC (rev 224)
+++ trunk/nmwg/schema/rnc/nmbase.rnc    2007-05-02 18:16:45 UTC (rev 225)
@@ -76,12 +76,12 @@
 
 
 # ##############################################################
-# 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.
+# Metadata is the 'data' that describes physical measurements.
+# Metadata can be 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: 
 # 
@@ -128,10 +128,10 @@
 
 # ##############################################################
 # Subject identifies an endPoint (or points), perhaps the name of
-# a service, or some other form of physical location.  For the 
-# purpose of the general case we make no assumptions on potential
-# elements and allow all elements, in any namespace.  Verification
-# can be handled in subsequent schema files.    
+# a service or some other form of physical location. For the
+# purpose of the general case, we make no assumptions on potential
+# elements and allow all elements, in any namespace. Verification
+# can be handled in subsequent schema files.  
 #
 # Example: 
 # 
@@ -159,14 +159,14 @@
         
 
 # ##############################################################
-# Parameters and Parameter elements can be used in a number of 
-# ways: in the message to signify items such as time stamp or
-# authorization, in metadata or data to specify filters or
-# special cases for the information.  A 'parameters' block
-# has an id, and encloses one to many 'parameter' elements. 
+# Parameters and Parameter elements can be used in a number of
+# ways in: 1) the message to signify items such as time stamp
+# or authorization or 2) metadata or data to specify filters or
+# special cases for the information. A 'parameters' block
+# has an id and encloses one to many 'parameter' elements.
 # These elements have a required 'name', and may contain
-# an attribute, element, or text value (only one please, 
-# software using this should consider complex elements, then 
+# an attribute, element, or text value (only one please;
+# software using this should consider complex elements, then
 # text, and finally the value attribute; exceptions should
 # be thrown on duplicates).
 #
@@ -232,8 +232,8 @@
 
    
 # ##############################################################
-# The key is used to return a 'pointer' or otherwise special chunk
-# of identifying information in response to a request.  For now
+# The key is used to return a 'pointer' or otherwise special piece
+# of identifying information in response to a request. For now, 
 # this information is enclosed only within a parameters block.
 # The optional ID can be used to track past searches.
 #
@@ -259,10 +259,10 @@
         
            
 # ##############################################################
-# The data block is complex, and has the potential to contain
-# many things.  The data block can be used to return a metadata
-# block from a request, commonTime or datum elements, keys, 
-# or something that we have perhaps not defined as of yet.  
+# The data block is complex and has the potential to contain
+# many things. The data block can be used to return a metadata
+# block from a request, commonTime or datum elements, keys,
+# or something that we have perhaps not defined as of yet. 
 #
 # Example: 
 # 
@@ -312,11 +312,11 @@
         }
 
 # ##############################################################
-# CommonTime is used a a shortcut able to 'factor out' a frequently
-# occurring time range that a bunch of datum (or other) elements
-# might share, thus reducing complexity of XML representation.  
-# CommonTime is similar to the other NMWG time stamps (from 
-# nmtime.rnc) in its potential time representations.
+# CommonTime is used as a shortcut that is  able to 'factor out' 
+# a frequently occurring time range that a bunch of datum (or 
+# other) elements might share, thus reducing complexity of XML 
+# representation. CommonTime is similar to the other NMWG time 
+# stamps (from nmtime.rnc) in its potential time representations.
 #
 # Example: 
 # 
@@ -359,7 +359,7 @@
 
 
 # ##############################################################
-# The datum is meant to be generic in this case, because specific
+# The datum is meant to be generic in this case because specific
 # namespace declarations should be used to better define what
 # format that datum should have.
 #
@@ -381,8 +381,8 @@
         
          
 # ##############################################################
-# Common elements defined as named patterns, as they are re-used
-# several times.
+# Common elements are defined as named patterns as they are re- 
+# used several times.
 # ##############################################################
                 
 Identifier =
@@ -400,7 +400,7 @@
 
 # ##############################################################
 # This sequence allows any element, attribute, or text (regardless 
-# of name, or namespace) into the document when invoked.
+# of name or namespace) into the document when invoked.
 # ##############################################################
 
 anyElement = 

Modified: trunk/nmwg/schema/rnc/nmtime.rnc
===================================================================
--- trunk/nmwg/schema/rnc/nmtime.rnc    2007-05-02 18:16:15 UTC (rev 224)
+++ trunk/nmwg/schema/rnc/nmtime.rnc    2007-05-02 18:16:45 UTC (rev 225)
@@ -17,11 +17,11 @@
 
 
 # ##############################################################
-# Regular time is attached to a specific datum instance, it is 
-# essentially the the same as before, but cannot have anything 
-# 'inside' of it.  The type can be simple like UNIX, etc. or it 
-# could be something like timeRange, or timeInterval.  If this is 
-# the case we would then see the two extra time designators for 
+# Regular time is attached to a specific datum instance; it is
+# essentially the same as before, but cannot have anything
+# 'inside' of it. The type can be simple, like UNIX, or it
+# could be something like timeRange or timeInterval. If this is
+# the case, we would then see the two extra time designators for
 # the start and end (or duration)
 # 
 # Example: