June 2011 - nml-wg - lists.ogf.org

Conference Call June 30th
by Jeroen van der Ham 27 Jun '11

27 Jun '11

Hello, We have another call coming up on June 30th at the usual time and place: UTC 15:00 = 8:00 PDT = EDT 11:00 = 17:00 CEST. Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145 Since last call I've also worked to write out the NML schema in OWL so that we can use a graphical editor that was created in our group. Please have a look: http://nml-editor.appspot.com/ In the ontology I defined the superclass "relation" and some specific relations, but unfortunately our editor has a bit of trouble with that so only the generic "relation" is used. Also the editor does not yet support the creation of OWL/RDF Containers. Jeroen.

1 0

RNC questions
by Freek Dijkstra 21 Jun '11

21 Jun '11

Hi, Today, I was trying to create and improve an example topology file based on the RNC schema. Unfortunately, the current RNC schemata do not validate when used with a stricter parser. We tried last week with Jing-Trang, and that gave no errors. Today, I tried with http://validator.nu/ and got a few more errors. Could someone answer my noob questions on RNC? (Either on-list or off-list). 1) What is the difference between Lifetime = element lifetime { StartTime, (EndTime | Duration)? } and Lifetime = element lifetime { StartTime & (EndTime | Duration)? } and which one should I use? The goal is a lifetime element with a start element (defined in the StartTime rule) and optionally an end OR duration element (respectively defined in the EndTime and Duration rules). 2) I read on http://relaxng.org/compact-tutorial-20030326.html that the order is relevant in RNC. Thus <location><latitude>51.5155</latitude><longitude>-0.0922</longitude></location> is different from <location><longitude>-0.0922</longitude><latitude>51.5155</latitude></location>. Is there a way to specify in the RNC schema that this order is irrelevant in the XML? 3) The NML Group is -by it's current definition- recursive: A group is a NML NetworkObject, and a Group can contain NML NetworkObjects, thus including other groups. I have a problem with such recursive definitions in RNC. At least the validator complains about patterns defined later on in the document. Can't I do that, or am I just doing something wrong (I'm happy to provide offlist the URLs of RNC schema and example topology file I'm currently working on, so you can see the errors for yourself) 4) In the current RNC schema, extensibility was ensured using the "anyElement" rule. E.g. BasePortContent = NetworkObject & element capacity { xsd:float }? & anyElement* Unfortunately, the validator complained about this. When checking a document, it is unclear if a "location" element should be parsed according the second rule (element capacity { xsd:float }?) or third rule (anyElement*). When reading about this, it was suggested to remove the anyElement* from the BasePortContent, since it is possible to still add new allowed element in the following method: BasePortContent = NetworkObject & element capacity { xsd:float }? # later extension: BasePortContent &= element my_extension { xsd:string }? I have some more questions, but these were the most important ones. If some RNC expert could help me out or point me in the right way, GREAT! Freek

3 7

RNC schema
by Freek Dijkstra 20 Jun '11

20 Jun '11

Hello all, Roman Łapacz has kindly provided a Relax NG Compact Syntax (RNC) file with a draft of the NML schema as it currently stands. Allow me to publicly thank Roman for creating this RNC file. I have to agree with Jeroen's comment on last' weeks conf call, that this is an important step forward. Thanks Roman, and all those who contributed to it (I like to specifically mention to Aaron Brown for contributing to earlier discussions.) With permission (thanks!) I uploaded the RNC file to Gridforge: http://forge.gridforum.org/sf/docman/do/viewDocument/projects.nml-wg/docman… This also includes a modification that Jeroen and I created last week. I have a few questions, but for now I just wanted to thank Roman for his contribution. Regards, Freek

1 0

bidirectional/unidirectional link
by Aaron Brown 16 Jun '11

16 Jun '11

Hey Martin, On the call today, the topic of having explicit unidirectional vs. bidirectional link elements came up. I tried to give your example of the need for a unified element for links (the one related to SCinet), but am pretty sure I did an awful job at it. Is there any way you could send an email to the mailing list describing it? Cheers, Aaron Summer 2011 ESCC/Internet2 Joint Techs Hosted by the University of Alaska-Fairbanks http://events.internet2.edu/2011/jt-uaf

2 1

Conference call Thu June 16nd
by Freek Dijkstra 16 Jun '11

16 Jun '11

During today's call we agreed to have another conference call in two weeks time. The next NML call is scheduled on June 16th at UTC 15:00 = 8:00 PDT = EDT 11:00 = 17:00 CEST. Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145 Regards, Freek

2 3

Notes of Jun 2 conf call
by Freek Dijkstra 02 Jun '11

02 Jun '11

Today we had a short call, with Aaron Brown, Jeroen van der Ham, Roman Łapacz, and Freek Dijkstra. Jeroen, Freek and Roman expressed the desire to propose a schema document to the NML group at the next OGF 32. We will use the RNC schema from Roman and others as the base document (this RNC file is attached). Jeroen and Freek will meet in person somewhere in the next weeks to review this file and provide feedback to Roman. Then, we'll try to make a proposal to the NML group together. We will ask for 2 NML sessions during OGF32 on Friday July 15. There were two talks at previous TERENA conference (TNC2011) which mentioned NML. These talks where by know culprits Jeroen and Freek https://tnc2011.terena.org/core/presentation/55 https://tnc2011.terena.org/core/presentation/73 Jeroen's talk had a path finding background, while Freek's talk had a monitoring background -- two distinct application types. There was some talk about a "NSI topology", but it was not clear what this is. The NWI working group is now finishing there protocol document, and will work on this later. Jeroen will keep track of the NSI work. Jeroen requests everyone to review to the current schema document, and make fixes and changes, either to your allotted sections or other sections. The documents are in the NML-base repository, and can be checked out and checked in by anyone who is member of the NML group (i.e. you can, and if not, ask Freek, Martin, Jeroen or Paola) http://forge.gridforum.org/sf/scm/do/viewRepository/projects.nml-wg/scm.nml… Regards, Freek

1 0

Conference call Thu June 2nd
by Freek Dijkstra 01 Jun '11

01 Jun '11

Reminder for tomorrow's call: I would like to schedule another NML call on June 2th at UTC 15:00 = 8:00 PDT = EDT 11:00 = 17:00 CEST. Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145 On the agenda is a small summary of the presentations at TNC, and how to get the good ideas we've seen into the schema. Regards, Freek

1 0