POST form data

[Florian Müller <florian.mueller@alfresco.com>]

Hi all,

Here are some initial thoughts on HTTP POST and how the form data could look like.

Form fields:

- action
  Action indicator. See URL patterns.
  
- objectId
  Object id. See URL patterns.

- property_name_<index> and property_value_<index>
  Single value property value.
  Example:
    property_name_0  = cmis:name
    property_value_0 = my%20document
    property_name_1  = my:singleInteger
    property_value_1 = 42

- property_name_<index> and property_value_<index>_<listIndex>
  Multi value property value
  Example:
    property_name_0    = my:mvProperty
    property_value_0_0 = first
    property_value_0_1 = second

- addACE_principal_<index> and addACE_permission_<index>_<permIndex>
  ACE to add.
  Example:
    addACE_principal_0    = bob
    addACE_permission_0_0 = cmis:read
    addACE_permission_0_1 = cmis:write

- removeACE_principal_<index> and removeACE_permission_<index>_<permIndex>
  ACE to remove.
  Example:
    removeACE_principal_0    = tom
    removeACE_permission_0_0 = cmis:write

- policy_<index>
  Policy to set.
  Example:
    policy_0 = policy-id-001
    policy_1 = policy-id-002

- changeToken
  The change token. If unknown, it should not be set.

- versioningState
  Versioning state

- checkinComment
  Checkin commment.

- filename
  Filename.

- query
  CMIS QL.

...to be continued...


You might wonder why the property ids and principal names are not part of the field names. The reason is that form input names are case-insensitive.
A CMIS repository could expose a type with a property "my:property" and a property "my:PROPERTY" and those would be two different properties.


Any comments?

Florian