[Nml-wg] id/idRef

[Roman Łapacz]

W dniu 2012-07-18 12:45, Freek Dijkstra pisze:
> On 12-07-2012 17:23, Aaron Brown wrote:
>> I don't have a strong opinion on using id/idRef, as the method, but the
>> idea is based around inheritance. As an example, you have port P defined
>> in topology T. When referencing the port in topology S, I might want to
>> override some of its properties (e.g. include our name for its Port).
> So you are saying that the difference between id and idRef is that an
> object referenced by an id inherits some of the properties (such as
> Location) from the parent object, while an object referenced by an idRef
> does not inherit there properties?
>
> I do like this concept.

But does NML need this? To me IdRef is only for referencing/reusing or 
chaining existing elements. That's all. Without inheritance. Simple use 
case: a resource X is defined in a topology storage/service TS1. X  is 
pointed in a topology storage/service TS2 (e.g. to describe multi-domain 
link). Use of IdRef for X in TS2 is very useful.

Roman

>
>> Another example might be the example I sent to the NSI list where I
>> override the VLANs of the PortGroup so that the VLAN is chosen from a
>> subset of the VLANs available.
> You mean the example in
> http://www.ogf.org/pipermail/nsi-wg/2012-July/001984.html? I like this
> use case, and I based my proposal to the NSI-WG on your ideas:
> http://www.ogf.org/pipermail/nsi-wg/2012-July/001993.html. However,
> neither example contained an id or idRef attribute, so I think id/idRef
> is not essential for this use case.
>
>
> Freek
>
> _______________________________________________
> nml-wg mailing list
> nml-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nml-wg