RE: PaceVersionAsText

["Dare Obasanjo" <dareo@xxxxxxxxxxxxx>]

You are jumping the gun. Unless you have a versioning policy in place there isn't much point in trying to bake semantics into the version number. 
 
-- 
PITHY WORDS OF WISDOM
There are always two solutions to the problem: yours and the boss's. 

________________________________

From: owner-atom-syntax@xxxxxxxxxxxx on behalf of Antone Roundy
Sent: Wed 6/23/2004 6:09 PM
To: atom-syntax@xxxxxxx
Subject: PaceVersionAsText




Whether the version is a number, something resembling a number (eg. a
dotted triple (sorry, not RDF) like 0.5.2) or text, it would be useful
to have some structure in the version string so that a number or
something resembling one could be extracted from it easily.  I'd
imagine there will be things in, for example, version < 1.5 or 1.2 <
version < 1.8.3 or version >= 2.0, etc.  Being able to quickly extract
that number and do numeric comparisons to know how to handle certain
things would be good.

Having some sort of structure would require a change to the proposal,
since it proposes saying "The format of this attribute is unstructured
text."

Maybe we could use something like <feed version="0.5.1;
draft-ietf-atom-format-04.txt; do not implement this"> where everything
before the first semicolon is number-like, and everything after it is
unstructured text.

Antone