Figure L.15 - Links to Other Parts of the SID Model

<b>Location & Address Role</b><br/>In the Party SID model facet, we defined roles that parties (people and organizations) may play. In a similar fashion, we may find it useful to define location and address roles. This will allow us to use a single location or address for different purposes, e.g. a single address may be a:<br/>        • Customer billing address<br/>        • Phone directory address<br/>        • CPE equipment location address and a<br/>        • Geographic plant reference address (pillar outside the front of …).<br/>Because the role requirements are simpler than in the Party SID model facet, Location roles have been modeled as associations. [Fowler-role]<br/>Care should be taken not to confuse when to create address & location subtypes versus address & location roles.<br/><br/><b>Interworking with the rest of the SID model</b><br/>Fig 15 shows some possible connections from Location to other parts of the SID model. This diagram is intended to be illustrative rather than prescriptive.<br/>The SID model doesn’t store GeoSpatial information as a part of every entity. As each entity is modeled, we determine whether the entity has GeoSpatial attributes or refers to GeoSpatial attributes. For network equipment, we create abstract GeoSpatial entities of location and route section etc. and reference these from the network elements.<br/>To reiterate; Location information should not be stored in Product, Party or Network Resource entities but associated with a Place. <br/>If a Place exists, it should be shared and not duplicated.<br/>This allows queries that would otherwise require GeoSpatial queries to be done textually, i.e. to check if two network elements are at the same location, just see if the place ids are the same. <br/>When placing a Resource or a Product, the choice is to associate to an:<br/>        • address, or<br/>        • site, or<br/>        • location <br/>