Hi Freek/All; On 3/28/12 5:30 AM, thus spake Freek Dijkstra:
Jeroen van der Ham wrote:
We'll be discussing most of the issues I sent out earlier. Freek will followup with a more detailed list soon.
We propose to discuss the following topics: * implicit hasTopology relation between Topology and (sub)topology artf6537
https://forge.ogf.org/svn/repos/nml-examples/201203-subtopology/hasTopology.... (proposal #2 and optional #1)
Since I won't be on the call, I include the exchange from early May via email in this ticket, and my commentary to the various proposals.
* implicit hasNode relation between Topology and Node (no artifact created)
https://forge.ogf.org/svn/repos/nml-examples/201203-subtopology/hasNode.xml (proposal #1 and optional #3)
Commentary on this also in the notes/email exchange, and included in artifact 'artf6537'
* name of the serial compound relation is "isSerialCompoundLink" https://forge.ogf.org/sf/go/artf6545 https://forge.ogf.org/sf/go/artf6510 (related)
https://forge.ogf.org/svn/repos/nml-examples/201203-vlans/compoundlink.xml (first question at footer)
This is fine by me.
* What is the direction and name of the relation between Port and Link? https://forge.ogf.org/sf/go/artf6538 (second part)
https://forge.ogf.org/svn/repos/nml-examples/201203-vlans/compoundlink.xml (second question at footer) (this needs some further explanation, I'll provide that shortly)
Being consistent is what would prefer, either: - we always use the same 'direction' but multiple works (is/has) - We always use the same word (has or is) and that may imply different directions I can get used to either I suppose.
* VLAN is a link with multiple source and multiple sink ports, and optional parameter noReturnTraffic https://forge.ogf.org/sf/go/artf6503 https://forge.ogf.org/sf/go/artf6542 (duplicate) https://forge.ogf.org/svn/repos/nml-examples/201203-vlans/vlan-link.xml
These proposals were fine with me, the only extra comment I could add is if we need to be 'naming' (assigning IDs) to bidirectional ports and links for later use. Thanks; -jason
Sorry for the delay. I was too tired yesterday, and found that not all issues have an artifact, and a few duplicate artifact were created, and some artifacts cover two items. I'll try to correct this in a few hours time and post a full proposal.
Freek