FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
sheinrich
Summary
All references to "present" in the validation rules must be changed to "exists".
For example, from: "If firstPeriodStartDate is present, @href must match the @id attribute of a party element."
To: "If firstPeriodStartDate exists, @href must match the @id attribute of a party element."
The distinction between present and exists is significant. Take the example of default/implied values which exist but may not be present.
You must also define exists and present in the manual.
Notes:
h_mcallister
08/15/07 3:45 pm
By all means define terms and use them consistently, however the distinction between “present” and “exists” is spurious.
The terms are used interchangeably through the validation rules. The meaning is intuitively clear i.e. the referenced element is produced in the instance document (what else should we validate??).
The only use of default/implied values in FpML is to specify the default value of coding scheme attributes (I’m happy to be corrected on this …); there are no validation rules on such attributes, so the example is irrelevant.
matthew
08/15/07 3:53 pm
I agree it is not significant for the schema, but it is significant for the architecture, which has uses outside the current schema; for example in extensions.
mgratacos
09/25/07 1:38 pm
Validation Working Group 2007-09-25: Agreed to do the replacement.
mgratacos
09/25/07 4:04 pm
This has been committed to the trunk (4.4) and 4.3 branch.