Hi Pierre, We have been working in the backend of the system, and we have found that we need to maintain the existing management of digital assets made by our Store in order to be able to validate the actual digital assets which are included as ProductSpecs in the catalog. Enclosed you can find a diagram that reflects this situation. There you can see that we have renamed the authorization proxy. This has been done since this proxy is currently making more complex validations than only the access token of the user. Regarding the asset management it is important to note that selling digital assets require some specific validations. For example validating that a provider creating a data product is the owner of the data (and this is diffrent depending if the data in in CKAN or in the Context Broker). In this respect, we are following this approach: - Specific types of digital assets are registered using plugins, which implement a set of handlers that allow to perform the needed validations. (This is already implemented). - The existing types of supported digital assets are exposed through an API. Currently, we are using our existing API since we haven't found how to save this info using the TMForum APIs. If you think that this can be done using a concrete TMForum API we can handle it. - The concrete asset type is included as a characteristic in the productSpecs - When a new product is created the logic-layer intercepts this request and validates that the given asset type is supported using the Asset Management module. Do not hesitate to ask if you have any doubt or give any comment regarding this architecture. Best regards, Francisco -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tmforum/attachments/20151027/0e9e7556/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE-TMF-AssetMngmt.png Type: image/png Size: 11585 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-tmforum/attachments/20151027/0e9e7556/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy