It's hard to search for this. Does anyone recall resolution to this? If you specify properties that are clearly mismatched e.g., you specify dfdl:occursCountKind on an element that isn't an array, or you specify dfdl:textStringJustification on a number. Does this generate an error or a warning or nothing? Obviously this doesn't cause any issue if these properties are in scope or referenced from a format annotation. It's only an issue if they are actually written locally in short or long-form annotations right on the point where the incompatibility resides. -- Mike Beckerle | OGF DFDL WG Co-Chair | Tresys Technologies Tel: 781-330-0412
Mike, this was covered by the 2nd half of errata 3.8 as follows: Clarify what action a DFDL processor should take when it encounters an object that explicitly carries properties that are not relevant to the object as defined. o Property not applicable to the object’s DFDL annotation. Schema definition error. Example is lengthKind on xs:sequence. o Property not applicable because of simple type. Warning (optional). Example is calendarPatternKind on xs:string. o Property not applicable because of another DFDL property setting. Warning (optional). Example is binaryNumberRep when representation is text. o Property not applicable because object is local, global or reference. Warning (optional). Example is occursCountKind on a global xs:element. ** ** Excludes inputValueCalc and outputValueCalc which give SDE. IBM DFDL has a big bunch of checks for the warnings, but we are considering making them an optional feature on performance grounds. Regards Steve Hanson Architect, Data Format Description Language (DFDL) Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh@uk.ibm.com tel:+44-1962-815848 From: Mike Beckerle <mbeckerle.dfdl@gmail.com> To: dfdl-wg@ogf.org, Date: 20/12/2012 21:02 Subject: [DFDL-WG] irrelevant properties Sent by: dfdl-wg-bounces@ogf.org It's hard to search for this. Does anyone recall resolution to this? If you specify properties that are clearly mismatched e.g., you specify dfdl:occursCountKind on an element that isn't an array, or you specify dfdl:textStringJustification on a number. Does this generate an error or a warning or nothing? Obviously this doesn't cause any issue if these properties are in scope or referenced from a format annotation. It's only an issue if they are actually written locally in short or long-form annotations right on the point where the incompatibility resides. -- Mike Beckerle | OGF DFDL WG Co-Chair | Tresys Technologies Tel: 781-330-0412 -- dfdl-wg mailing list dfdl-wg@ogf.org https://www.ogf.org/mailman/listinfo/dfdl-wg Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
participants (2)
-
Mike Beckerle -
Steve Hanson