Re: Proposal / RFC: Change xAP wire format

["patricklidstone" <patrick@xxxxxxxxxxxx>]

I appreciate the need to evangelise, and the resources/time such
activity requires - especially when it has to be done for love and there is
no commercial/financial support, but as I scratch my own itch, I'd much
rather be doing so against a standard implementation than a fork.

Perhaps now would be a good time to open a consultation period for changes,
and work out a mechanism for how those changes would be accepted (voting,
committee, something else?). I'd very much like to see xAP v.++ with JSON
incorporated into it...

P.

--- In xAP_developer@xxxxxxx, Kevin Hawkins <yahoogroupskh@...>
wrote:
>
> I'm fairly enthused with using JSON too,  I've been using it a little
in
> xAP Flash and now in the iViewer xAP implementation.  It would seem a
> good fit for xAP.
>
> However  I feel there are many other aspects of moving xAP forward
that
> we need to address, mostly time and commitment related in order to get
> resources and visibility out there.  I am not sure we have that
> capability at the moment.
>
> There are certainly aspects of BSC that we could improve,  a classic
> example is how to represent negative values e.g.  temperature for
> example.   I have posted quite a bit both on and off list with people
> about this, including Daniel, about what we might do here.   There are
a
> few unofficial BSC enhancements that are in fairly widespread use
> (choice devices and level offsets for example) but no official BSC2.
> TSC I feel is not ready yet for adoption and I know of no TSC aware
> applications.
>
> BSC is the most widely adopted schema in the xAP world today and is as
> near to plug and play as we're likely to get.  IMHO it is the best
> schema that we have introduced and has helped xAP adoption
considerably.
>    Almost every commercial HA software application supports it either
> inbuilt or via plugins.  However this prevalence has meant that many
> people try and squeeze every xAP implementation into BSC and hence
> breach it's purpose and capabilities.
>
>    Cheers Kevin
>
> On 07/07/2011 11:19, patricklidstone wrote:
> >
> > --- In xAP_developer@xxxxxxx, "Daniel
Berenguer"<dberenguer@>  wrote:
> >>> What additional capabilities would you like to see in the
'upper' xAP layer?
> >> Not really related to your post. I simply think that having a
good schema for M2M apps would be a plus for new adopters. BSC and TSC have
serious limitations IMO:
> >> http://tech.groups.yahoo.com/group/xAP_developer/message/2120
> >>
> >> If we ever do the jump to the JSON adoption, we may return to
the topic.
> >>
> > I have to confess to being a bit of a BSC luddite - most of my
stuff predates BSC, and I haven't found an opportunity to use it in anger
yet, so I don't really feel informed enough to comment on your post.
> >
> > I'd be interested to hear others' opinions on JSON. I really do
find the arguments compelling!
> >
> > P.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>




------------------------------------