[Nml-wg] XML Examples and Proposals

Freek Dijkstra Freek.Dijkstra at sara.nl
Fri Mar 9 18:49:47 EST 2012


Hi Guys,

I hope you like XML.

I've just filled the nml-example repository with a whole bunch of
examples and proposals that I like to go through next week at the OGF.

If you haven't checked it out, do so now:
  svn checkout --username YourGridForgeName \
     https://forge.ogf.org/svn/repos/nml-examples

If you get a permission error, let me know off-list.
The examples are also attached to this mail, but be aware that I may
improve some typos and add clarifications in the coming days.

The examples and proposals are:

subtopology - hasNode
    four alternative proposals how to relate a topology and a node

subtopology - hasTopology
    one example and three questions how to relate a topology to
    a subtopology (hopefully trivial after we decided on hasNode)

subtopology - inbound-outbound-ports
    four proposals to decide on the term for ingress and
    egress ports

subtopology - alias
    three proposal to relate a external port of a topology
    with its internal structure

versioning - lifetime
    a (surely flawed) example how I interpreted Aaron's
    description of the current use of lifetime in IDC.

versioning - aliases-lifetime
versioning - aliases-version
    six proposals to describe the changes in a network over
    time using either a lifetime object or a version attribute

vlans - compoundlink
    two questions on the exact name of the source/sink relation
    and the serial compound link relation

vlans - vlan
    a proposal to describe vlans (Ethernet subnets) between
    hosts

vlan - shared-switchingservice
vlan - multiple-switchingservice
    <not yet written -- will follow sunday or monday>
    two proposals to describe multiple VLANs as one or more
    switching services inside a single node

In case you wonder "haven't we decided on that already" -- in most
cases, "yes" -- while going through previous examples, I've noted some
small discrepancies. For examples some examples used "source" relation,
while others used "hasSource". I don't care, so we should decide, and
that's what this is about: make sure that we make a decision. Note the
consensus and make the decision authoritative, so we can refer back to
it, and update the previous examples to comply with the decision.

I did my best to make all proposals stand on it's own, and VERY much
hope that the decision for most proposals is a formality without discussion.

Regards,
Freek
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nml-examples.zip
Type: application/zip
Size: 32065 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nml-wg/attachments/20120310/c246fb47/attachment-0001.zip>


More information about the nml-wg mailing list