[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Call for dissent csprd01 comments 033, 057, and 061 - Validation Module design changes proposal.
In an effort to simplify and clarify the Validation Module, we would like to propose the following changes in response to csprd01 comments 033, 057, and 061. This table summarizes
the changes that will need to be made to the module’s attributes that signify “rules”.
Additionally, the following changes to processing requirements: ·
I.1.2.2 - second bullet: When <validation> occurs at the <group> level, rules must be applied to all <target> elements within the scope of <group>, except where overrides
are specified in a nested <group> element, or at the <unit> level. ·
I.1.2.2 - remove the last bullet: When <validation> occurs at the <segment> level, rules must be applied to the <target> element within the scope of the <segment>. ·
I.1.2.3 – Exactly one of the following attributes:
·
isPresent
·
isNotPresent
·
Placeholder
·
stsrtsWith
·
endsWith
·
or a custom rule defined by elements from any namespace must be used in any one <rule> element.
And a change to the method of escaping quotes: …double quotation mark " (U+0022) must be escaped by using the predefined XML entity " and single quotation mark ‘ (U+0027)
by using the predefined XML entity ' If anybody has suggestions or objections to these changes, please let me know by 22 July. Otherwise, I will consider these issues resolved, and update the spec. Thanks, Ryan |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]