[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Arbitrary strings as IDs
XML requires IDs and IDREFs to be names (eg they can't have spaces). Should our ID/IDREF replacement feature allow arbitrary strings? This is related to the typed IDs feature and to the support for IDREFS (more than one in a single attribute value).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC