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] Commented: (CMIS-319) There should be justone default value



    [ http://tools.oasis-open.org/issues/browse/CMIS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579#action_13579 ] 

Al Brown commented on CMIS-319:
-------------------------------

fixed in 62e

changed maxOccours from unbounded to 1.

Also changed the cmisChoice* to be similiar how defaultValue is modeled.

Example of a string property w/ default value & choice list
        <cmis:propertyStringDefinition>
            <cmis:id>custom-customertype</cmis:id>
            <cmis:localName>rep-custom-customertype</cmis:localName>
            <cmis:displayName>custom-customertype</cmis:displayName>
            <cmis:description>Description for custom-customertype</cmis:description>
            <cmis:propertyType>string</cmis:propertyType>
            <cmis:cardinality>single</cmis:cardinality>
            <cmis:updatability>readwrite</cmis:updatability>
            <cmis:inherited>true</cmis:inherited>
            <cmis:required>false</cmis:required>
            <cmis:queryable>true</cmis:queryable>
            <cmis:orderable>true</cmis:orderable>
            <cmis:openChoice>false</cmis:openChoice>
            <cmis:defaultValue localname="rep-custom-customertype" pdid="custom-customertype">
                <cmis:value>defaultvalue for custom-customertype</cmis:value>
            </cmis:defaultValue>
            <cmis:maxLength>128</cmis:maxLength>
            <cmis:choice displayName="Choice 1">
                <cmis:value>choice1value</cmis:value>
            </cmis:choice>
            <cmis:choice displayName="Choice 2">
                <cmis:value>choice2value</cmis:value>
            </cmis:choice>
            <cmis:choice displayName="Choice 3">
                <cmis:value>choice3value</cmis:value>
            </cmis:choice>
        </cmis:propertyStringDefinition>

> There should be just one default value
> --------------------------------------
>
>                 Key: CMIS-319
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-319
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Schema
>    Affects Versions: Draft 0.62
>            Reporter: Florian Mueller
>            Assignee: Al Brown
>             Fix For: Draft 0.62
>
>
> The schema defines default values in property definition types like this (string property type example):
> <xs:element minOccurs="0" maxOccurs="unbounded" name="defaultValue" type="cmis:cmisChoiceStringType" />
> This implies that a property definition type could have multiple default values which doesn't make sense. It should be: 
> <xs:element minOccurs="0" maxOccurs="1" name="defaultValue" type="cmis:cmisChoiceStringType" />
> Apart from that, cmisChoiceStringType defines some attributes and a hierarchy that don't apply to a default value. Shouldn't it be a simple value/list?

-- 
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

        


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