acronyms: PO = product offering; PS = product specification; POP = product offering priceIs the ProductSpecification the definition of the product itself and ProductSpecificationRef the definition of the connection between the Product Offering and ProductSpecfication? Yes.name, schemaLocation, target etc questions:I would suggest you read TMF630. It will clarify your other questions as they are relevant for any TMF API.@type is also very important to understandWhat is the difference between Ref and Relationship?
ProductSpecificationRef store relationships betwen PO and PS
ProductSpecificationRelationship create relationships between PS (with a relationshiptype to control the relationship, API doc has examples and good definition on page 56)."Ref" are generally the entity that expose related classes, like your example.
A general comment about this API:it shows the complete model of a given productoffering. We have POs with 50 prices, it doesn't mean customer will pay 50 prices. It's because the PO can have various prices, maybe a price for web channel, another for telephone, a discount if you're a new customer, a discount if you're a senior etc. All possible prices are returned by the API for a given productoffering.This also means that the consumer of the API must be capable of interpreting the payload.