[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Consensus on BSC temperature reporting?
--------------060907070106010909000503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Gregg,
My view FWIW is that it should be text=20C or text=68F (or, for the
physicists, text=293K).
Where greater accuracy is required then text=20.55C, etc. These are all
easy to parse.
Patrick's website lists the temp.reading class but that doesn't have the
units info.
The DIY Zoning sourceforge project xAP support uses another class,
dz.dac, and uses
centigrade/celsius.
I'm with you, time for a common class for environmental monitoring -
temp, humidity,
light, pressure, current, voltage, etc?
Lehane
Gregg Liming wrote:
>
> After having searched this list for methods for temperature reporting
> w/i BSC, I'm having difficulty determining a consensus. It seems that
> while there is a consensus on putting the temperature value in the
text
> field, a standard practice for units and scale are missing. In most
> cases, "degrees" for units seems implied (although, I've
noted at least
> one exception) and then the first letter of the scale is appended. Is
> this accurate? Does case matter? Can spaces exist between the value
> and "scale letter"?
>
> I realize that the "beauty" of BSC is informality, but my
preference
> would be to drive to a consensus. Or, would adopting some other schema
> for temperature reporting be better altogether (i.e., is this trying
to
> make BSC do too much)?
>
> Gregg
>
>
>
------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.11.6/430 - Release Date:
28/08/2006
>
--------------060907070106010909000503
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Gregg,<br>
My view FWIW is that it should be text=20C or text=68F (or, for the
physicists, text=293K).<br>
Where greater accuracy is required then text=20.55C, etc. These are all
easy to parse.<br>
<br>
Patrick's website lists the temp.reading class but that doesn't have
the units info.<br>
<br>
The DIY Zoning sourceforge project xAP support uses another class,
dz.dac, and uses<br>
centigrade/celsius.<br>
<br>
I'm with you, time for a common class for environmental monitoring -
temp, humidity,<br>
light, pressure, current, voltage, etc?<br>
<br>
Lehane<br>
<br>
<br>
<br>
Gregg Liming wrote:
<blockquote cite="mid44F437CF.4070002@xxxxxxx"
type="cite"><!-- Network content -->
<div id="ygrp-text">
<p>After having searched this list for methods for temperature
reporting<br>
w/i BSC, I'm having difficulty determining a consensus. It seems
that<br>
while there is a consensus on putting the temperature value in the
text<br>
field, a standard practice for units and scale are missing. In
most<br>
cases, "degrees" for units seems implied (although, I've noted at
least<br>
one exception) and then the first letter of the scale is appended.
Is<br>
this accurate? Does case matter? Can spaces exist between the
value<br>
and "scale letter"?<br>
<br>
I realize that the "beauty" of BSC is informality, but my
preference<br>
would be to drive to a consensus. Or, would adopting some other
schema<br>
for temperature reporting be better altogether (i.e., is this trying
to<br>
make BSC do too much)?<br>
<br>
Gregg<br>
</p>
</div>
<!--End group email -->
<pre wrap="">
<hr size="4" width="90%">
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.6/430 - Release Date: 28/08/2006
</pre>
</blockquote>
<br>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590&grpId=9674343&grpspId=1600007709&msgId=2976&stime=1156860552";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br><br>
<div style="width:500px; text-align:right; margin-bottom:1px;
color:#909090;">
<tt>SPONSORED LINKS</tt>
</div>
<table bgcolor=#e0ecee cellspacing="13"
cellpadding="0" width=500px>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjZXExaWRyBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTY4NjA1NTI-?t=ms&k=X10+home+automation&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=tN49yZ8gLW44qGV8ngn-6Q";>X10
home automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjamY0M3JzBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTY4NjA1NTI-?t=ms&k=Home+automation&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=uxodCh5B-C-LfzJs4AF_uw";>Home
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjb3RraTI1BF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTY4NjA1NTI-?t=ms&k=Home+automation+product&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=-7-yoKCdmzYOn0eQU41W8Q";>Home
automation product</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjNzBpcWU3BF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTY4NjA1NTI-?t=ms&k=Home+automation+system&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=YiCpy6REMq-ZQ9BflM6GVg";>Home
automation system</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads;_ylc=X3oDMTJjZW9iMm9pBF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTY4NjA1NTI-?t=ms&k=Home+automation+security&w1=X10+home+automation&w2=Home+automation&w3=Home+automation+product&w4=Home+automation+system&w5=Home+automation+security&c=5&s=133&g=0&.sig=MqsbZg2eMmjgfWfWU0yLgQ";>Home
automation security</a></tt>
</td>
</tr>
</table>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
<tt>YAHOO! GROUPS LINKS</tt>
</div>
<br>
<ul>
<tt><li type=square> Visit your group "<a
href="http://groups.yahoo.com/group/xap_automation";>xap_automation</a>"
on the web.<br> </tt>
<tt><li type=square> To unsubscribe from this group,
send an email to:<br> <a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>xap_automation-unsubscribe@xxxxxxx</a><br> </tt>
<tt><li type=square> Your use of Yahoo! Groups is
subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.</tt>
</ul>
<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</body>
</html>
--------------060907070106010909000503--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|