[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-520) Inconsistent use ofabstract attribute in XML schema
[ http://tools.oasis-open.org/issues/browse/CMIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266#action_17266 ]
Al Brown commented on CMIS-520:
-------------------------------
JIRA Cleanup
> Inconsistent use of abstract attribute in XML schema
> ----------------------------------------------------
>
> Key: CMIS-520
> URL: http://tools.oasis-open.org/issues/browse/CMIS-520
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Improvement
> Components: Schema
> Affects Versions: Draft 0.63
> Reporter: Jens Hübel
> Priority: Trivial
> Fix For: Draft 0.63
>
>
> We only have one location in CMISCore.xsd that uses the "abstract" attribute:
> <xs:complexType name="cmisTypeDefinitionType" abstract="false">
> This seems not to make too much sense. Either we ignore the existence of the abstract capability completely and remove this attribute here. Or we use it consistently within the schema which raises the followinig questions:
> 1) Why is it set to false, cmisTypeDefinitionType should be an abstract type? This is confusing.
> 2) We have other types in the schema that are abstract too, e.g. cmisPropertyDefinitionType that do not use abstractl.
> The default is probably false anyway so removing it would be easiest solution. Making use of abstract=true would allow better validation.
--
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]