-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup items: removing obsolete markup #397
Comments
Remove audience/@othertype, audience/@otherjob, itemgroup #397
Change base of itemgroup to div oasis-tcs/dita#397
Based on discussion of this email on Dec 8 2020: https://lists.oasis-open.org/archives/dita/202012/msg00008.html Adding the |
Not a removal, but based on discussion at TC May 11, another cleanup item will restore the universal-attributes to specializations of body (missing as an oversight for several releases, ever since those elements were made optional): https://lists.oasis-open.org/archives/dita/202104/msg00020.html |
Per discussion at TC May 18 2021, agreed to remove |
Replace sectiondiv with div oasis-tcs/dita#397
Additional cleanup coming out of TC meeting June 1 2021:
|
Remove longquoteref topic, add keyref to highlight elements #397
Add keyref to xml, markup elements oasis-tcs/dita#397
Per TC meeting November 2, 2021, |
Per TC meeting January 11, 2011, voted to remove several obsolete items:
|
Removing the following attributes from object, which are deprecated in HTML5 (including the "keyrefs" DITA version of removed attributes): |
Same update for |
Realized that |
At the TC meeting on 24 May 2022, we decided to remove the title attribute on reltable element |
…posal-647 * 'DITA-2.0' of https://github.com/oasis-tcs/dita: Remove title att from reltable oasis-tcs#397 Update source files in preparation for review 0: accessibility Clean up draft comments in a11y topics
From recent TC meetings: Removing enumeration so that any value is allowed for scale attribute, keeping enumerations only for |
Per TC meeting June 14 2022, Eliot Kimber will be writing up the after-the-fact stage 3 proposal for this item. |
Remove enumeration for scale, apart from table #397
Relax scale values except simpletable oasis-tcs/dita#397
…posal-647 * 'DITA-2.0' of https://github.com/oasis-tcs/dita: Incorporate edits from review O Update cover page metadata Update spec source for scale att oasis-tcs#397 Remove enumeration for scale, apart from table oasis-tcs#397 Incorporate edits from review O Correct typs Add rev marking for "review-o" Adds link from accessibility topic to WCAG Incorporate review comments from Bob Johnson Add "Closed" as a permitted value for disposition on <draft-comment> Adds rev attribute value for review O Revert "Adds draft comments from Content Fusion review" Adds draft comments from Content Fusion review Add bindings for disposition attr on draft-comment Edited new expansion topics (work in progress) Typo fix in heading replaced "DITAweb" with "Congility Web Server" as detailed in draft comment # Conflicts: # specification/resources/DITA2.0-spec.ditaval
Working on the proposal now |
Proposal reviewed and updated. Submitted for TC review 17 Oct 2022 |
To ensure full compatibility with DITA 2.0, the reference to a `<sectiondiv>` should be switched to a `<div>`. I've left `<sectiondiv>` processing in as well for backward compatibility to DITA 1.4. > Per discussion at TC May 18 2021, agreed to remove `<sectiondiv>` which is a subset of functionality now available with `<div>`. _Originally posted by @robander in oasis-tcs/dita#397 (comment)
As discussed at TC meeting October 20, 2020, as we get more deeply into editing the 2.0 spec we're finding items that are really obsolete and no longer needed. Many of these should have been marked deprecated in 1.3 or earlier, but were not noticed.
We will be treating these as fixes, but need to track to make sure that they are included in any migration instructions.
Items added to the list initially:
@othertype
and@otherjob
on<audience>
are obsolete and can be removed<itemgroup>
is no longer useful, its function can be entirely filled by the<div>
elementThe text was updated successfully, but these errors were encountered: