Ok. This is just a thought, and I know this may have been mentioned
before. But why not
specify that for PUT and POST operations we will weaken the atom xml
syntax spec so that
fields that are usually required can be ignored. It would be easy
then to specify that the server should fill in all values that are
missing automatically.
((Btw: an RDF spec would have made this a lot easier to state.))
This would then be a little like when we edit a file on unix. The OS
will automatically change the
updated time stamp on files we change. I would not be surprised if
there were not ways to specify the time stamp if one really wanted to
on unix (any pointers).
Henry
On 5 Jul 2006, at 23:08, James M Snell wrote:
http://www.intertwingly.net/wiki/pie/PaceAppUpdated
#pragma section-numbers off
== Abstract ==
Regarding Draft-09... add an explicit statement that the server
determines when and if the atom:updated element is modified
== Status ==
Proposed
== Rationale ==
Whether or not to change atom:updated on an update request is
implementation specific and can only reasonably be determined by the
server. A server could choose to use the atom:updated value
provided by
the client, but is not required to do so.
== Proposal ==
{{{
8.6 Editing members and the atom:updated element
Upon successfully processing an update request on a member resource
or linked media resource, a server MAY modify the value of the members
atom:updated element. The choice of whether or not to modify the
value of atom:updated is an implementation choice that is dependent on
whether or not the server considers the update to be significant.
}}}
== Impacts ==
== Notes ==
----
CategoryProposals
