Hi all,
My first post here and am attempting to get more acclimated with TMF Open API modeling. I have been working with a team trying to use the TMF658 Loyalty Management API. They are looking to add a Shipping Address model (extended from the Address JSON schema) to the API in order for the object to be stored and retrieved later for display on a GUI. TMF658 mentions CustomerOrder on pg 15 (Processing of events that may result in a LoyaltyAction being executed (LoyaltyEarn, CustomerOrder, BusinessInteraction), but doesn't go into much details around it.
I am part of the Enterprise Architecture group trying to set guidelines around proper use and extensions around TMF Open APIs. The TMF658 base-spec doesn't include an Address model so I'm trying to understand if this API is the right place to put it. I think the challenge is still making the right judgment call about when to extend and when not to (and whether or not there are hard and fast rules around that).
Apologies in advance if this question appears pedestrian.
Thanks,
Kevin.
------------------------------
Kevin Ng
TELUS
------------------------------