Remove <ins> and <del> markup in preparation for 1.2#676
Remove <ins> and <del> markup in preparation for 1.2#676
<ins> and <del> markup in preparation for 1.2#676Conversation
| <li id="alg-inv-defaul-base-dir" class="changed"> | ||
| <ins cite="#change_pr639"><em>(this step was removed by a <a href="#change_pr639">candidate correction</a>)</em></ins> | ||
| <del cite="#change_pr639"> | ||
| Otherwise, if <var>active context</var> has a | ||
| <a>default base direction</a>: | ||
| <ol> | ||
| <li>Initialize a variable <var>lang dir</var> | ||
| with the concatenation of <var>default language</var> and <a>default base direction</a>, | ||
| separate by an underscore (`"_"`), | ||
| normalized to lower case.</li> | ||
| <li>If <var>language map</var> does not have a <var>lang dir</var> <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| <li>If <var>language map</var> does not have an `@none` <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| <li>If <var>type map</var> does not have an `@none` <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| </ol> | ||
| </del> | ||
| <em>(this step was removed by a <a href="#change_pr639">candidate correction</a>)</em> | ||
| </li> |
There was a problem hiding this comment.
Should this list item be fully removed now?
index.html
Outdated
| to the result of converting the | ||
| <a>lexical form</a> | ||
| to a JSON <a>number</a>. | ||
| : |
There was a problem hiding this comment.
| : | |
| Then: |
?
|
I cannot assign reviewers, so pinging @pchampin @BigBlueHat @anatoly-scherbakov @iherman to check if this is the wanted change and direction. |
|
What's the process here and timeline for this change? It seems the ins/del markup is useful during the entire 1.2 development, at least in the editors draft. Is the intent to only remove the text for publication, but otherwise retain until 1.2 is finalized? Asking because if the markers are only used short term, then why use at all rather than regular text or semantic diffs? |
It is perfectly possible for editors to use these as part of their work but, afaik, it is hardly ever done. With the lack of proper tools, managing them is the editors' nightmare. (I know it from personal experience.) The only place where it is required per process is when a Recommendation is "maintained" by the WG, i.e., when a Rec is changed without going back to the traditional WD->CR->AC Vote->Rec route. The "living standard" case, as it were. Because, when there are non-editorial substantive changes, the AC still has to approve the changes, the ins/del tool is used for that sole purpose: get the AC vote on the changes. I guess this is why they are part of the 1.2 drafts in the first place. However, under the new charter, 1.2 will undergo the traditional process and, therefore, the usage of those tags is now moot, and they should disappear. (That is the reason why the "living standard" model essentially failed in the W3C: it is a pain in the backside. Other groups choose never to publish a Rec, but leave the specification in a perpetual CR stage.) |
pchampin
left a comment
pchampin
left a comment
There was a problem hiding this comment.
one <del> tag has been treated as an <ins>, line 5518 and following (@davidlehn also noted this in a comment).
Apart from that, looking good.
The next step would be to remove the divs with class="candidate correction", and move their text to the corresponding item in section "Change logs".
| <li id="alg-inv-defaul-base-dir" class="changed"> | ||
| <ins cite="#change_pr639"><em>(this step was removed by a <a href="#change_pr639">candidate correction</a>)</em></ins> | ||
| <del cite="#change_pr639"> | ||
| Otherwise, if <var>active context</var> has a | ||
| <a>default base direction</a>: | ||
| <ol> | ||
| <li>Initialize a variable <var>lang dir</var> | ||
| with the concatenation of <var>default language</var> and <a>default base direction</a>, | ||
| separate by an underscore (`"_"`), | ||
| normalized to lower case.</li> | ||
| <li>If <var>language map</var> does not have a <var>lang dir</var> <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| <li>If <var>language map</var> does not have an `@none` <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| <li>If <var>type map</var> does not have an `@none` <a>entry</a>, | ||
| create one and set its value to the <a>term</a> | ||
| being processed.</li> | ||
| </ol> | ||
| </del> | ||
| <em>(this step was removed by a <a href="#change_pr639">candidate correction</a>)</em> | ||
| </li> |
Co-authored-by: David I. Lehn <dil@lehn.org>
4 participants
This removes all
<ins>and<del>markup in the document. There may still be artefacts left that relate to these, so we may need to think about the scope of this PR (see comments).If I got it right, we want this in preparation for JSON-LD 1.2 working drafts, along with other important changes (title, correct "What's new in 1.2", change use of
class="changed"...). Do we want these other changes in separate PR:s, or a bigger branch for all the prep work?Preview | Diff