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-201) Explain why baseTypeand baseTypeQueryName are specified



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

David Caruana commented on CMIS-201:
------------------------------------

I believe this is resolved by CMIS-87.  Although baseType and baseTypeQueryName still exist, baseType is a property, and baseTypeQueryName is accessible via type definition only.

> Explain why baseType and baseTypeQueryName are specified
> --------------------------------------------------------
>
>                 Key: CMIS-201
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-201
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> 0.62a Domain Model Line 538
> What is the point of including both baseType and baseTypeQueryName when for all 4 base types they have the same value (except for case, but query names are not case sensitive).

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