SourceForge : artf6580: Relate Node/Topology to a Link

Project: NML-WG Trackers > Schema Progress > View Artifact

Artifact artf6580 : Relate Node/Topology to a Link

Tracker:	Schema Progress
Title:	Relate Node/Topology to a Link
Description:	Proposal: Allow the following eight relations: Node --isSource--> Link Node --isSource--> LinkGroup Topology --isSource--> Link Topology --isSource--> LinkGroup Node --isSink--> Link Node --isSink--> LinkGroup Topology --isSink--> Link Topology --isSink--> LinkGroup Meaning that the given Link/LinkGroup is a source or sink of the given Node or Topology. Rationale: This allows for a shorted NML description than the current relations: Node --hasOutboundPort--> Port --isSource--> Link Node --hasInboundPort--> Port --isSink--> Link
Submitted By:	Freek Dijkstra
Submitted On:	07/30/2012 6:07 AM EDT
Last Modified:	11/30/2012 7:30 AM EST
Closed:	11/30/2012 7:30 AM EST

	Status / Comments		Change Log		Associations		Attachments

Status
Status:*	Completed
Category:*	– Link / Path / Segment
Priority: *	3
Assigned To: *	None

Comments

Jeroen van der Ham: 11/30/2012 7:30 AM EST
	Comment:	Moved to: https://redmine.ogf.org/issues/44
	Action:	Update Closed set to 11/30/2012 Status changed from Under discussion to Completed

Jason Zurawski: 08/16/2012 11:34 AM EDT

Comment:

I understand your point of view, but I stand by my assessment that any time you add shortcuts around something complex, they become more widely used. 
 

I would still vote for not doing this, but vote around me as needed :)

Action:

Update

Freek Dijkstra: 08/16/2012 9:26 AM EDT

Comment:

Jason, a use case is a highly abstracted topology description, where only Topologies and Links between Topologies are described.

This feature, along with artf6507, allows for very compact NML by not describing Ports, but only Nodes and Links.

In the repository nml-examples/201206-lhcopn, you can see that such an approach would reduce the NML description by roughly 60%.

I'm aware that this is unconventional, and will bot become mainstream even if published as a standard. So this is an experimental feature. Meaning 
that it is NOT RECOMMENDED in production use, but still allowed (eg the standard allows for such extensions) for those weirdos (like me) who like to 
play with it for academic purposes.

Action:

Update

Jason Zurawski: 08/16/2012 8:38 AM EDT
	Comment:	I don't like this, it seems very awkward just to create a shortcut. the explicit string of relations is more clear to me.
	Action:	Update

Freek Dijkstra: 08/08/2012 10:28 AM EDT
	Action:	Update Priority changed from 4 to 3

Freek Dijkstra: 07/30/2012 6:07 AM EDT
	Action:	Create

Return

< Previous

Next >