[Fiware-tmforum] FIWARE - TMForum Asset Management

[Pierre Gauthier]

I was planning for a call at 9:00 AM Thursday.


Regards
Pierre Gauthier
Chief API Architect
TM Forum
t +1 (819) 743-9342
e pgauthier at tmforum.org<mailto:pgauthier at tmforum.org>
w www.tmforum.org<http://www.tmforum.org>

On Nov 3, 2015, at 9:46 AM, jeanluc.tymen at orange.com<mailto:jeanluc.tymen at orange.com> wrote:

Hi Pierre and Francisco,

At what time would you plan the Fiware-TMForum call on Thursday?

Pierre, would you send us a recurrent invitation for our Tuesday weekly calls as promised ☺?

Regards

Jean-Luc

De : fiware-tmforum-bounces at lists.fiware.org<mailto:fiware-tmforum-bounces at lists.fiware.org> [mailto:fiware-tmforum-bounces at lists.fiware.org] De la part de Francisco de la Vega
Envoyé : mardi 3 novembre 2015 10:19
À : Pierre Gauthier
Cc : fiware-tmforum at lists.fiware.org<mailto:fiware-tmforum at lists.fiware.org>
Objet : Re: [Fiware-tmforum] FIWARE - TMForum Asset Management

Hi Pierre,

Today I am traveling to hamburg, so I agree to have our conf call on Thursday.

Best regards,
Francisco

2015-11-03 0:59 GMT+01:00 Pierre Gauthier <pgauthier at tmforum.org<mailto:pgauthier at tmforum.org>>:
Hi Francisco,

Lets talk about that this week on our weekly Conf Call.

I will be coming back form China on Monday.

Cn we have our Conf Call exceptionaly on Thursday the week ?

Regards
Pierre Gauthier
Chief API Architect
TM Forum
t +1 (819) 743-9342<tel:%2B1%20%28819%29%20743-9342>
e pgauthier at tmforum.org<mailto:pgauthier at tmforum.org>
w www.tmforum.org<http://www.tmforum.org/>

On Oct 27, 2015, at 9:36 AM, Francisco de la Vega <fdelavega at conwet.com<mailto:fdelavega at conwet.com>> wrote:

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
<FIWARE-TMF-AssetMngmt.png>



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tmforum/attachments/20151103/c5d2036d/attachment.html>