remotestorage-00 -> remotestorage-01

[mic...@michielbdejong.com]

my idea for remotestorage-01 is to make it a bugfix release, and make it
happen in four months from now, when remotestorage-00 expires.

As i am implementing remotestorage-00 in the remotestorage ownCloud app
https://github.com/michielbdejong/owncloud-owa
i actually found quite a few small bugs. I'm tracking them here:
https://github.com/RemoteStorage/spec/commits/master

Specifically, this one:
https://github.com/RemoteStorage/spec/commit/127ac4cbdb171cb4c742611545370263f8cb5310
was found by Steven, who emailed me about it. Thanks for spotting it! :)

All proposed changes so far are bugfixes, so fixing the text to align it
with how it was intended:
- fix the names and response codes of the conditional headers
- allow dots in item names
- forbid zero-length folder names

There have also been suggestions for changes to the actual intended content
of the spec, like dropping the requirement that ETags be milli-timestamps
(by Steven)
and adding byte range support (by Francois), but i don't think we should
make such changes unless several apps or several storage servers are
having trouble with it.

The milli-timestamps are controversial from a design perspective, but very
easy to implemement on most systems, so it doesn't actually hurt anyone.
The byte ranges are necessary in theory, and the point is of course valid,
but in practice we can do without (right now i'm listening to a 3-hour
DJ set which I'm "streaming" as one big 300Mb http request, and I do
this every day, it works without problems).

In all cases, there are several storage implementations already out there,
and a library that is included in several deployed apps, and each change
which is more than a bugfix in the text would be spending scarce resources.
Also, we will have a chance to make changes every 185 days for a while to
come, so i prefer to postpone bigger changes as much as possible.

Hope this makes sense. :)


Ciao!
Michiel