Location : public abstract class
Created: 3/12/2005 12:00:00 AM
Modified: 11/23/2006 10:40:16 AM
Project:
Advanced:
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>Location is an abstract superclass that represents the root of the DEN-ng location model. This provides a considerably simpler model than the corresponding SID model.<br/></p><p><br/></p><p>There are four fundamental types of Locations in the model: (1) Positions, (2) Addresses, (3) GeographicAreas, and (4) Structures. Please see the individual subclasses for more details on these four concepts.<br/></p>
Element Source Role Target Role Details
ContactMedium
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the set of Locations that this ContactMedium uses. The semantics of a particular communication (e.g., it is restricted to a particular set of Locations) is defined in the LocationContactMediumDetails association class.<br/></p>
BusinessContext
Class   		Name:  
  		Name:  
  		 
LocationComposite
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of Locations that make up this LocationComposite object. Note that at least one LocationAtomic (and zero or more LocationComposites) must be present.<br/></p>
BusinessContext
Class   		Name:  
  		Name:  
  		 
Element Source Role Target Role Details
PartyRole
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of PartyRoles that can be located at this particular Location.<br/></p>
EquipmentComponent
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>DONOTIMPLEMENT <br/></p><p>This association defines the concept of an EquipmentComponent existing at a particular Location. DEN-ng defines this in more detail.<br/></p>
EquipmentHolder
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>DONOTIMPLEMENT<br/></p><p>This association defines the concept of an EquipmentHolder existing at a particular Location. DEN-ng defines this in more detail<br/></p>
Equipment
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>DONOTIMPLEMENT<br/></p><p>This association defines the concept of an Equipment existing at a particular Location. DEN-ng defines this in more detail<br/></p>
PhysicalResource
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the Location(s) that a particular PhysicalResource can be found at. Note that there can be multiple Locations assigned for a particular PhysicalResource. For example, a Router can be installed in a POSITION in a Rack, which is in a particular PLACE (e.g., a Room in a Floor) which is in a particular STRUCTURE (e.g., a building) at a particular ADDRESS (e.g., the postal address that the main building is located at).<br/></p><p>    <br/></p><p>These four concepts (which are all in CAPS) are the four main subclasses of Location. More precise relationships can be made between the appropriate subclasses of PhysicalResource and the appropriate subclasses of Location. Please see the DEN-ng Location model for more information.<br/></p><p><br/></p><p>Note that this relationship is semantically different than the LogicalResourceLocatedAt association. This is because PhysicalResources are tangible objects that have different types of locations, whereas LogicalResources are intangible objects that are hosted by, or contained within, a PhysicalResource.<br/></p><p><br/></p><p>The semantics of this association are represented by the PhysicalResourceLocationDetails association class.<br/></p>
LogicalResource
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the Location(s) that a particular LogicalResource can be found at. Note that there can be multiple Locations assigned for a particular LogicalResource.<br/></p><p>    <br/></p><p>This relationship is semantically different than the PhysicalResourceLocatedAt relationship. This is because LogicalResources do not have physical presences, except through the PhysicalResource that they are bound to. For example, a DeviceInterface is bound to a PhysicalPort. The DeviceInterface doesn't have a location - the PhysicalPort does. Thus, the LogicalResource "location" is really the location of the PhysicalResource that contains, or hosts, the LogicalResource.<br/></p><p><br/></p><p>Please see the DEN-ng Location model for more information.<br/></p>
Service
Class   		Name:  
  		Name:  
 
<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the location(s) that a particular Service can be found at. Note that there can be multiple Locations assigned for a particular Service. Its semantics are defined by the ServiceLocationDetails association class. <br/></p><p><br/></p><p>Please see the DEN-ng Location model for more information.<br/></p>
Object Type Connection Notes
PartyRole Class Weak Copyright TM Forum 2005 This aggregation defines the set of PartyRoles that can be located at this particular Location.
LocationAtomic Class Tree  
LocationComposite Class Tree  
ContactMedium Class Class Copyright TM Forum 2005 This association defines the set of Locations that this ContactMedium uses. The semantics of a particular communication (e.g., it is restricted to a particular set of Locations) is defined in the LocationContactMediumDetails association class.
BusinessContext Class Class  
LocationComposite Class Weak Copyright TM Forum 2005 This aggregation defines the set of Locations that make up this LocationComposite object. Note that at least one LocationAtomic (and zero or more LocationComposites) must be present.
BusinessContext Class Class  
RootEntity Class Tree  
PhysicalResource Class Class Copyright TM Forum 2005 This association defines the Location(s) that a particular PhysicalResource can be found at. Note that there can be multiple Locations assigned for a particular PhysicalResource. For example, a Router can be installed in a POSITION in a Rack, which is in a particular PLACE (e.g., a Room in a Floor) which is in a particular STRUCTURE (e.g., a building) at a particular ADDRESS (e.g., the postal address that the main building is located at). These four concepts (which are all in CAPS) are the four main subclasses of Location. More precise relationships can be made between the appropriate subclasses of PhysicalResource and the appropriate subclasses of Location. Please see the DEN-ng Location model for more information. Note that this relationship is semantically different than the LogicalResourceLocatedAt association. This is because PhysicalResources are tangible objects that have different types of locations, whereas LogicalResources are intangible objects that are hosted by, or contained within, a PhysicalResource. The semantics of this association are represented by the PhysicalResourceLocationDetails association class.
LogicalResource Class Class Copyright TM Forum 2005 This association defines the Location(s) that a particular LogicalResource can be found at. Note that there can be multiple Locations assigned for a particular LogicalResource. This relationship is semantically different than the PhysicalResourceLocatedAt relationship. This is because LogicalResources do not have physical presences, except through the PhysicalResource that they are bound to. For example, a DeviceInterface is bound to a PhysicalPort. The DeviceInterface doesn't have a location - the PhysicalPort does. Thus, the LogicalResource "location" is really the location of the PhysicalResource that contains, or hosts, the LogicalResource. Please see the DEN-ng Location model for more information.
Service Class Class Copyright TM Forum 2005 This association defines the location(s) that a particular Service can be found at. Note that there can be multiple Locations assigned for a particular Service. Its semantics are defined by the ServiceLocationDetails association class. Please see the DEN-ng Location model for more information.