This argument would apply to anything that has locale-specific behavior.
are there any other properties that should be revisited this way as well?
DFDL has the design point that the combination of schema & data should give the same result regardless of locale and/or machine. To create a schema that does vary across locale or machine requires the user deliberately to use expressions for the relevant DFDL properties (encoding, decimal separator, etc) and parameterise the schema, using either built-in DFDL variables or user-defined variables.
However the dfdl:calendarLanguage property is only defined as a String, I think it should also allow an expression as otherwise a schema is tied to a particular locale for it's calendar language support.
Regards
Steve Hanson
Architect, IBM Data Format Description Language (DFDL)
Co-Chair, OGF DFDL Working Group
IBM SWG, Hursley, UK
smh@uk.ibm.com
tel:+44-1962-815848
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
--
dfdl-wg mailing list
dfdl-wg@ogf.org
https://www.ogf.org/mailman/listinfo/dfdl-wg