[OASIS Issue Tracker] Updated: (CMIS-702) Define mapping of HTMLform fields to CMIS content

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/CMIS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Melahn updated CMIS-702:
--------------------------------

    Proposal: 
See http://www.oasis-open.org/committees/download.php/40884/POSTData.docx


> Define mapping of HTML form fields to CMIS content 
> ---------------------------------------------------
>
>                 Key: CMIS-702
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-702
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Browser Binding
>    Affects Versions: Browser Binding Proposal
>            Reporter: Gregory Melahn
>            Assignee: Florian Mueller
>             Fix For: Browser Binding Proposal
>
>
> To make it simple for web developers to create and update content, we will use HTML forms.  This proposal describes how we will map HTML form field names to CMIS content including object properties, ACE's, policies, versioning state, checkin comments, change token, file name and query.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira