RE: [camp] Metadata Bootstrapping at the platform

Logged in JIRA: https://issues.oasis-open.org/browse/CAMP-177

From: Norman, Michael [mailto:michael.norman@jpmchase.com]
Sent: 26 February 2015 10:40
To: camp@lists.oasis-open.org
Subject: [camp] Metadata Bootstrapping at the platform_endpoints level

Hi guys,

I’m new to this list and to working with the API so please tell me if there is another place I should post this.

I may be missing something completely obvious, but I’ve hit a problem.

I’m trying to understand how I can source the metadata about the API in order to write a GUI client which constructs itself based on the metadata it sees. That way my client is only dependent on the structure of the API and doesn’t need to carry any semantics of the API itself, and so I can extend the API without having to write any new GUI code.

So, the obvious way to do this seems to be for the platform_endpoints resource to carry the metadata for the entire domain. However, the metadata is present in the type_definitions_uri of the platform Resource, which causes a couple of problems.

· The platform resource has a one-to-many relation with the platform_endpoints resource, so the platform_endpoints’ metadata sourced from the set of platforms is potentially ambiguous.

· The platform is behind authentication and the platform_endpoints resource potentially isn’t

· If we extend the platform_endpoints resource the only way we can retrieve the metadata is from a platform that knows about that extension. This breaks the loose coupling across the parent-child relation afforded by the Links (which is really nice, by the way)

I can see that there is a problem with versioning of metadata and the Platforms need to run with different versions and this may be why you’ve done it this way. However, I can’t see a way of dealing with the three problems above without extending the API – and making my GUI dependent on that extension being present, which kind-of defeats the point.

The specific extension I have been looking at involves carrying the metadata of the Resource into their corresponding List resources (e.g. putting the metadata for the platform_endpoint into the platform_endpoints resource).

Any help with this would be appreciated.

Thanks,

Mike

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.

camp message