-
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
Remove state and unknown elements #922
Labels
Comments
robander
added a commit
to robander/dita
that referenced
this issue
Jun 11, 2024
robander
added a commit
to robander/dita
that referenced
this issue
Jun 11, 2024
robander
added a commit
to robander/dita
that referenced
this issue
Jun 11, 2024
robander
added a commit
to robander/dita-techcomm
that referenced
this issue
Jun 11, 2024
robander
added a commit
to oasis-tcs/dita-techcomm
that referenced
this issue
Jun 11, 2024
Remove unknown element oasis-tcs/dita#922
robander
added a commit
to robander/dita
that referenced
this issue
Jun 11, 2024
robander
added a commit
to robander/dita
that referenced
this issue
Jun 11, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on discussion at today's TC meeting (June 11 2024), and coming out of the review of "specialization elements" section of elements, we will be removing the following elements from 2.0:
<state>
element -- migration path is to use<data>
for 1 to 1 migration if using metadata (both@name
and@value
are present), OR alternate migration path to use<ph>
or<keyword>
if using this for content (@value
will go into element content in the specialized element)The text was updated successfully, but these errors were encountered: