Skip to content

App Note 14 clarification for full API path #244

Description

@johnbilt

Context
AppNote 14 describes how to refer to TAMS content in other systems. This describes using tams:// plus the store address and relevant suffixes. The challenge that has come out is where the API has additional path elements between the domain and the TAMS API. For example the AWS implementation typically adds /Prod in the middle of the API path.

The philosophy of the app note is that the tams;// entry should directly match the full API path, however this is not clearly called out in the document. This has lead to a discussion in to another project which is referencing TAMS content about what should be included or not in the reference

Actions
Need to update App Note 14 to make it clear that the full API path should be included in all tams:// references. This should probably include more complex examples to make this clear

Outcome
Aims is to clarify a question that has been raised and remove any ambiguity. Other specifications which reference TAMS content should be able to refer to App Note 14 as the authority on this topic

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    tsc-discussDiscuss this issue at the next TSC meeting

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions