[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: ArchForms and LPDs
On Mon, Jul 26, 2021 at 6:02 AM Liam R. E. Quin <liam@fromoldbooks.org> wrote:
If you want determinism, just don't overload the element/attribute, so it always has the same datatype? In-place parsing isn't going to fly in a world with XInclude, nor for For XInclude, that is an application-level thing, not a parser thing. For NFC, IIRC the result of NFC normalization is (always?) smaller than non-normalized forms. So it does not require buffer enlargement. Sure, the act of decomposing a combining character sequence before recomposing it to a character may take an extra byte or two, and need a small string (I think Unicode doesn't allow more than 30 combining characters in a sequence, which would never happen.) Personally i'd be mre interested in a mini-xsd language that also was In the meantime, you could try the JSON version of Schematron, jsontron: https://www.npmjs.com/package/jsontron XML is already more complex than is useful. But we're stuck with it. That's what people said in 1994. MicroXML was an attempt to make a subset, but it's too small and also Yes. A mere subset is no bee's knees. If there's a way forward it's neither in re-inventing lower layers no Yes. Unless it does something that other formats don't, with any convenience, there is no point. Cheers Rick
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|