Hi, We have a few cases of convenience operations in which the processing of the "father" resource is exactly the same that the processing of the "child" resource with "/attributes": /ngsi9/contextEntities/{EntityId} and /ngsi9/contextEntities/{EntityId}/attributes /ngsi9/contextEntityTypes/{typeName} and /ngsi9/contextEntityTypes/{typeName}/attributes /ngsi10/contextEntities/{EntityId} and /ngsi10/contextEntities/{EntityId}/attributes /ngsi10/contextEntityTypes/{typeName} and /ngsi10/contextEntityTypes/{typeName}/attributes Why do we need such "duplication"? Best regards, ------ Fermín ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy