Hi!
I've been looking into use cases for Customer Site management in the Customer and Product domain. In TMF637 Product Inventory API there is a relation to a "place" RelatedPlaceRefOrValue. Place is in SID Common domain: Location ABE, but is not really defined much. The use cases I'm looking at are not specific to Product Installation Address, but more to logical and physical Customer Sites like Head office, Side office, Stores etc. In some real life use cases the Site can be considered logical (organisation unit, lobby services, maybe some place-of-work where the actual geographical location is not important) Or moving, as in vehicles and animals. They are not really users and most cannot be modeled as Parties anyway. They are not Resources either as they represent Customer information and are not part of the functionality of the "Network".
TMF674 seems like a good API candidate for this, but there is a problem (for me at least) in the API Resource model and API Conformance Profile. It assumes every Site has a known and relatively fixed location as either "address" or "geographicLocation" is mandatory. In real life use cases it can be currently unknown, not applicable or not fixed.
Long story short, is there a possibility to change the relationship between GeographicSite and GeographicAddress from
0..* - 1 to 0..* - 0..1 in the TMF674 Geographic Site Management API Resource model? Then it would be usable for all use cases of Party Site Management as well.
P.S. Having a dummy address for this is not a good workaround.
------------------------------
Niko Kolari
Enterprise Information Architect
DNA Plc
Finland
------------------------------