10 Nov
2014
10 Nov
'14
6:39 a.m.
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a device
has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.
10 Nov
10 Nov
7:12 a.m.
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a device
has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
7:37 a.m.
Hi Peter,
Sounds like good approach. This gives great flexibility to set meta information by the
owner.
Personally I do not like the proposed name 'thingJid' for the property. I would
just put 'jid' or 'thing' for the name. 'jid' is a personal
favourite as I like consistent naming ;-)
+1 for adding 'ROOM' to the tag list!
Cheers,
Eelco
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a
device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.
12 Nov
12 Nov
1:04 a.m.
Hi Peter,
As I would like to have this documented I added the change to my fork of the XMPP-IoT
repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a
device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.
3:46 a.m.
Hello Eelco
Thanks for the input. Unfortunately, I've already done the changes. Just hadn't
time yesterday to publish the updates. I've attached them to this mail. I'll send
the update to the XSF editor today.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 12 november 2014 05:04
To: XMPP in the Internet of Things
Subject: Re: [IOT] IoT discovery (XEP-0347)
Hi Peter,
As I would like to have this documented I added the change to my fork of the XMPP-IoT
repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a
device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
19 Nov
19 Nov
12:09 a.m.
Hi Peter,
Once again thanks for changing this!
For readability and to keep the XEP short you might want to consider merging paragraphs
3.13 and 3.14 like I suggested in the pull request.
Kind regards,
Eelco
On 12 Nov 2014, at 11:46, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for the input. Unfortunately, I've already done the changes. Just hadn't
time yesterday to publish the updates. I've attached them to this mail. I'll send
the update to the XSF editor today.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 12 november 2014 05:04
To: XMPP in the Internet of Things
Subject: Re: [IOT] IoT discovery (XEP-0347)
Hi Peter,
As I would like to have this documented I added the change to my fork of the XMPP-IoT
repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a
device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
<iot-discovery.html>_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
1:15 a.m.
Cramer:
I was on the virtue of merging your changes yesterday but needed to see
that there where no collisions
can you consider doing a new pull request towards the current state. I have
uploaded the latest changes.
/Joachim
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-19 8:09 GMT+01:00 Cramer, E.R. (Eelco) <Eelco.Cramer(a)tno.nl>nl>:
Hi Peter,
Once again thanks for changing this!
For readability and to keep the XEP short you might want to consider
merging paragraphs 3.13 and 3.14 like I suggested in the pull request.
Kind regards,
Eelco
11/03/14 Internal
Virus Database is out of date.
On 12 Nov 2014, at 11:46, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for the input. Unfortunately, I've already done the changes. Just
hadn't time yesterday to publish the updates. I've attached them to this
mail. I'll send the update to the XSF editor today.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 12 november 2014 05:04
To: XMPP in the Internet of Things
Subject: Re: [IOT] IoT discovery (XEP-0347)
Hi Peter,
As I would like to have this documented I added the change to my fork of
the
XMPP-IoT repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
> On 10 Nov 2014, at 15:12, Peter Waher <Peter.Waher(a)clayster.com> wrote:
>
> Hello Eelco
>
> Thanks for your input.
>
> How about adding an optional argument (for instance thingJid) to the
<update> message? If not provided, it is assumed the Thing sends the
message. If provided, it is assumed the owner sends the message. And
allowed values only include things actually owned by the sender of the
message.
>
> Example:
>
> <iq type='set'
> from=owner(a)clayster.com/1234'
> to='discovery.clayster.com'
> id='8'>
> <update xmlns='urn:xmpp:iot:discovery'
thingJid='thing(a)clayster.com
'>
> <str name='ROOM'
value='...'/>
> <str name='APT' value='...'/>
> <str name='BLD' value='...'/>
> <str name='STREET' value='...'/>
> <str name='STREETNR' value='...'/>
> <str name='AREA' value='...'/>
> <str name='CITY' value='...'/>
> <str name='REGION' value='...'/>
> <str name='COUNTRY' value='...'/>
> </update>
> </iq>
>
> Or, if behind a concentrator:
>
> <iq type='set'
> from=owner(a)clayster.com/1234'
> to='discovery.clayster.com'
> id='8'>
> <update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
> <str name='ROOM'
value='...'/>
> <str name='APT' value='...'/>
> <str name='BLD' value='...'/>
> <str name='STREET' value='...'/>
> <str name='STREETNR' value='...'/>
> <str name='AREA' value='...'/>
> <str name='CITY' value='...'/>
> <str name='REGION' value='...'/>
> <str name='COUNTRY' value='...'/>
> </update>
> </iq>
>
> If you think this is a good idea, I can update the specification
accordingly.
>
> We can also add ROOM to the set of predefined tags.
>
> Best regards,
> Peter Waher
>
>
> -----Original Message-----
> From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
> Sent: den 10 november 2014 10:39
> To: XMPP in the Internet of Things
> Subject: [IOT] IoT discovery (XEP-0347)
>
> I’m working my way through the IoT discovery XEP.
>
> For my use case I would like to update the Meta Information in the
registry
after a device has been claimed. For example:
>
> 1. I install a Thing in a room and the Thing registeres itself in the
registry.
> 2. I claim ownership of the Thing.
> 3. I now want to update the Meta Information with information not known
by
thing itself like for example location, room number, building number etc.
>
> How should I proceed with step 3? A Thing can update its
meta-information in
the registry but an owner cannot update the
meta-information of the Thing or tell a Thing to do so as of the current
version of the spec.
>
> Any ideas?
>
> Thanks,
> Eelco
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date:
11/03/14
Internal Virus Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date:
<iot-discovery.html>_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. TNO accepts no
liability for the content of this e-mail, for the manner in which you use
it and for damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
2:58 a.m.
Hi Joachim,
Peter already included the changes I suggested in his new version. I will close the PR as
it became irrelevant.
Thanks,
Eelco
On 19 Nov 2014, at 09:15, Joachim Lindborg
<joachim.lindborg@sust.se<mailto:joachim.lindborg@sust.se>> wrote:
Cramer:
I was on the virtue of merging your changes yesterday but needed to see that there where
no collisions
can you consider doing a new pull request towards the current state. I have uploaded the
latest changes.
/Joachim
Regards
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se<http://SUST.se>
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg@sust.se<mailto:Joachim.lindborg@sust.se>
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-19 8:09 GMT+01:00 Cramer, E.R. (Eelco)
<Eelco.Cramer@tno.nl<mailto:Eelco.Cramer@tno.nl>>:
Hi Peter,
Once again thanks for changing this!
For readability and to keep the XEP short you might want to consider merging paragraphs
3.13 and 3.14 like I suggested in the pull request.
Kind regards,
Eelco
On 12 Nov 2014, at 11:46, Peter Waher
<Peter.Waher@clayster.com<mailto:Peter.Waher@clayster.com>> wrote:
Hello Eelco
Thanks for the input. Unfortunately, I've already done the changes. Just hadn't
time yesterday to publish the updates. I've attached them to this mail. I'll send
the update to the XSF editor today.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco)
[mailto:Eelco.Cramer@tno.nl<mailto:Eelco.Cramer@tno.nl>]
Sent: den 12 november 2014 05:04
To: XMPP in the Internet of Things
Subject: Re: [IOT] IoT discovery (XEP-0347)
Hi Peter,
As I would like to have this documented I added the change to my fork of the XMPP-IoT
repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.
_______________________________________________
IOT mailing list
IOT@xmpp.org<mailto:IOT@xmpp.org>
http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________
IOT mailing list
IOT@xmpp.org<mailto:IOT@xmpp.org>
http://mail.jabber.org/mailman/listinfo/iot
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher@clayster.com<mailto:Peter.Waher@clayster.com>> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the <update>
message? If not provided, it is assumed the Thing sends the message. If provided, it is
assumed the owner sends the message. And allowed values only include things actually owned
by the sender of the message.
Example:
<iq type='set'
from=owner@clayster.com/1234<http://owner@clayster.com/1234>'
to='discovery.clayster.com<http://discovery.clayster.com/>'
id='8'>
<update xmlns='urn:xmpp:iot:discovery'
thingJid='thing@clayster.com<mailto:thing@clayster.com>'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner@clayster.com/1234<http://owner@clayster.com/1234>'
to='discovery.clayster.com<http://discovery.clayster.com/>'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology'
thingJid='rack@clayster.com<mailto:rack@clayster.com>'>
<str name='ROOM' value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco)
[mailto:Eelco.Cramer@tno.nl<mailto:Eelco.Cramer@tno.nl>]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a
device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself
like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry
but an owner cannot update the meta-information of the Thing or tell a Thing to do so as
of the current version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com/>
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
_______________________________________________
IOT mailing list
IOT@xmpp.org<mailto:IOT@xmpp.org>
http://mail.jabber.org/mailman/listinfo/iot
-----
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com/>
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date: 11/03/14 Internal Virus
Database is out of date.
<iot-discovery.html>_______________________________________________
IOT mailing list
IOT@xmpp.org<mailto:IOT@xmpp.org>
http://mail.jabber.org/mailman/listinfo/iot
20 Nov
20 Nov
7:07 p.m.
Thanks
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-19 10:58 GMT+01:00 Cramer, E.R. (Eelco) <Eelco.Cramer(a)tno.nl>nl>:
Hi Joachim,
Peter already included the changes I suggested in his new version. I
will close the PR as it became irrelevant.
Thanks,
Eelco
On 19 Nov 2014, at 09:15, Joachim Lindborg <joachim.lindborg(a)sust.se>
wrote:
Cramer:
I was on the virtue of merging your changes yesterday but needed to see
that there where no collisions
can you consider doing a new pull request towards the current state. I
have uploaded the latest changes.
/Joachim
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-19 8:09 GMT+01:00 Cramer, E.R. (Eelco) <Eelco.Cramer(a)tno.nl>nl>:
Hi Peter,
Once again thanks for changing this!
For readability and to keep the XEP short you might want to consider
merging paragraphs 3.13 and 3.14 like I suggested in the pull request.
Kind regards,
Eelco
11/03/14 Internal
Virus Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
On 12 Nov 2014, at 11:46, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for the input. Unfortunately, I've already done the changes.
Just
hadn't time yesterday to publish the updates. I've attached them to
this mail. I'll send the update to the XSF editor today.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 12 november 2014 05:04
To: XMPP in the Internet of Things
Subject: Re: [IOT] IoT discovery (XEP-0347)
Hi Peter,
As I would like to have this documented I added the change to my fork
of the
XMPP-IoT repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
> On 10 Nov 2014, at 15:12, Peter Waher <Peter.Waher(a)clayster.com>
wrote:
>
> Hello Eelco
>
> Thanks for your input.
>
> How about adding an optional argument (for instance thingJid) to the
<update> message? If not provided, it is assumed the Thing sends the
message. If provided, it is assumed the owner sends the message. And
allowed values only include things actually owned by the sender of the
message.
>
> Example:
>
> <iq type='set'
> from=owner(a)clayster.com/1234'
> to='discovery.clayster.com'
> id='8'>
> <update xmlns='urn:xmpp:iot:discovery' thingJid='
thing(a)clayster.com'>
> <str name='ROOM'
value='...'/>
> <str name='APT' value='...'/>
> <str name='BLD' value='...'/>
> <str name='STREET' value='...'/>
> <str name='STREETNR' value='...'/>
> <str name='AREA' value='...'/>
> <str name='CITY' value='...'/>
> <str name='REGION' value='...'/>
> <str name='COUNTRY' value='...'/>
> </update>
> </iq>
>
> Or, if behind a concentrator:
>
> <iq type='set'
> from=owner(a)clayster.com/1234'
> to='discovery.clayster.com'
> id='8'>
> <update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
> <str name='ROOM'
value='...'/>
> <str name='APT' value='...'/>
> <str name='BLD' value='...'/>
> <str name='STREET' value='...'/>
> <str name='STREETNR' value='...'/>
> <str name='AREA' value='...'/>
> <str name='CITY' value='...'/>
> <str name='REGION' value='...'/>
> <str name='COUNTRY' value='...'/>
> </update>
> </iq>
>
> If you think this is a good idea, I can update the specification
accordingly.
>
> We can also add ROOM to the set of predefined tags.
>
> Best regards,
> Peter Waher
>
>
> -----Original Message-----
> From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
> Sent: den 10 november 2014 10:39
> To: XMPP in the Internet of Things
> Subject: [IOT] IoT discovery (XEP-0347)
>
> I’m working my way through the IoT discovery XEP.
>
> For my use case I would like to update the Meta Information in the
registry
after a device has been claimed. For example:
>
> 1. I install a Thing in a room and the Thing registeres itself in the
registry.
> 2. I claim ownership of the Thing.
> 3. I now want to update the Meta Information with information not
known by
thing itself like for example location, room number, building
number etc.
>
> How should I proceed with step 3? A Thing can update its
meta-information in
the registry but an owner cannot update the
meta-information of the Thing or tell a Thing to do so as of the current
version of the spec.
>
> Any ideas?
>
> Thanks,
> Eelco
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date:
11/03/14
Internal Virus Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date:
<iot-discovery.html>_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. TNO accepts no
liability for the content of this e-mail, for the manner in which you use
it and for damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
12 Nov
12 Nov
9:44 a.m.
Thanks for the update I will incorporate the changes to the github.
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-12 9:04 GMT+01:00 Cramer, E.R. (Eelco) <Eelco.Cramer(a)tno.nl>nl>:
Hi Peter,
As I would like to have this documented I added the change to my fork of
the XMPP-IoT repository and created a pull request.
https://github.com/joachimlindborg/XMPP-IoT/pull/7
Best regards,
Eelco
On 10 Nov 2014, at 15:12, Peter Waher
<Peter.Waher(a)clayster.com> wrote:
Hello Eelco
Thanks for your input.
How about adding an optional argument (for instance thingJid) to the
<update> message? If not provided, it is assumed the Thing sends the
message. If provided, it is assumed the owner sends the message. And
allowed values only include things actually owned by the sender of the
message.
Example:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' thingJid='thing(a)clayster.com
'>
<str name='ROOM'
value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
Or, if behind a concentrator:
<iq type='set'
from=owner(a)clayster.com/1234'
to='discovery.clayster.com'
id='8'>
<update xmlns='urn:xmpp:iot:discovery' nodeId='imc1'
sourceId='MeteringTopology' thingJid='rack(a)clayster.com'>
<str name='ROOM'
value='...'/>
<str name='APT' value='...'/>
<str name='BLD' value='...'/>
<str name='STREET' value='...'/>
<str name='STREETNR' value='...'/>
<str name='AREA' value='...'/>
<str name='CITY' value='...'/>
<str name='REGION' value='...'/>
<str name='COUNTRY' value='...'/>
</update>
</iq>
If you think this is a good idea, I can update the specification
accordingly.
We can also add ROOM to the set of predefined tags.
Best regards,
Peter Waher
-----Original Message-----
From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 10 november 2014 10:39
To: XMPP in the Internet of Things
Subject: [IOT] IoT discovery (XEP-0347)
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the
registry after
a device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the
registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known
by thing
itself like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its
meta-information in the
registry but an owner cannot update the
meta-information of the Thing or tell a Thing to do so as of the current
version of the spec.
Any ideas?
Thanks,
Eelco
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4189/8501 - Release Date:
11/03/14 Internal
Virus Database is out of date.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. TNO accepts no
liability for the content of this e-mail, for the manner in which you use
it and for damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot
3587
days inactive
3598
days old
9 comments
3 participants
participants (3)
-
Cramer, E.R. (Eelco) -
Joachim Lindborg -
Peter Waher