OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (CMIS-805) Add property groups to type definitions


Florian Mueller created CMIS-805:
------------------------------------

             Summary: Add property groups to type definitions
                 Key: CMIS-805
                 URL: https://issues.oasis-open.org/browse/CMIS-805
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: New Feature
          Components: Domain Model
    Affects Versions: Proposals for 2.0
            Reporter: Florian Mueller


When a generic CMIS client should display the properties of an object, it can only show them as a flat list in a random order. That can be confusing to end-users. A simple example is an address with properties for the street, the city, the state, and the zip code. It would be nice to group them together in a meaningful order.

The type definition should contain an (optional) ordered list of property group definitions. A property group consists of a display name and an ordered subset of the properties of that type. A client could than iterate through the property groups and within the property groups through the properties and display them. Not all properties need to part of a property group.

Property groups only exist on the type definition level. They don't have any effect on the way the properties a transmitted.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]