[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: BSC 1.4. Where art thou
------=_NextPart_000_012A_01CAC39C.F0B022B0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hi Kevin,
I still think we need a common area, not spread out over numerous emails
over a huge time frame, for the points I have raised.
> Where can we pass comment on the proposed changes/updates?
>
> Where can we contribute our ideas towards a new version?
>
The best place to discuss is right here :-) - Discuss yes,
>
> Given that it is an open source protocol, shouldn't the above areas be
made available?
>
Discuss yes, formally document no. It showed be in a displayed place.
Sorry but the below sounds like a government that knows what's best for the
people without even asking what the people want.
>One thing we have learned is that when you have a dozen independent
contributors to a specification , all with differing views and
even different languages and timezones then getting consensus is
incredibly difficult and causes months of delays. This is part of the
contributory issue with the xAP v1.3 specification delay and it is
likely that we will drop several intended features simply because we can
not formalise them in a timely or agreed way. I do agree that the
formal xAP v1.3 spec if lamentably overdue but we also then don't want
to supercede it with a 1.4 version a few months later.
What were the intended features? Where do I find this information?
If you aren't actively taking part in the discussion and only putting in a
view very few months, then you can't expect your views to be included in
the
specification.
But surely it must be open for discussion by the people that use it.
I'm trying to utilize this Protocol into the hardware of two different
business's and take this into other huge world wide areas "Model
Trains",
which probably a larger user base than home automation.
Hence my great interest in this protocol.
As an embedded developer, I want to give the best possible products and
solutions to my customers.
Thus my keen interest in this group.
Regards,
Neil Wrightson.
N.W.Electronics
ABN 76 768 513 867
Embedded Controllers and Home Automation Products
Skype : Neil_Wrightson
Web : www.nwe.net.au
_____
From: xAP_developer@xxxxxxx [mailto:xAP_developer@xxxxxxx]
On Behalf Of Kevin Hawkins
Sent: Sunday, 14 March 2010 12:40 AM
To: xAP_developer@xxxxxxx
Subject: Re: [xAP_developer] BSC 1.4. Where art thou
On 13/03/2010 09:16, nwemail27 wrote:
> Hi,
>
> So what is the status on BSC Ver 1.4?
>
I am not aware of any formal intention to release a BSC v1.4 . xAP
BSC v 1.3 is current and seems to work really well. There is however
the need to update the current spec when xAP v1.3 is formalised - but
that only relates to allowing the UID format to be increased regarding
the number of supported digits. This has been well discussed on this
list but should really be rolled into a BSC v1.3a update .
BSC was designed to be exactly that - Basic and Simple - and it
accomplishes that pretty well. There is great reluctance to complicate
the schema specification with any extra functionality although there are
a couple of unofficial adaptions eg the BSC 'choice' device for
selecting from several presets like PlayPauseFFREWStop that might
be candidates. Whatever might be added we must ensure it is fully
backward compatible with the existing BSC.
>
> Where is it being discussed?
>
> Where can we pass comment on the proposed changes/updates?
>
> Where can we contribute our ideas towards a new version?
>
The best place to discuss is right here :-)
>
> Given that it is an open source protocol, shouldn't the above areas be
made available?
>
One thing we have learned is that when you have a dozen independent
contributors to a specification , all with differing views and
even different languages and timezones then getting consensus is
incredibly difficult and causes months of delays. This is part of the
contributory issue with the xAP v1.3 specification delay and it is
likely that we will drop several intended features simply because we can
not formalise them in a timely or agreed way. I do agree that the
formal xAP v1.3 spec if lamentably overdue but we also then don't want
to supercede it with a 1.4 version a few months later.
> Being an embedded developer, I for one would like to see some standard
watchdog components being implemented.
>
Make a proposal here and see how it goes - ensure it is backwards
compatible - you can always create your own schema and propose it be
rolled into another one officially. That's a pretty 'open' approach.
K
> Regards,
>
> Neil Wrightson.
> N.W.Electronics
> ABN 76 768 513 867
> Embedded Controllers and Home Automation Products
> Skype : Neil_Wrightson
> Web : www.nwe.net.au
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
------=_NextPart_000_012A_01CAC39C.F0B022B0
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii"
http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML
8.00.6001.18876"></HEAD>
<BODY style="BACKGROUND-COLOR: #fff">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<DIV dir=ltr align=left><SPAN class=421051806-14032010><FONT
color=#0000ff
size=2 face=Arial>Hi Kevin,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=421051806-14032010><FONT
color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=421051806-14032010><FONT
color=#0000ff
size=2 face=Arial>I still think we need a common area, not spread out
over
numerous emails over a huge time frame, for the points I have
raised.</FONT></SPAN></DIV>
<DIV><BR>> Where can we pass comment on the proposed
changes/updates?<BR>><BR>> Where can we
contribute our ideas towards a new
version?<BR>> <BR>The best place to discuss is right
here :-)<SPAN
class=421051806-14032010> - Discuss yes,
</SPAN><BR>><BR>> Given that it
is an open source protocol, shouldn't the above areas be made
available?<BR>>
<BR></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>Discuss yes, formally document no. It showed be
in a
displayed place.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2
face=Arial></FONT> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>Sorry
but the below sounds like a government that knows what's best for the
people
without even asking what the people
want.</SPAN></FONT></DIV>
<DIV><SPAN class=421051806-14032010>>One thing we have
learned is that when
you have a dozen independent <BR>contributors to a specification ,
all with
differing views and <BR>even different languages and timezones then
getting
consensus is <BR>incredibly difficult and causes months of delays.
This is part
of the <BR>contributory issue with the xAP v1.3 specification delay
and it is
<BR>likely that we will drop several intended features simply because
we can
<BR>not formalise them in a timely or agreed way. I do agree that the
<BR>formal
xAP v1.3 spec if lamentably overdue but we also then don't want
<BR>to supercede
it with a 1.4 version a few months
later.<BR></SPAN></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>What
were the intended features? Where do I find this
information?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>If you
aren't actively taking part in the discussion and only putting in a view
very
few months, then you can't expect your views to be included in the
specification.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>But
surely it must be open for discussion by the people that use
it.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>I'm
trying to utilize this Protocol into the hardware of two different
business's
and take this into other huge world wide areas "Model Trains",
which probably a
larger user base than home
automation.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>Hence
my great interest in this protocol.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>As an
embedded developer, I want to give the best possible products and solutions
to
my customers.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=421051806-14032010>Thus
my keen interest in this group.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2
face=Arial></FONT> </DIV>
<DIV class=Section1>
<P><SPAN style="FONT-FAMILY: Arial; FONT-SIZE:
10pt">Regards,</SPAN> </P>
<P><B><SPAN style="FONT-SIZE: 13.5pt">Neil
Wrightson.</SPAN></B> <BR><B><I><SPAN
style="FONT-SIZE:
13.5pt">N.W.Electronics</SPAN></I></B>
<BR><SPAN
style="FONT-SIZE: 10pt">ABN 76 768 513 867</SPAN>
<BR><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Embedded
Controllers and Home
Automation Products</SPAN> <BR>Skype : <SPAN
class=SpellE>Neil_Wrightson</SPAN>
<BR><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE:
10pt">Web
:</SPAN><U> <SPAN style="COLOR:
blue">www.nwe.net.au</SPAN></U> </P></DIV>
<DIV><FONT color=#0000ff size=2
face=Arial></FONT> </DIV><U><FONT
color=#0000ff></FONT></U><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT:
5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B>
xAP_developer@xxxxxxx
[mailto:xAP_developer@xxxxxxx]
<B>On Behalf Of </B>Kevin
Hawkins<BR><B>Sent:</B> Sunday, 14 March 2010 12:40
AM<BR><B>To:</B>
xAP_developer@xxxxxxx<BR><B>Subject:</B> Re:
[xAP_developer] BSC 1.4.
Where art thou<BR></FONT><BR></DIV>
<DIV></DIV><SPAN style="DISPLAY:
none"> </SPAN>
<DIV id=ygrp-text>
<P>On 13/03/2010 09:16, nwemail27 wrote:<BR>>
Hi,<BR>><BR>> So what
is the status on BSC Ver 1.4?<BR>> <BR>I am not aware of
any formal
intention to release a BSC v1.4 . xAP <BR>BSC v 1.3 is current and
seems to
work really well. There is however <BR>the need to update the current
spec
when xAP v1.3 is formalised - but <BR>that only relates to allowing
the UID
format to be increased regarding <BR>the number of supported digits.
This has
been well discussed on this <BR>list but should really be rolled into
a BSC
v1.3a update .<BR><BR>BSC was designed to be exactly that -
Basic and Simple -
and it <BR>accomplishes that pretty well. There is great reluctance
to
complicate <BR>the schema specification with any extra functionality
although
there are <BR>a couple of unofficial adaptions eg the BSC 'choice'
device for
<BR>selecting from several presets like PlayPauseFF<WBR>REWStop
that might
<BR>be candidates. Whatever might be added we must ensure it is fully
<BR>backward compatible with the existing
BSC.<BR>><BR>> Where is it
being discussed?<BR>><BR>> Where can we pass
comment on the proposed
changes/updates?<BR>><BR>> Where can we
contribute our ideas towards a
new version?<BR>> <BR>The best place to discuss is right
here
:-)<BR>><BR>> Given that it is an open source
protocol, shouldn't the
above areas be made available?<BR>> <BR>One thing we
have learned is that
when you have a dozen independent <BR>contributors to a specification
, all
with differing views and <BR>even different languages and timezones
then
getting consensus is <BR>incredibly difficult and causes months of
delays.
This is part of the <BR>contributory issue with the xAP v1.3
specification
delay and it is <BR>likely that we will drop several intended
features simply
because we can <BR>not formalise them in a timely or agreed way. I do
agree
that the <BR>formal xAP v1.3 spec if lamentably overdue but we also
then don't
want <BR>to supercede it with a 1.4 version a few months
later.<BR>> Being
an embedded developer, I for one would like to see some standard watchdog
components being implemented.<BR>> <BR><BR>Make a
proposal here and see how
it goes - ensure it is backwards <BR>compatible - you can always
create your
own schema and propose it be <BR>rolled into another one officially.
That's a
pretty 'open' approach.<BR><BR>K<BR>>
Regards,<BR>><BR>> Neil
Wrightson.<BR>> N.W.Electronics<BR>> ABN 76 768
513 867<BR>> Embedded
Controllers and Home Automation Products<BR>> Skype :
Neil_Wrightson<BR>> Web :
www.nwe.net.<WBR>au<BR>><BR>><BR>><BR>><BR>>
------------<WBR>---------<WBR>---------<WBR>------<BR>><BR>>
Yahoo!
Groups
Links<BR>><BR>><BR>><BR>><BR>>
<BR><BR></P></DIV><!-- end group email -->
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=2089/stime=1268548624";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xAP_developer/join;_ylc=X3oDMTJmdWhtbG4zBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNjg1NDg2MjQ-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkZmNrMG1nBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjY4NTQ4NjI0";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</BODY></HTML>
------=_NextPart_000_012A_01CAC39C.F0B022B0--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|