[DAS2] mapping document

[Andrew Dalke]

Been thinking about the response to a writeback.  The spec said
the server responds with a mapping document saying "uploaded id
X is now Y".

As per discussion this will now return a features document.  Each
feature element may contain a new attribute "was" if its URI
changed.  This happens for one of two reasons:
   - the client created the feature using the private naming scheme
   - the server supports versioning and each feature version gets
        its own identifier

Perhaps also "the server's ornery and jest feels like it."

I had written the spec so a server could optionally implement
type writeback.  With this change that is not possible.  It's
possible to have a new return document which combines features
and types (which is very similar to the current writeback spec).

However,  type writeback was not considered a high priority and
none of the servers under development will support such thing.
(Correct?)  If needed we have extension mechanisms by which that
can be supported in the future.

questions:
   - I wrote above that the new attribute is named "was", as in

<FEATURE uri="blah" was="spam" ...>
</FEATURE>

The word "was" is wrong.  Otherwise the new version should be "is",
and not "uri".  Other options are "previously", "old_uri",
"prev_uri", "previous_uri", "uri_was"

I can't find old discussion on this.  Anyone one not like "old_uri"
and have a better name?


   - anyone want type writeback in this version of the spec?  if not
i'll remove all traces of it from the spec.

					Andrew
					dalke at dalkescientific.com