One of the rest concepts is to do a get with @verbose=0&@protected=true. The attributes
dict returned should be able to be modified and returned.

This round trip is not currently done in testing.

However currently protected items in the list are ignored. This isn't quite right.

The rule should be:

  if a protected property matches the current value in the database, ignore it.

  if the property does not match the entry in the db, reject it with a usage error
    and a message like "creator is a reserved property and can not be set".

This will fix the following issue:

  kanban drag and drop does not error when the columns are a reserved prop (e.g. creator).
  the drop sends the put for creator to the back and and the back end filters the reserved
  prop out. It should error. (see issue2551363)