Regarding the schema at http://forge.gridforum.org/sf/go/doc15481 During the last OGF meeting, the following changes have been proposed. - Martin: rename Port/Interface -> Port (Freek: make it clear in the description that this concerns a logical port, not a physical port) - Martin: rename Device/Node -> Node - Guy: rename Network Element -> Network Object (as "network element" has a well established but different meaning in other organisations, namely that what we call Node) - Freek: Port is unidirectional (not bidirectional. This suggestion is based on experience with multicast, and complex adaptation stacks, which were harder to describe using bidirectional Ports. Suggested by Guy) - Freek: Adaptation and Deadaptation are separate classes (to make it unidirectional, just like links) - Martin: Make transport processing functions (Adaptation, Deadaptation and Unidirectional Link) a subclass of Service (see separate email) - Freek: Change the hasPort relation Node-Link to Group-Link and make Node a subclass of Group. This allows a relation between Port and Topology (for describing edge interfaces of a domain, which was not possible with the current schema). - Martin: Add time-based information. Each network object can point to _multiple_ time intervals (with start time and end time). The meaning is that if "the network object is available" during these time interval(s). It was shortly discussed that time intervals can be used for both inventory management as well as reservation data, though it is not yet entirely clear if this can be described with the same type of relation from network object to time interval. Regards, Freek Dijkstra