Hi, please. take a look at the RNC schema of nml base that I've attached to this email. Any comments, updates and suggestions are welcome. regards, Roman
Hey Roman, Overall, it looks good. A few questions on the schema. 1. It'd be good if StartTime/EndTime/Duration were specified explicitly instead of being anyElement* (e.g. an xsd:string that contains a unix timestamp) - Relatedly, is there any reason to have both Duration and EndTime instead of just one or the other? 2. Apparently, in the US, zip codes can have a different form than just an integer. 5 digits, a hyphen and 4 digits (e.g. 20037-8001): http://en.wikipedia.org/wiki/ZIP_code#ZIP.2B4 3. What's the expected use of the 'type' element in 'link'? 4. What's the expected use of the 'type' attribute on 'name'? Cheers, Aaron On Apr 18, 2011, at 10:44 AM, Roman Łapacz wrote:
Hi,
please. take a look at the RNC schema of nml base that I've attached to this email. Any comments, updates and suggestions are welcome.
regards, Roman <nmlbase-201103beta-v1.rnc>_______________________________________________ nml-wg mailing list nml-wg@ogf.org http://www.ogf.org/mailman/listinfo/nml-wg
Summer 2011 ESCC/Internet2 Joint Techs Hosted by the University of Alaska-Fairbanks http://events.internet2.edu/2011/jt-uaf
W dniu 2011-04-22 23:40, Aaron Brown pisze:
Hey Roman,
Hi Aaron,
Overall, it looks good. A few questions on the schema.
1. It'd be good if StartTime/EndTime/Duration were specified explicitly instead of being anyElement* (e.g. an xsd:string that contains a unix timestamp)
I did this way to have it very generic. The UML diagram from nml-base.pdf does not define too much details. For Lifetime it has only "sequence of (start,end)".
- Relatedly, is there any reason to have both Duration and EndTime instead of just one or the other?
I took it from https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/rnc/topo/nmtypes.rnc.
2. Apparently, in the US, zip codes can have a different form than just an integer. 5 digits, a hyphen and 4 digits (e.g. 20037-8001): http://en.wikipedia.org/wiki/ZIP_code#ZIP.2B4
I took it from https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/rnc/topo/nmtopo_base.rn.... This can be updated.
3. What's the expected use of the 'type' element in 'link'?
I took this attribute from the NML's UML diagram. It may have at least two values: "link" or "crossconnect". I remember the discussion that it should be removed but I haven't noticed any final agreement to do this so I included it in the schema.
4. What's the expected use of the 'type' attribute on 'name'?
I took it from https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/rnc/topo/nmtypes.rnc. I was trying to be as close to things defined in nmwg's topo stuff as possible because it seems to me quite complete and exists for few years (nmtb namespace shows 2007). Should this base schema be more detailed? I think in few places yes (e.g., time parameters) but it should be defined and agreed by the NML group. Cheers, Roman
Cheers, Aaron
On Apr 18, 2011, at 10:44 AM, Roman Łapacz wrote:
Hi,
please. take a look at the RNC schema of nml base that I've attached to this email. Any comments, updates and suggestions are welcome.
regards, Roman <nmlbase-201103beta-v1.rnc>_______________________________________________ nml-wg mailing list nml-wg@ogf.org <mailto:nml-wg@ogf.org> http://www.ogf.org/mailman/listinfo/nml-wg
Summer 2011 ESCC/Internet2 Joint Techs Hosted by the University of Alaska-Fairbanks http://events.internet2.edu/2011/jt-uaf
On 26/04/2011 16:11, Roman Łapacz wrote:
W dniu 2011-04-22 23:40, Aaron Brown pisze:
Hey Roman,
Hi Aaron,
Overall, it looks good. A few questions on the schema.
1. It'd be good if StartTime/EndTime/Duration were specified explicitly instead of being anyElement* (e.g. an xsd:string that contains a unix timestamp)
I did this way to have it very generic. The UML diagram from nml-base.pdf does not define too much details. For Lifetime it has only "sequence of (start,end)".
I agree that we could do with a better specification of those dates and the duration. Iirc there are some standard types in XML that can handle that.
- Relatedly, is there any reason to have both Duration and EndTime instead of just one or the other?
I think there are some scenarios where you'd use one or the other, or perhaps even both where you ask for a link that you will use for some duration, but it has to be before endTime.
2. Apparently, in the US, zip codes can have a different form than just an integer. 5 digits, a hyphen and 4 digits (e.g. 20037-8001): http://en.wikipedia.org/wiki/ZIP_code#ZIP.2B4
I took it from https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/rnc/topo/nmtopo_base.rn.... This can be updated.
Zipcode would be a good place to have just an xsd:string. Who knows what crazy scheme some countries come up with :) Jeroen.
On Apr 27, 2011, at 4:09 AM, Jeroen van der Ham wrote:
On 26/04/2011 16:11, Roman Łapacz wrote:
W dniu 2011-04-22 23:40, Aaron Brown pisze:
Hey Roman,
Hi Aaron,
Overall, it looks good. A few questions on the schema.
1. It'd be good if StartTime/EndTime/Duration were specified explicitly instead of being anyElement* (e.g. an xsd:string that contains a unix timestamp)
I did this way to have it very generic. The UML diagram from nml-base.pdf does not define too much details. For Lifetime it has only "sequence of (start,end)".
I agree that we could do with a better specification of those dates and the duration. Iirc there are some standard types in XML that can handle that.
Looks like there are some defined in http://www.w3schools.com/Schema/schema_dtypes_date.asp . They're kinda verbose, and don't seem to offer sub-second granularity, but I'm not sure either is all that important.
- Relatedly, is there any reason to have both Duration and EndTime instead of just one or the other?
I think there are some scenarios where you'd use one or the other, or perhaps even both where you ask for a link that you will use for some duration, but it has to be before endTime.
I'm not sure the semantics all that intuitive. e.g. <lifetime> <duration>3600</duration> <endTime>1304510973</endTime> </lifetime> Does the above mean "the circuit finishes at time 1304510973 and was active for 3600 seconds", or "the circuit is valid no later than time 1304510973, but was active for 3600 seconds sometime before then". Does this change if startTIme is specified as well?
2. Apparently, in the US, zip codes can have a different form than just an integer. 5 digits, a hyphen and 4 digits (e.g. 20037-8001): http://en.wikipedia.org/wiki/ZIP_code#ZIP.2B4
I took it from https://svn.internet2.edu/svn/nmwg/trunk/nmwg/schema/rnc/topo/nmtopo_base.rn.... This can be updated.
Zipcode would be a good place to have just an xsd:string. Who knows what crazy scheme some countries come up with :)
I'm sure the US can come up with a crazier scheme. I'll write my congress critters :) Cheers, Aaron Summer 2011 ESCC/Internet2 Joint Techs Hosted by the University of Alaska-Fairbanks http://events.internet2.edu/2011/jt-uaf
participants (3)
-
Aaron Brown -
Jeroen van der Ham -
Roman Łapacz