[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sarif] Provisional draft includes all changes
We agree on #1. I’ll file an issue and make the change in the provisional draft. I’ll put a change-barred version in the “Accepted” folder. I can move it to “Rejected” and revert the change in the unlikely event the TC rejects it in the e-ballot.
As for #2: As you say, Jim worried that if we chose the wrong default, a tool that accidentally omitted columnKind would induce unexpected behavior in the consumer (for example, the consumer would interpret columns as UTF-16 code units when the producer meant them to be interpreted as Unicode code points).
But if we do what you say, a tool that accidentally omits columnKind will induce unpredictable behavior in the consumer (some consumers might interpret the columns as UTF-16 code units, and others as Unicode code points). To my mind, that’s worse.
I still prefer my proposal of keeping columnKind as required (which is what the TC approved), and adding a value "none" that non-text-processing tools can use.
Here is the status:
I will wait for resolution of those two issues before creating the ZIP. May I ask Michael to help me drive resolution of the two issues (by which I mean, gently nudge people who care about them to weigh in – I’m not good at that), and David and Stefan to adjust our balloting process to accommodate the changes, if we accept them.