Page History

...

• NACHA
• ISO8583
• QuasiXML
• GeoNames
• IBM4690TLOG (as of 2019-05-17 - development branch)

The following schemas are published, are intended to be portable/interoperable, but do not yet work across implementations due to DAFFODIL features/bugs

...

• EDIFACT

The following schemas are published, but need minor adjustments for portability, including possibly documentation edits on the DFDLSchemas web site materials.

...

This test suite is part of the Daffodil source tree, but can be run against IBM DFDL using a cross tester.

Daffodil tests that fail on IBM DFDL, but NOT due to interoperability concerns:

These Daffodil tests fail on IBM_DFDL, but should not. They fail because of DAFFODIL-2026 - a limitation in Daffodil's TDML Tester

• test_simple_type_properties_text_calendar_13_03
• test_simple_type_properties_text_calendar_13_04
• test_simple_type_properties_bin_calendar_13_01
• test_simple_type_properties_bin_calendar_13_02
• test_simple_type_properties_text_calendar_13_01
• test_alignment_bytes_12_05

Incompatibilities

These tests fail for lack of support of identical separator and terminator in IBM DFDL. All these are the same issue. This issue is considered minor, and is not a barrier to interoperability in practical schemas.

• test_length_delimited_12_01
• test_length_delimited_12_04
• test_multiple_delimiters
• test_length_delimited_12_02
• test_length_delimited_12_03
• test_nested_separator_delimited_baseline_ibm

Needs Further Investigation

Currently (2018-12-10) These tests fail on IBM DFDL with a NPE during schema compilation. No trace output is produced  - Need study to determine cause. The origin of these tests was the very earliest part of the Daffodil project at Univ. of Illinois NCSA.

• test_AF000, test_AF001, test_AF002
• test_AW000, test_AW001
• test_AX000
• test_AY000
• test_AZ000

All tests in this suite run portably on Daffodil and IBM DFDL. (2019-05-17 development branch).

A few tests are conditionalized and run on only one or the other due to specific features that Daffodil has, or that IBM has.

Daffodil Test Suite 'daffodil-test'

...

• daf:error - function obviously not supported by IBM DFDL.
• Many daffodil tests put constructs on global elements that are not allowed on global elements by DFDL.
• Many tests have namespace errors - root elements of infosets are not in the proper namespace.  (commonly this is the ex or http://example.com namespace)
• Missing properties (textBooleanTrueRep/FalseRep being undefined is one)
• Mixing of invalid schema errors in the same test suites with other tests.
  
  • Different defineSchema inside a TDML file are not being isolated - compile errors in one stop all tests in that TDML file from compiling.
  • This is a TDML Runner issue and just how tests are authored.
• Incorrect property syntax: extraEscapedCharacter="%#WSP*; ..." for example
• Missing properties: textBidi, textPadKind, textTrimKind, escapeSchemeRef, documentFinalTerminatorCanBeMissing, and many others are missing from  test environments.

Incompatibilities

• test_timeFunctions01 - IBM DFDL does not support dfdl:calendarTimeZone="" (empty string, meaning 'no time zone')
  • This is problematic because the default format most tests use has this property defined this way.
  • TBD: Perhaps tests should choose from the normal daffodil default formats, and one designed for compatibility??
• dfdl:calendarPattern contains more than 3 "S" symbols. (Should be a warning? - possible bug in cross-test rig)
• separator and escapeCharacter cannot include the same value - this is tolerated by Daffodil. (Allows a delimiter to be escaped by doubling it.)

...