- From: Norm Tovey-Walsh <norm@saxonica.com>
- Date: Tue, 17 May 2022 14:09:37 +0100
- To: public-ixml@w3.org
- Message-ID: <m2wnekwb2f.fsf@saxonica.com>
"C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com> writes: > ixml meeting 17 May 2022 I realized on closer inspection that I’m not sure where this issue is in the agenda: https://lists.w3.org/Archives/Public/public-ixml/2022May/0018.html I didn’t actually create an issue for it because I felt like it was editorial. But since it hasn’t been addressed yet, I want to make sure we can discuss it today. FWIW, the language that “@” makes an attribute is in the specification all the way back to the first commit in October 2020. I hope that restoring the previous language isn’t controversial. I’m happy to discuss how we can make the specification less XML-specific and more broadly applicable to other output formats in V.next, but we want to get 1.0 out by Prague and, IMHO, there’s no way to redraft the entire specification with a broader scope and get consensus on those changes before Prague. Given that the normative output of an ixml 1.0 processor is XML, I don’t think it’s wrong or misleading to describe the mapping in simple, concrete terms. That’s true even if our future goal is broader. Be seeing you, norm -- Norm Tovey-Walsh Saxonica
Received on Tuesday, 17 May 2022 13:20:12 UTC