[Nml-wg] NMLify of AutoGOLE topology

[Roman Łapacz]

W dniu 2012-02-22 10:52, Freek Dijkstra pisze:
> Hi all,
>
> I've tried to NML-ify the AutoGOLE topology. I did in RDF/XML because
> that is probably readable by both OWL and XML folks.
>
> Below are the steps I took in detail, along with intermediate results
> (which may help in understanding the differences).
>
> The main changes are:
> - made ports and link unidirectional, per NML specs.
> - use explicit link object to describe the SDP
>    (NML has no connectedTo concept)
> - change the urn:ogf:network identifiers to a valid syntax,
>    the ones currently in AutoGOLE use are not valid according
>    to proposed standard nor previous use in either GLIF or
>    perfSONAR community.
>
> The file AutoGOLE-Topo-2012-02-22.rdf gives the result so far.
>
> Notes:
>
> 1. The resulting topology file has three layers:
>    - NML topology
>    - dtox NSNetwork
>    - dtox NSA
>    I really like the clear distinction between the data plane (NML) and
> control plane (dtox/NSI). However, I wonder if we should move this to
> two layers, perhaps merging dtox:NSNetwork and nml:topology.

I'm not sure of this distinction if nml:bidirectionalport is STP (I have 
a problem with this: dtox:hasSTP in dtox:NSNetwork points at 
nml:bidirectionalport; moving from dtox to nml domain does not look 
right to me in this case). All elements in the example belong to NSI 
abstraction (links are SDPs, ports STPs; except VCard part). To me 
distinction is between NSI topology (represented by STP, SDP, NSNetwork, 
NSA) and internal domain topology which is hidden under mapTo relation.

btw. I'm still thinking that we don't need nml:bidirectionalport in NML 
:) We could use port with "bidirectional" relation.

Roman

> 2. The dtox:hasSTP relation now points to a nml:bidirectionalport. NML
> defines a similar "hasPort" relation between a nml:Topology and
> nml:Port. (and there is some discussion to differentiate between
> hasOutboundPort and hasInboundPort). If dtox:NSNetwork and nml:topology
> are merged, I recommend to use these relations.
> 3. Yet unclear how exactly to tie Ethernet specifics to the examples, it
> seems prudent to use labels and the subnetwork concept as discussed in
> the NML-WG in Lyon (see subversion:
> https://forge.ogf.org/svn/repos/nml-examples/20110922/other_examples/configured_vlan.xml;
> you need a gridforge login. Drop me a line if you can't access it.)
>
>
> Regards,
> Freek Dijkstra
>
>
> List of steps I took:
>
> Source: AutoGOLE-Topo-2012-01-25.owl
>
> Removed owl:NamedIndividual
> Removed schema definitions (owl:Ontology, owl:AnnotationProperty, etc.)
> Removed Position comments (used by auto-gole.appspot.com)
> Removed unnecessary comments
>
> Result: AutoGOLE-Topo-2012-01-25.rdf
>
> Changed dtox:lat, dtox:long and dtox:Location to geo84:lat, geo84:long
> and geo84:SpatialThing
> Corrected label of Netherlight location from Copenhagen to Amsterdam
> (geo84 was OK)
>
> Changed dtox:STP to nml:bidirectionalport
> Grouped ports of a single network in a nml:topology
> Commented dtox:connectedTo, since this is not valid NML
> Added rdfs:label to all NSA and all locations
> Changed admin contact from string to vCard
>
> Result: AutoGOLE-Topo-2012-02-20.rdf
>
> Change urn:ogf:network identifiers to valid syntax
> (urn:ogf:network:<FQDN>:<date>:<opaque>)
> Make all bidirectional ports unidirectional
> Explicitly defined NML links, with sources and sinks
>
> Result: AutoGOLE-Topo-2012-02-22.rdf
>
> Possible future direction:
>
> Merge NML:topology with dtox:NSNetwork
> Remove the dtox:managedBy property, as there is already an inverse
> relation dtox:managing to find the correct dtox:NSA
> Added switch matrix to each NML topology
> Define switching capabilities for each topology.
> use nml:hasPort instead of dtox:hasSTP
>
> Result: (the-AutoGOLE-future-is-yet-to-be-written.rdf)
>
>
> _______________________________________________
> nml-wg mailing list
> nml-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nml-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nml-wg/attachments/20120222/9f6fa33f/attachment.html>