>Three ways of making that a convention would be: > >a. The explict: http://www.foo.com/a/b/version=_verions_/morestuff > > In this case, the version is identified by a specially marked path > element. The path element could be anywhere. > >b. The implicit: http://www.foo.com/_version_/morestuff > > Here the first element implicitly denotes the version. This is a > bit like the way Atria uses their view-extended path names: the > first element is the view (which selects the the versions), and > subsequent elements are interpreted according to that view. > >c. The hidden: http://www.foo.com/a/b/_version_/morestuff > > Here the version, just as with The Economist, is simply an > indistinguishable part of the path. No one knows, except for > the version-controlled server. Again we use a convention as follows: http://www.foo.com/entity/_version_ This is because a version of an entity may consist of different versions of component entities. Generally speaking, each constituent of configuration layers may have different version schemas and numbers. For example, version 3 of an entire document consists of version 4 of a component and version 5 of another component. Regards, Kenji -- Kenji Takahashi | e-mail: kt@nttlabs.com NTT Software Laboratories | http://www.nttlabs.com/people/kt/ 250 Cambridge Avenue, Suite 205 | Phone : 415-833-3604 Palo Alto, CA 94306 | Fax : 415-326-1878