[Fiware-ngsi] OMA spec interpretation egarding NGSI10 ONVALUE subscription

[Fermín Galán Márquez]

Dear Martin,

Thanks for the feedback!

Maybe "ambiguity" is not the right word... maybe I have said "poorness in description". In particular, in table 5.4.2.1 it would be more clearer if the text for AttributeList include something like this:

"Whenever the NotifyConditions of the subscription are meet, a notifyContext request is snet to Reference URI. This notifyContext message includes the value of this attributes for the entities in EntityIDlist"

...or a similar wording.

Best regards,

------
Fermín

El 21/12/2012 11:54, Martin Bauer escribió:
Hi Fermin,

In my opinion, the semantics you describe corresponds exactly to what was the intended
semantics in NGSI-10. The trigger attribute can, but does not have be part of the attribute list to
be returned. Where do you see the ambiguity?

Best regards,

Martin

------------------------------------------
Dr. Martin Bauer
Senior Researcher
NEC Europe Ltd.
NEC Laboratories Europe
Software & Services Research Division
Kurfürsten-Anlage 36
D-69115 Heidelberg
Tel: +49/ (0)6221/4342-168
Fax: +49/ (0)6221/4342-155
E-Mail: Martin.Bauer at neclab.eu<mailto:Martin.Bauer at neclab.eu>
http://www.nw.neclab.eu<http://www.nw.neclab.eu/>

*************************************************************
NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 2832014

From: fiware-ngsi-bounces at lists.fi-ware.eu<mailto:fiware-ngsi-bounces at lists.fi-ware.eu> [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Fermín Galán Márquez
Sent: Friday, December 21, 2012 11:51 AM
To: fiware-ngsi at lists.fi-ware.eu<mailto:fiware-ngsi at lists.fi-ware.eu>
Subject: [Fiware-ngsi] OMA spec interpretation egarding NGSI10 ONVALUE subscription

Hi,

Recently, I have discovered a unambiguity in the OMA spec regarding NGSI10 ONVALUE subscriptions which solution is not clear to me, so I will try to describe it in this email to know what other people involved in NGSI in the project think.

Within the subscribeContextRequest parameters you define a list of entity/attributes (marked in blue in the example below) and a attribute within the ONVALUE condition (marked in red in the example below).

<subscribeContextRequest>
  <entityIdList>
        <entityId type="Room" isPattern="false">
          <id>OfficeRoom</id>
        </entityId>
  </entityIdList>
  <attributeList>
        <attribute>temperature</attribute>
        <attribute>lightstatus</attribute>
        <attribute>pressure</attribute>
  </attributeList>
  <reference>localhost:5000/notify</reference>
  <duration>PT1H</duration>
  <notifyConditions>
        <notifyCondition>
          <type>ONCHANGE</type>
          <condValueList>
                <condValue>temperature</condValue>
          </condValueList>
        </notifyCondition>
  </notifyConditions>
  <throttling></throttling>
</subscribeContextRequest>

My interpretation is that the condValue acts as trigger but what is included in the notifyContext message are the entity/attributes included in the lists under subscribeContextRequest. So, in this case, if temperature changes, then temperature, lighstatus and pressure are notified (although lightstatus and pressure have not changed). In fact, I could even have subscriptions in which the triggering attribute is not part of the attributes being included in the notifyContext message, e.g.

  ...
  <attributeList>
        <attribute>lightstatus</attribute>
        <attribute>pressure</attribute>
  </attributeList>
  ...
          <condValueList>
                <condValue>temperature</condValue>
          </condValueList>
  ...

What do you think?

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


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ngsi/attachments/20121221/3f1a89bb/attachment.html>