[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
RE: Re: version 1.3 of xAP documents
--_000_825EDC0C3291C943B30B9F79E82009410104304406sdsmtex07_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thanks for the heads up.. That does simplify things.
Steve
From: xAP_developer@xxxxxxx [mailto:xAP_developer@xxxxxxx] =
On Behalf Of Kevin Hawkins
Sent: Monday, May 18, 2009 4:50 AM
To: xAP_developer@xxxxxxx
Subject: Re: [xAP_developer] Re: version 1.3 of xAP documents
Steve, one more thing I forgot to mention....
xAP v1.2 supported target=3D lines within the body(ies) of messages -
effectively allowing the various body sections within a single message
to be addressed to different devices. This AFAIK has never been used by
any applications and is awkward to implement as there are then two
target filters in use. Nor do I know of any listener application that
correctly handled it either. ......
So... from xAP v1.3 this feature is now deprecated.
K
stevejbauer wrote:
> Thanks... That's what I have been looking for!
>
> Steve
>
> --- In xAP_developer@xxxxxxx<mailto:xAP_developer%40yahoogroups.c=
om>, Kevin Hawkins <yahoogroupskh@...> wrote:
>
>> Hi Steven,
>>
>> There's a formal spec, plus a rewrite of the v1.2 spec imminent.
>> It's been delayed due to some aspects of the specification that
haven't
>> been finalised and so will now be deferred to a future v1.4 (not
>> anytime soon). The deferred aspects are not impacting typical
usage but
>> are desireable for some more demanding applications and include
long
>> messages, message continuations, sequencing, acknowledges,
>> re-transmissions, authentication, security, discovery and
configuration
>> aspects. These are essentially impemented using a higher protocol
layer
>> sitting on top of the v1.3 protocol and so will be totally
backward
>> compatible. There are outline proposals for many of these allowing
for
>> experimentation within xAP v1.3.
>>
>> The aspects that have been finalised for v1.3 include various
header
>> and body flexibility changes - which are backwards compatible with
v1.2.
>> The v1.3 UID format change however is mostly compatible in that it
is
>> transparent to nearly every existing xAP application except those
using
>> the xAP BSC or TSC schema which might need updating. Most affected
>> applications have already been updated . A xAP v1.3 application
must
>> support existing v1.2 messages and UID formats transparently so
that
>> ensures forward compatibility.
>>
>> Re the UID it has been changed from the v1.2 fixed length NNAAAASS
>> format to NN.AAAA:SS in v1.3.
>> ie a '.' and ':' delimiting the three segments has been added
which
>> now allows any of these segments to be any (even) length of
uppercase
>> hex digits.
>> The main reason for this was to allow expansion of the sub address
>> field SS from the v1.2 two hex digits to longer as many
applications
>> required.
>> In all segments values of all 0's or all F's are reserved or have
>> special meaning.
>>
>> NN - network number - usually the special all F's representing the
>> local network
>> AA - application/device ID (unique on the network)
>> SS - sub address (if the application or device implements multiple
>> endpoints) . All 0's represents the application itself rather than
an
>> endpoint within it.
>>
>> Having previously said that any even number of characters is now
>> permissable in any segment there are some recommended formats that
>> suffice for most needs.
>> NN usually always two characters
>> AAAA usually four, six or rarely eight characters
>> SS usually two, four, six or eight characters - although some
>> implementations have used longer sub addresses..(eg 1-wire 64bit
16chars=
)
>> All leading 0's must be included to maintain consistent segment
length
>> for the application
>>
>> A v1.2 UID of FF1234A2 is directly equivalent to a v1.3 UID of
FF.1234:A=
2
>>
>> Examples of v1.3 UID's:
>>
>> UID=3DFF.1234:00A6
>> UID=3DFF.AB34:67A203
>> UID=3DFF.000032:5C
>>
>> There are ramifications to the xAPBSC v1.3 Basic Status and
Control
>> schema (and xAPTSC) but these are self evident I hope as you read
the
>> specification.
>>
>> Any questions .. ask away....
>>
>> Cheers Kevin
>>
>>
>> Bauer, Steven J. wrote:
>>
>>> Is there anyplace where a person can find (even the draft
spec) of the
>>> version 1.3 xAP?? I would like to support the extended uid
correctly
>>> in the programs that I am writing?
>>>
>>> Thanks!
>>>
>>> Steve Bauer
>>>
>>>
>>>
>>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
--_000_825EDC0C3291C943B30B9F79E82009410104304406sdsmtex07_
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>
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:p="urn:schemas-microsoft-com:office:powerpoint"
xmlns:a="urn:schemas-microsoft-com:office:access"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset"
xmlns:z="#RowsetSchema"
xmlns:b="urn:schemas-microsoft-com:office:publisher"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet"
xmlns:odc="urn:schemas-microsoft-com:office:odc"
xmlns:oa="urn:schemas-microsoft-com:office:activation"
xmlns:html="http://www.w3.org/TR/REC-html40";
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:rtc="http://microsoft.com/officenet/conferencing";
xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/";
xmlns:mt="http://schemas.m
icrosoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml";
xmlns:ppda="http://www.passport.com/NameSpace.xsd";
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/";
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/";
xmlns:ds="http://www.w3.org/2000/09/xmldsig#";
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp";
xmlns:udc="htt
p://schemas.microsoft.com/data/udc"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/";
xmlns:ec="http://www.w3.org/2001/04/xmlenc#";
xmlns:sp="http://schemas.microsoft.com/sharepoint/";
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:udcs="http://schemas.microsoft.com/data/u
dc/soap"; xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile";
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart";
xmlns:wf="http://schemas.microsoft.com/sharepoin
t/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup";
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig";
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature";
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006";
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml";
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/re
lationships"; xmlns:spwp="http://microsoft.com/sharepoint/webpartpages";
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types";
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages";
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/";
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService";
xmlns:Z="urn:schemas-microsoft-com:"
xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.left
{mso-style-name:left;}
span.bld
{mso-style-name:bld;}
p.ad, li.ad, div.ad
{mso-style-name:ad;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad3, li.ad3, div.ad3
{mso-style-name:ad3;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts
{mso-style-name:yshortcuts;}
p.ad4, li.ad4, div.ad4
{mso-style-name:ad4;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad5, li.ad5, div.ad5
{mso-style-name:ad5;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad6, li.ad6, div.ad6
{mso-style-name:ad6;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts1
{mso-style-name:yshortcuts1;
font-family:"Verdana","sans-serif";
font-weight:bold;}
span.yshortcuts2
{mso-style-name:yshortcuts2;
font-family:"Verdana","sans-serif";
font-weight:normal;}
span.EmailStyle35
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:700321996;
mso-list-template-ids:1039720250;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<div class=Section1>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for the heads up.. That does simplify
things.<o:p></o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Steve<o:p></o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in
0in 0in'>
<p class=MsoNormal><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
xAP_developer@xxxxxxx [mailto:xAP_developer@xxxxxxx]
<b>On
Behalf Of </b>Kevin Hawkins<br>
<b>Sent:</b> Monday, May 18, 2009 4:50 AM<br>
<b>To:</b> xAP_developer@xxxxxxx<br>
<b>Subject:</b> Re: [xAP_developer] Re: version 1.3 of xAP
documents<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<p class=MsoNormal><br>
<br>
<br>
<o:p></o:p></p>
<p style='margin-bottom:12.0pt'>Steve, one more thing I forgot to
mention....<br>
<br>
xAP v1.2 supported target= lines within the body(ies) of messages -
<br>
effectively allowing the various body sections within a single message
<br>
to be addressed to different devices. This AFAIK has never been used by
<br>
any applications and is awkward to implement as there are then two
<br>
target filters in use. Nor do I know of any listener application that
<br>
correctly handled it either. ......<br>
<br>
So... from xAP v1.3 this feature is now deprecated.<br>
<br>
K<br>
<br>
stevejbauer wrote:<br>
> Thanks... That's what I have been looking for!<br>
><br>
> Steve<br>
><br>
> --- In <a href="mailto:xAP_developer%40yahoogroups.com";>xAP_developer@xxxxxxx</a>,
Kevin Hawkins <yahoogroupskh@...> wrote:<br>
> <br>
>> Hi Steven,<br>
>><br>
>> There's a formal spec, plus a rewrite of the v1.2 spec
imminent. <br>
>> It's been delayed due to some aspects of the specification
that
haven't <br>
>> been finalised and so will now be deferred to a future
v1.4 (not <br>
>> anytime soon). The deferred aspects are not impacting
typical usage
but <br>
>> are desireable for some more demanding applications and
include long <br>
>> messages, message continuations, sequencing, acknowledges,
<br>
>> re-transmissions, authentication, security, discovery and
configuration <br>
>> aspects. These are essentially impemented using a higher
protocol
layer <br>
>> sitting on top of the v1.3 protocol and so will be totally
backward <br>
>> compatible. There are outline proposals for many of these
allowing for
<br>
>> experimentation within xAP v1.3.<br>
>><br>
>> The aspects that have been finalised for v1.3 include
various header <br>
>> and body flexibility changes - which are backwards
compatible with
v1.2. <br>
>> The v1.3 UID format change however is mostly compatible in
that it is <br>
>> transparent to nearly every existing xAP application
except those
using <br>
>> the xAP BSC or TSC schema which might need updating. Most
affected <br>
>> applications have already been updated . A xAP v1.3
application must <br>
>> support existing v1.2 messages and UID formats
transparently so that <br>
>> ensures forward compatibility.<br>
>><br>
>> Re the UID it has been changed from the v1.2 fixed length
NNAAAASS <br>
>> format to NN.AAAA:SS in v1.3. <br>
>> ie a '.' and ':' delimiting the three segments has been
added which <br>
>> now allows any of these segments to be any (even) length
of uppercase <br>
>> hex digits.<br>
>> The main reason for this was to allow expansion of the sub
address <br>
>> field SS from the v1.2 two hex digits to longer as many
applications <br>
>> required.<br>
>> In all segments values of all 0's or all F's are reserved
or have <br>
>> special meaning.<br>
>><br>
>> NN - network number - usually the special all F's
representing the <br>
>> local network<br>
>> AA - application/device ID (unique on the
network)<br>
>> SS - sub address (if the application or device implements
multiple <br>
>> endpoints) . All 0's represents the application itself
rather than an <br>
>> endpoint within it.<br>
>><br>
>> Having previously said that any even number of characters
is now <br>
>> permissable in any segment there are some recommended
formats that <br>
>> suffice for most needs. <br>
>> NN usually always two characters <br>
>> AAAA usually four, six or rarely eight
characters<br>
>> SS usually two, four, six or eight characters - although
some <br>
>> implementations have used longer sub addresses..(eg 1-wire
64bit
16chars)<br>
>> All leading 0's must be included to maintain consistent
segment length
<br>
>> for the application<br>
>><br>
>> A v1.2 UID of FF1234A2 is directly equivalent to a v1.3
UID of
FF.1234:A2<br>
>><br>
>> Examples of v1.3 UID's:<br>
>><br>
>> UID=FF.1234:00A6<br>
>> UID=FF.AB34:67A203<br>
>> UID=FF.000032:5C<br>
>><br>
>> There are ramifications to the xAPBSC v1.3 Basic Status
and Control <br>
>> schema (and xAPTSC) but these are self evident I hope as
you read the <br>
>> specification.<br>
>><br>
>> Any questions .. ask away....<br>
>><br>
>> Cheers Kevin<br>
>><br>
>><br>
>> Bauer, Steven J. wrote:<br>
>> <br>
>>> Is there anyplace where a person can find (even
the draft spec) of
the <br>
>>> version 1.3 xAP?? I would like to support the
extended uid
correctly <br>
>>> in the programs that I am writing?<br>
>>> <br>
>>> Thanks!<br>
>>> <br>
>>> Steve Bauer<br>
>>><br>
>>><br>
>>><br>
>>> <br>
><br>
><br>
><br>
><br>
> ------------------------------------<br>
><br>
> Yahoo! Groups Links<br>
><br>
><br>
><br>
><br>
> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span
style='color:white'><o:p></o:p></span></p>
</div>
</div>
<!-- **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=1969/stime=1242657427";
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=X3oDMTJmbGE4N2NxBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNDI2NTc0Mjc-";>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=X3oDMTJkNXVjMzkyBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjQyNjU3NDI3";>
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>
--_000_825EDC0C3291C943B30B9F79E82009410104304406sdsmtex07_--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|