
Mike I had suggested elementAlias for exactly the two reasons you mention :) If we add xs:any support in the future then we don't need to add a new property, and it makes refactoring a choice into a wildcard, and vice versa, straightforward. I am ok changing the name but I don't think the name should contain 'choice'. With SAP IDocs, the element name is the content of the tag field. 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: 03/04/2012 15:42 Subject: [DFDL-WG] issue 145 - name dfdl:elementAlias Sent by: dfdl-wg-bounces@ogf.org About the name dfdl:elementAlias It suggests that this is another element name, and in other contexts than a choice it might be used as well, and in addition it suggests that the dfdl:choiceBranchRef can evaluate to the element name, or to this alias. I think the definition of all this behavior should be narrower, and the names should suggest this. dfdl:choiceBranchRef dfdl:choiceBranchID seem like the right pairing. A choice branch ref can refer to exactly and only the choice branch ID, never the element name, and this ID is used only for choice branch ref purposes. ...mikeb -- Mike Beckerle | OGF DFDL WG Co-Chair 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