Attached are the meeting notes made in OGF30 in Brussels. For slides and this form in ASCII, see http://forge.gridforum.org/sf/docman/do/listDocuments/projects.nml-wg/docman... Regards, Freek Rough Consensus =============== * Namespace for schema (object and attribute identifiers) is http://schemas.ogf.org/nml/base/2013/10/ (with year and month the date of the actual schema) * Instance identifiers SHOULD follow the urn:ogf:network:domain.name:opaque_id syntax. These identifiers are case insensitive, and non-international. * Instance identifiers are not restricted in length, like GLIF requires. * Different objects eg link and port MUST have different identifiers * Everything is just a link – don’t need to distinguish between paths, links and segments. * "Group" is subclassed with "BidirectionalLink", "BidirectionalPort", etc. * Allow grouping of 2 serial compounds links * Disallow relating groups together until a clear use case and related logic is presented. * Adaptation relates ports, not links. This is still open for discussion. * cross connects must be included in a serial compound link * connectors (plastic) can be described as a port, without the need to describe a cross connect Action Items ============ * Revise definition of multiplexing: Freek, Jeroen * Setup a teleconference: Jeroen * Ask for whiteboard software (Adobe connect) for teleconference: Jason * Specs for delegation of urn:ogf namespace: Freek, Richard, Joel Replogle * Specs for urn:ogf:network identifiers: Freek * Propose description of multicast and broadcast links: Richard, Freek * Create example of adaptation on Port/Link: Jeroen, Jason * Given example of serial compound links with and without cross connect: Freek * How to specify properties of relations: <question postponed> * How to specify the order in relations: Jason (XML), Jeroen (RDF) * Explain NSI requirements/solutions for channels and labels: Tomohiro