[Fiware-ngsi] details on registerContextRequest

[Ken Zangelin]

Hi again,

first of all, thank you very much for all the replies to my initial doubts. Very helpful indeed.
Now, I've started to implement the 'registerContext' and I just want to make sure I implement
exactly what is desired ...

Using the example input for a 'registerContextRequest' from subversion:

<?xml version="1.0" encoding="UTF-8"?>
<registerContextRequest>
    <contextRegistrationList>
        <contextRegistration>
            <entityIdList>
                <entityId><id>ConferenceRoom</id><type>Room</type><isPattern>false</isPattern></entityId>
                <entityId><id>OfficeRoom</id><type>Room</type><isPattern>false</isPattern></entityId>
            </entityIdList>
            <contextRegistrationAttributeList>
                <name>temperature</name>
                <type>degree</type>
                <isDomain>false</isDomain>
                <metaData>
                    <contextMetadata><name>ID</name><type>string</type><value>1110</value></contextMetadata>
                    <contextMetadata><name>XXX</name><type>YYY</type><value>ZZZ</value></contextMetadata>
                </metaData>
            </contextRegistrationAttributeList>
            <registrationMetaData>
                <contextMetadata><name>ID</name><type>string</type><value>2212</value></contextMetadata>
                <contextMetadata><name></name><type></type><value></value></contextMetadata>
            </registrationMetaData>
            <providingApplication>http://192.168.100.1:70/application
            </providingApplication>
        </contextRegistration>
    </contextRegistrationList>
    <duration>PT1M</duration>
    <registrationId>1579964ss5t</registrationId>
</registerContextRequest>

I treat this message as containing two entities ('ConferenceRoom' and 'OfficeRoom') of type 'Room', both with
one attribute ('temperature', of type 'degree') that has two metadatas: ID and XXX.
The providing application for both these entites is 'http://192.168.100.1:70/application' and the entities
will live for one month from the second I receive this request.
For both entities, the registration id is '1579964ss5t'

Is this correct so far?

Doubts:

01. We should be able to send more than one attribute, right?

    How come '<contextRegistrationAttributeList>' isn't defined like this? :

      <contextRegistrationAttributeList>
        <contextRegistrationAttribute>
          <name>temperature</name>
          <type>degree</type>
          <isDomain>false</isDomain>
          <metaData>
            <contextMetadata><name>ID</name><type>string</type><value>1110</value></contextMetadata>
            <contextMetadata><name>XXX</name><type>YYY</type><value>ZZZ</value></contextMetadata>
          </metaData>
        </contextRegistrationAttribute>
        <contextRegistrationAttribute>
         [ second attribute ]
        </contextRegistrationAttribute>
      </contextRegistrationAttributeList>


02. After one month (PT1M), what do I do with the expired entities?
    Do I simply remove them, or do I mark them as 'expired' and I keep them in storage?
    If kept, they could be 'relived' easily ...
    Also, the duration is only associated to the entity, not to individual attributes, right?

03. Assume a second 'registerContextRequest' arrives, containing one of these two already registered entities.
    New attributes from this second request are added to the entity while already
    existing attributes (coinciding 'name' and 'type') are updated.
    Actually, here I need to take a look at ID in metadata as well.
    The new duration is used (if provided).
    If the providing application is changed, ditto. etc.
    This request would have to contain a registrationId that coincides with the registrationId that registered the
    entity in the first place.

    Correct?

04. The registration metadata ...
    These attributes I will save together with the registration id, but, I'm not sure
    what the attributes will be used for ...


That's all for now, more is sure to come ... Please bear with me :-)

/KZ


________________________________

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/20120509/0d0d63b5/attachment.html>