document #207
Schema Definition Errors for non-applicable properties
| Status: | closed | Start date: | 10/02/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Tim Kimber | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Document Type: | Proposed Recommendation |
Description
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
History
Updated by Steve Hanson about 8 years ago
- Status changed from public comment to closed
- % Done changed from 0 to 100
See http://redmine.ogf.org/boards/15/topics/106
Erratum 4.121 raised. GWD.207 updated.
(Other formats not available in this archive.