RE: Issues, Issues, ???

> Currently, I still have some stuff to write up for the revised
> protocol, but the only thing left on my "unresolved issue" list is:
>
> (1) Should version history URL's be in core (i.e. be required)?

No

> (2) Should version URL's be stable (i.e. cannot later refer to
> something else)?

Prefer no (but can live with yes).

I can imagine the simplest server (with a thin client) re-initializing the
versioning of a resource on request and recycling URLs.

	Thanks,

	Mark