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: [cmis] [CMIS 1.1 Draft Review] CMIS 1.1 Working Draft 01b: correction for section 2.1.9.1



In section 2.1.9.1
General Constraints on Metadata Changes

The section that says:

Validation constraints (min/max length, min/max value, etc.) on existing properties MUST
NOT be relaxed. They MAY be further restricted. For example, an integer minimum con-
straint value of 100 for an integer MAY be changed to 90 but not to 110.

(I believe) Should instead read:

Validation constraints (min/max length, min/max value, etc.) on existing properties MAY be relaxed but they MUST NOT be further restricted. For example, an integer property value who originally had a minimum constraint of 100 and a maximum constraint of 1000 could change as follows:
A new minimum could be changed to 50 but could not be changed to 150. 
A new maximum could be changed to 1100 but could not be changed to 900.  
This ensures that the new constraints will not leave any existing data out of the permitted constraint range. 

This is pretty much the opposite of what we had in there before.   That was probably incorrect in my original Mutable metadata draft.



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