Forums » #117 - DFDL v1.0 Revision »
Schema Definition Errors for non-applicable properties
Added by Tim Kimber about 9 years ago
The specification should make a statement about this situation:
- A DFDL property is supplied for a schema component
- The DFDL processor does not need to examine the property in order to process the data
- There is a problem with the property value that would trigger a Schema Definition Error if the processor did examine the property
Example 1:
- dfdl:representation is 'text'
- binaryBooleanTrueRep has a bad value ( is not a valid DFDL String Literal )
Example 2:
- dfdl:representation is 'text'
- binaryBooleanTrueRep is explicitly defined on the element and on its simple type
I am fairly sure that XML Schema would require that the entire schema is valid before it is used for any purpose.
Replies (7)
RE: Schema Definition Errors for non-applicable properties - Added by Michael Beckerle about 9 years ago
These are surely some sort of schema definition errors. Question is, does the DFDL standard require them to be detected, or is a higher-quality implementation that detects them, lower quality implementation is still conformant, but doesn't help users this way.
In other words, are there sets of SDEs where detecting them is considered an optional feature?
If I added rows to that table of optional DFDL features late in the spec, and the rows said
Detection of irrelevant DFDL properties
Detection of invalid values for irrelevant DFDL Properties
To some degree this seems ok to me. E.g., what if I create a DFDL implementation that is very very bad at diagnostics, but screaming fast, and I do that intentionally, expecting you to use some other DFDL implementation during development and debug, and use my DFDL implementation just for deployment?
RE: Schema Definition Errors for non-applicable properties - Added by Steve Hanson about 9 years ago
This sort of thing is already discussed in section 2.7 (Optional checks and warnings) but the categories do not quite cover Tim's scenarios.
RE: Schema Definition Errors for non-applicable properties - Added by Steve Hanson almost 9 years ago
Jonathan has also noted that the phrase 'schema definition warning' appears once in section 2.6.
Resolved - RE: Schema Definition Errors for non-applicable properties - Added by Michael Beckerle almost 9 years ago
Add to 2.7 additional paragraph describing optional warning if there is a invalid property value for a property that is unused or being ignored.
For example: dfdl:length property, is unused when dfdl:lengthKind="fixed". If dfdl:length has a value which is an expression and that expression has some invalid syntax within it.
For example: unused escape scheme having inconsistent properties, such as having an escapeBlockStart, but no escapeBlockEnd defined.
Add reference to implementation-dependency section.
Change 2.6 "Schema Definition Warning" to just "warning".
Resolved: Schema Definition Errors for non-applicable properties - Added by Steve Hanson over 8 years ago
New erratum 4.21 in experience document 1.
DONE - RE: Schema Definition Errors for non-applicable properties - Added by Michael Beckerle over 8 years ago
change in draft-gwdrp-dfdl-v1.0.4-r06.docx
DONE - RE: Schema Definition Errors for non-applicable properties - Added by Steve Hanson about 8 years ago
(1-7/7)