RE: Re: Changes to Protocol Docs - a Summary

["Ian Lowe" <ian.lowe@xxxxxxxxxxxxxxxxxx>]

There's a need here for the version information to be in the xml file -

Developers will create new functionality in existing apps. If the xml
files describes the triggers and commands available for each version of
the app, it eases the process.

There's one xml file for each vendor, as you say, but each device is
broken out inside that file - in <device></device> - I don't
see a
reason why that can't become:

<device>
<1.23>
trigs etc for v1.23
</1.23>
<1.5>
trigs etc for v1.5
</1.5>
</device>

This way, the frontend apps can tell which features are available from
the combination of returned version and the vendor's xml file.

That, tbh, kinda leads itself to major/minor/revision numbering...

Major is a change in features,
Minor is an update that you *should* do as it contains bugfixes,
Revision is a minor change that you can update for.

>From what I can see on sourceforge, this numbering system is widely
adopted across a lot of different projects.

I'd say numbers only, as characters (like "b" or "rc"
etc) are human
readable, but not readily machine parseable.

Ian.



-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of Mal Lansell
Sent: 26 September 2005 14:14
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] Re: Changes to Protocol Docs - a Summary

The version number of the running app is not stored in the vendors xml
(because there is only one xml per vendor, not per application)

They could store the version number of the latest release in the vendor
xml, so we can compare and see if an update is available, but in that
case we will need a format that we can parse using a standard set of
rules.

Mal


--- In ukha_xpl@xxxxxxx, Tom Van den Panhuyzen <tomvdp@g...>
wrote:
> Why any formatting ?
> Will this nr ever be used in an automated way ? And if so, the nr
to compare
> with is probably coming from the vendor's xml file or similar.
>  (still not convinced ;-)
>  Tom
>
>
>  On 9/26/05, Paul Robinson <ukcueman@y...> wrote:
> >
> > What about version numbers like "1.2rc1" or
"1.3b" to indicate
whether
> > this is beta or a
> > release candidate etc
> >
> > ----- Original Message -----
> > From: "Ian Lowe" <ian.lowe@w...>
> > To: <ukha_xpl@xxxxxxx>
> > Sent: Monday, September 26, 2005 12:16 PM
> > Subject: RE: [ukha_xpl] Re: Changes to Protocol Docs - a Summary
> >
> >
> > > Yeah - I don't see the need to enforce a specific format,
beyond
> > > specifying what it can contain: numbers and decimal points
only, no
> > > leading "v" or "ver" etc.
> > >
> > > Ian.
> > >
> > > -----Original Message-----
> > > From: ukha_xpl@xxxxxxx
[mailto:ukha_xpl@xxxxxxx] On
> > > Behalf Of Paul Robinson
> > > Sent: 26 September 2005 11:54
> > > To: ukha_xpl@xxxxxxx
> > > Subject: Re: [ukha_xpl] Re: Changes to Protocol Docs - a
Summary
> > >
> > > > If we're going to specify the format of the version
number,
can I make
> > >
> > > > an appeal for a 3 part numerals only version e.g
4.12.1543 -
then it
> > > > would match the version numbering system in the Windows
Installer that
> > >
> > > > most of us use to package our apps.
> > > Is it necessary to tie developers to a particular format?
Saying that it
> > > shouldn't be prefixed by "version" or
"v" etc is quite
different from
> > > specifying exactly how they should be formatted.
> > >
> > > Paul
> > >
> > >
> >
> >
> >
> >
> >
> >
> > ___________________________________________________________
> > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide
with
> > voicemail http://uk.messenger.yahoo.com
> >
> >
> > xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
> > http://www.xpl.myby.co.uk To Post a
Message:
> > ukha_xpl@xxxxxxx To Subscribe:
> > ukha_xpl-subscribe@xxxxxxx
> > To Unsubscribe: ukha_xpl-unsubscribe@xxxxxxx
> >
> >
> >
> > SPONSORED LINKS
> >   Protocol analyzer<http://groups.yahoo.com/gads?
t=ms&k=Protocol+analyzer&w1=Protocol+analyzer&w2=Protocol+converter&w
3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig
=QulmGKu5OpHgigyaWFXqqA> Protocol
> > converter<http://groups.yahoo.com/gads?
t=ms&k=Protocol+converter&w1=Protocol+analyzer&w2=Protocol+converter&
w3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.si
g=_Gav_2JNLbgwjsCn8RqM-w> Sip
> > protocol<http://groups.yahoo.com/gads?
t=ms&k=Sip+protocol&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip
+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=d2G6
YVkW-P5WBFmpuWQ3Zw>
> > Tcp<http://groups.yahoo.com/gads?
t=ms&k=Tcp&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+protocol
&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=9xqmZjMntiOfV
EPLIpwKUg> Protocol
> > analysis<http://groups.yahoo.com/gads?
t=ms&k=Protocol+analysis&w1=Protocol+analyzer&w2=Protocol+converter&w
3=Sip+protocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig
=j5RxaJ5TSW2NTgWhIna4qQ>
> > Protocol<http://groups.yahoo.com/gads?
t=ms&k=Protocol&w1=Protocol+analyzer&w2=Protocol+converter&w3=Sip+pro
tocol&w4=Tcp&w5=Protocol+analysis&w6=Protocol&c=6&s=111&.sig=OPnkI6Ga
dMASTgKewyeqDQ>
> >  ------------------------------
> > YAHOO! GROUPS LINKS
> >
> >
> >    - Visit your
group "ukha_xpl<http://groups.yahoo.com/group/ukha_xpl>"
> >    on the web.
> >     - To unsubscribe from this group, send an email to:
> >    ukha_xpl-unsubscribe@xxxxxxx<ukha_xpl-
unsubscribe@xxxxxxx?subject=Unsubscribe>
> >     - Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> >    Service <http://docs.yahoo.com/info/terms/>.
> >
> >
> >  ------------------------------
> >
>
>
> [Non-text portions of this message have been removed]