richard at dobson-i.net
Tue May 6 19:01:14 UTC 2003
I was thinking exactly this just now while pondering this in the bath,
having the namespace as the jep page until it reaches final in which case it
reverts to the authors preferred namespace.
Also the versioning idea is good but I think authors should only bother to
update the version number on the namespace if there are incompatible or
required changes between versions, otherwise it could add an unnecessary
burden on implementors even tho by implementing an experimental protocol
they have undertaken the requirement to keep their implementation up to
----- Original Message -----
>From: "Evan Prodromou" <evan at prodromou.san-francisco.ca.us>
To: <standards-jig at jabber.org>
Sent: Tuesday, May 06, 2003 7:29 PM
Subject: Re: [standards-jig] Avatars
> >>>>> "DC" == Daniel Chote <daniel at chote.net> writes:
> DC> Instead of doing a per client namespace (which i think is a
> DC> stupid idea). why take a jep revision based approach such as
> DC> xmlns="http://www.jabber.org/jeps/jep-0008.html/1.0"
> Or, maybe "http://www.jabber.org/jeps/jep-0008.html#1.0", with the JEP
> XSL creating an <a name='1.0'> for each revision.
> The version is part of the namespace. As the semantics and syntax of
> the standard changes, the namespace changes, too.
> I also think this should be part of each JEP revision.
> Evan Prodromou
> evan at prodromou.san-francisco.ca.us
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards