perfsonar development work

[maxim <>]

Hi Yee,
I am still working on your schema. One thing is clear - it should be
independed to current ping.rnc
since extending it will create more mess. Another this is that even without
dependence the schema is not valid
due some inherited problems from underlying schemas. They all written in
Relax NG which makes them more expressive
but less valid when translated into the XML schema world. For example ( and
this is a question to the person
who designed it, its nmtopo-l4.rnc file ) this fragment is not valid (
elements with the same name must be of the same type):

 L4EndpointPairContent =
        (
                element nmtl4:endPoint {
                        attribute port { xsd:string }? &
                        attribute protocol { xsd:string }? &
                        (
                                attribute role { "src" } |
                                element nmwgtopo3:role { "src" }
                        )? &
                        (
                                element nmtl4:address { L4Address } |
                                element nmtl3:interface { anyThing }
                        )?                
                },
                element nmtl4:endPoint {
                        attribute port { xsd:string }? &
                        attribute protocol { xsd:string }? &
                        (
                                attribute role { "dst" } |
                                element nmwgtopo3:role { "dst" }
                        )? &
                        (
                                element nmtl4:address { L4Address } |
                                element nmtl3:interface { anyThing }
                        )                
                } 
        )

Can someone let me know how to deal with that ?
Also in the nmbase.rnc this will violate UPA principal :
commonTime = 
        element nmwg:commonTime {
                (
                        Type &
                        (
                                TimeStamp |
                                (
                                        StartTime & 
                                        (
                                                EndTime | 
                                                Duration 
                                        )
                                )
                        ) &
                        Datum*
                ),
                anyElement*
        }
--------------------------------------------
because it translates into:
--------------------------------------------
<xs:group name="commonTime">
    <xs:sequence>
      <xs:element name="commonTime">
        <xs:complexType>
          <xs:sequence>
            <xs:choice minOccurs="0" maxOccurs="unbounded">
              <xs:choice>
                <xs:group ref="nmtm:TimeStamp"/>
                <xs:choice>
                  <xs:element ref="nmtm:start"/>
                  <xs:element ref="nmtm:end"/>
                </xs:choice>
              </xs:choice>
              <xs:element ref="nmwg:datum"/>
            </xs:choice>
            <xs:group minOccurs="0" maxOccurs="unbounded"
ref="nmwg:anyElement"/>
          </xs:sequence>
          <xs:attributeGroup ref="nmwg:Type"/>
          <xs:attributeGroup ref="nmtm:TimeStamp"/>
          <xs:attribute name="duration" type="xs:string"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:group>
-------------------------
Thanks,
          Maxim.

> -----Original Message-----
> From: Yee-Ting Li 
> [mailto:]
>  
> Sent: Friday, May 25, 2007 6:18 PM
> To: 
> ;
>  
> 
> Cc: maxim; Les Cottrell; Warren Matthews
> Subject: [I2-perfSONAR] PingER services and schemas
> 
> Hi,
> 
> we're in the process of defining a schema for our PingER 
> suite which we plan to use for digital divide measurements 
> and lhc-opn performance measurements. the PingER suite is 
> basically a statistical subset of ping measurements.
> 
> We would like the ability to be able to query for statistical 
> information as part of the xml document; ie using the 'select'  
> namespace. unfortunately, the example schemas in the 
> perfsonar svn do not answer my questions wholly.
> 
> so from the examples, we can define a metadata block with:
> 
>      <select:parameters id="#select1">
>        <nmwg:parameter name="timeValue">
>          <nmwg:parameter name="lessThan">1107492207</nmwg:parameter>
>        </nmwg:parameter>
>      </select:parameters>
> 
>   so, i would be interested in something like:
> 
>      <select:parameters id="#select2">
>        <nmwg:parameter name="minRtt">
>          <nmwg:parameter name="lessThan">5.0</nmwg:parameter>
>        </nmwg:parameter>
>      </select:parameters>
> 
> Assuming that we have a schema in place for the pinger info such that:
> 
> PingERDatum =
>            element pinger:datum {
>                    attribute name { "minRtt" | "maxRtt" | 
> "meanRtt" | "medianRtt" |
>                                     "lossPercent" |
>                                     "minIpd" | "maxIpd" | 
> "ipdv" | "duplicatePercent" } &
>                    attribute value { xsd:float } &
>                    attribute valueUnits { xsd:string }? &
>                    (
>                            (
>                                    attribute timeType { xsd:string } &
>                                    attribute timeValue { xsd:string }
>                            ) |
>                            Time
>                    )?
>            }
> 
> how does one map the selected parameter 'name' (minRtt) to 
> that of the datum where
> 
>    <nmwg:data>
>      <pinger:datum name="minRtt" value="4.9" valueUnits="msec"/>
>    </nmwg:data>
> 
> ie how does one know that the minRtt in the select statement 
> refers to the above element? where is the namespace mapping? 
> how can i qualify the select with the  attribute 'valueUnits's value?
> 
> 
> Thanks,
> 
> Yee.
>