RE: Providing policy around messages (was Re: Feedback from UHKA 2003)

[Kevin Hawkins]

Does anyone have any feedback on these outline topics below - are they all
that we want to discuss ? Are there any we want to skip ? If not I'll
create
the separate threads later today and I hope that we can have some informed
opinion and interesting ideas to thrash through over the next week or so.

Kevin

> -----Original Message-----
> From: Kevin Hawkins [mailto:<a
href="/group/xAP_developer/post?postID=omOh6lKqTvIKC2BiQdnvts7OhenMs4T0V1dHYtUw1-XGwguUWTzycVk_ycWs79eS-RMHkEdT6ikGVXM1a6j_8NsJ">lists@u...</a>]
> Sent: 21 May 2003 13:54
> To: <a
href="/group/xAP_developer/post?postID=QZlcpHox-jqktZNknuWQ4pEw1Cbq20j8vkup1K6Dlgv7HHv8bcqc3VkPvwEfg9kH9MagN_p6LQB0s5yZ56WCeyzh-b0">xAP_developer@xxxxxxx</a>
> Subject: [xAP_developer] Providing policy around messages (was Re:
> Feedback from UHKA 2003)
>
> I want to try and agree on some of the policies that we need on
> top
> of the lower level xAP message protocol that will allow easy
> incorporation
> of a device type model for a xAPp within a hardware or software
> controller
> type device. This will facilitate software and hardware developers
> wishing
> to support xAP to proceed easily with a base implementation that will
> work
> internally with their state models. ( Harmony, Autom8it, HomeBrain,
> Ace,
> Homeseer etc). It will also allow a much easier xAP connector to be
> written
> for HomeVision.
>
> There are a number of things that come from this that we need to
> discuss and I think it's best if we divide the areas into their own
> separate
> threads and then thrash them through here on the xAP developer list.
>
> Here are some of the topics. There are no doubt a few more -
> could
> you comment on this and then I shall start threads on each of the
> topics we
> agree.
>
> Topic 1: A base level 'Status' schema that provides for minimalist
> essential state reporting for the typical devices that are prevalent
> today
> in the HA world. ON OFF LEVEL etc
>
> Topic 2: Discussion around inheritance of classes - for example if
> the above Class was defined as XAPSTATUS then should xAPStatus.C-Bus
> inherit
> from xAPSTATUS and further should xAPStatus.C-Bus.Lighting enforce the
> inheritance from the C-Bus class.
>
> Topic 3: The importation of Class/Schema templates into xAP and
> their
> repository. Includes XSLT XML ideas.
>
> Topic 4: The point to point acknowledgement policy that we need to
> provide to ensure delivery / reception of xAP critical data - this
> discussion to incorporate sequencing.
>
> Topic 5: Suggestion that all devices must support targeting within
> the spec (change from optional to mandatory)
>
>
> I think all these issues are related and need to have concurrent
> discussion
> - there are also the following pending topics from earlier discussion
> that
> we need to address so I have listed them here for completeness - some
> of
> them have are entwined with the above.
>
> TOPIC: Targetting based on UID. Contentious I know.
>
> TOPIC: Wildcarding of UID
>
> TOPIC: Event based addressing (Patrick)
>
> TOPIC: Discovery and Configuration
>
> TOPIC: Groups and Scenes
>
> I also note that we have a large number of members (58) of the
> general xAP list (which is very quiet)and (19) on this list - whilst I
> don't
> want to create an unmanageable free for all there are some people
there
> that
> have valued opinions. Either we should solicit their input or announce
> our
> intentions on that list.I assume this list is restricted to members
who
> are
> actively developing xAP applications.
>
> Kevin
>
>
> ------------------------ Yahoo! Groups Sponsor
---------------------~--
> >
> Get A Free Psychic Reading! Your Online Answer To Life's Important
> Questions.
> <a href="http://us.click.yahoo.com/Lj3uPC/Me7FAA/uetFAA/dpFolB/TM";>http://us.click.yahoo.com/Lj3uPC/Me7FAA/uetFAA/dpFolB/TM</a>
>
---------------------------------------------------------------------~-
> >
>
> To unsubscribe from this group, send an email to:
> <a
href="/group/xAP_developer/post?postID=ZKNb8JViRdyPT55vxxxK1wMV_nye1WVALaqSyfIzGE4W1Zy9GHs5WqrOOvbdB31ji9OM6G8Pmi0VXsxvikDhyU8GYoiGw_5cL5qKcTouUfeD7bed">xAP_developer-unsubscribe@xxxxxxx</a>
>
>
>
> Your use of Yahoo! Groups is subject to
> <a href="http://docs.yahoo.com/info/terms/";>http://docs.yahoo.com/info/terms/</a>