Symmetry in submission Re: ACTION-2292: Specify merge of send and load.

• From: Steven Pemberton <steven.pemberton@cwi.nl>
• Date: Fri, 11 Dec 2020 14:16:03 +0100
• To: public-xformsusers@w3.org, "XForms Users Community Group Issue Tracker" <sysbot+tracker@w3.org>
• Message-ID: <op.0vgps1bksmjzpq@steven-xps13>

While working ACTION 2292, it struck me that there's a disagreeable lack  
of symmetry in submission.

Example: saving and restoring an instance:

  <submission id="save" resource="list.xml" method="put"
              ref="instance('list')"
              replace="none"
  />

  <submission id="restore" resource="list.xml" method="get"
              replace="instance" instance="list"
              serialization="none"
  />


(how I wish we had used "serialize" instead of "serialization", since it  
is shorter, and "replace" is a verb and not a noun, while "serialization"  
is a noun not a verb).

A symmetric approach would look like this:

  <submission id="save" resource="list.xml" method="put"
              ref="instance('list')"
              replace="none"
  />

  <submission id="restore" resource="list.xml" method="get"
              targetref="instance('list')"
              serialization="none"
  />

I realise that the default value of "replace" is "all", but we could say  
that the default value is only "all" if there is no @targetref.

Why do you think?

Steven

Received on Friday, 11 December 2020 13:16:19 UTC