Skip to content

Fix for issue #2876: deprecate the use of valList as a direct child of elementSpec #2886

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.

Sign up for GitHub

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

Open
martindholmes wants to merge 1 commit into
base: dev
Choose a base branch
from
+7 −0
Open

Fix for issue #2876: deprecate the use of valList as a direct child of elementSpec #2886

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions P5/Source/Specs/elementSpec.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,13 @@
</elementSpec>
</egXML>
</exemplum>
<remarks xml:lang="en" versionDate="2026-04-16" validUntil="2027-09-01">
<p><gi>elementSpec</gi> currently allows <gi>valList</gi> as a direct child,
but this usage is deprecated and will be removed on 2027-09-01.
If a <gi>valList</gi> is used to specify the content model of an element,
it should be placed inside the <gi>content</gi> child of the
<gi>elementSpec</gi>.</p>
</remarks>
<listRef>
<ptr target="#TDTAG"/>
<ptr target="#TD"/>
Expand Down
Loading