I volunteered (was coerced into) writing some use cases for deliverable #2. One reason I liked to do that was because I wanted to check if our schema can actually be used. Attached is the list of use cases I actually made during the previous OGF but never sent out. Jason and Jeff asked me about it, so here it is. If you are interested in a particular use case, make it yours, and check if the schema as we have can support the use case. If not, propose a change to Jeroen van der Ham (the document editor) or to the group on this list. Regards, Freek - describe a patch panel - describe a job description - describe computing resources as end-points for networks (link to other resources) - historic data (time based information) - aggregation multiple devices into a network - switching capability of an wavelength selective switch - describe Ethernet interface in a SONET switch that embeds 1 Gb/s Ethernet in 7 VC-4 with GFP-F. - partitioning of a device (e.g. for virtualisation) - broadcast switch, e.g. multiple interfaces in the same VLAN in a device. - multicast network. - inverse adaptation - is a connection through a domain with an adaptation (interworking function) a link? Are we modelling technology boundaries or administrative boundaries? - describe a virtual network over one or more physical networks, where the control of the virtual network is also delegated to a virtual organisation. Different links: - provided by underlying layers, but in practice static - dynamic (provided underlying layers) - unidirectional, bidirectional - point-to-point, point-to-multipoint (multicast), multipoint-to-multipoint (broadcast) - should we define a specific term for a tandem link between edges of a domain? (so an organisation name rather then a technological name). would this be a subnetwork connection?