Not aware of any discussions in this area.
You are correct that using the specification pattern allows things to be defined dynamically, but you need to ask the question - how feasible or relevant is it to use dynamic behavior. It could be argued that strongly-typed extensions give you a firmer contract.
And even in the "classic" area for dynamic definition - product/service/resource catalog, we are seeing a move towards domain-specific modeling for lines of business.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Dec 13, 2022 14:27
From: Jason Funk
Subject: Retail Store (physical store)
Ran across this thread while looking for ways to store site data. Has any consideration been given to creating site specifications? They could be used to define the particular types of sites including the characteristics required by those sites. This would enhance the existing without the need for subtyping things. I've wondered, a few times, why the specification/characteristic pattern wasn't applied to more objects...
------------------------------
Jason Funk
Metronet
Original Message:
Sent: Nov 12, 2018 02:36
From: Jonathan Goldberg
Subject: Retail Store (physical store)
While waiting for this Retail Premise API (which is indeed on the API map as future, in the Enterprise domain), you could extend the Geographical Site resource model with custom enhancements, or create a new resource model that refers to Geographical Site. There are various ways of doing this, you will have to consider which best fits your need:
- Add characteristics to the resource (completely dynamic, but you will not be able to take advantage of schema validation)
- Add strongly-typed attributes to the resource
- Subclass the resource and add attributes to the subclass, using @type and @schemalocation
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Original Message:
Sent: Nov 12, 2018 02:28
From: Koenraad Peeters
Subject: Retail Store (physical store)
Hi Antonio,
I believe a "Retail Premise" API is listed as a future extension in the Open API Map.
You can either wait for that API to appear or even contribute your own initial proposal for this API.
Regards
------------------------------
Koenraad Peeters
Ciminko Luxembourg
Original Message:
Sent: Nov 09, 2018 09:27
From: António Ribeiro
Subject: Retail Store (physical store)
Dear Forum,
I would like to use an API in order to save information related to Retail Store, such as:
- Name,
- Address
- Calendar (opening and closing hours)
- Other information related to the store
I've discovered the APIs called "Geographical Site, Address and Location" but they cannot fit in 100% because I don't have any possibility to insert the other information related with the store, for <g class="gr_ gr_1832 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" id="1832" data-gr-id="1832">example</g> In Customer Management API you can insert other info through Characteristics.
Is there another API that I can use for this particular case? Or can you suggest another approach to solve this?
Thanks in advance
------------------------------
António Ribeiro
Celfocus
------------------------------