Freek Thanks, I very much appreciate this feedback. We seem to be on the same track (which is good), and gives some good textual suggestions. Also, I very much like to see that "is_on_fire" attribute be put into action some day ;) Freek
I think this is a general case of "undefined attributes or relationships are undefined". If someone adds a 'version' attribute to a Port, the fact that we've got an attribute for Topologies is immaterial. It should be treated in the same manner as if they'd added a 'is_on_fire' attribute to a Node. Same deal with the relationships. If someone adds a "hasTopology" for a service or whatever, then it's treated the same as if they'd added a "hasPortIfOnFire" relationship to a Node.
We could probably get away with "NMLv1 parsers SHOULD ignore undefined attributes or relationships. NMLv1 generators MAY add attributes or relationships outside of the NMLv1 specification, but MUST NOT assume that other parsers will handle those attributes or relationships.", and the cases above would simply implicitly be part of this.
Cheers, Aaron
Regards, Freek _______________________________________________ nml-wg mailing list nml-wg@ogf.org <mailto:nml-wg@ogf.org> https://www.ogf.org/mailman/listinfo/nml-wg
ESCC/Internet2 Joint Techs July 15-19, 2012 - Palo Alto, California Hosted by Stanford University http://events.internet2.edu/2012/jt-stanford/