Skip to content
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

Issue2525 parsing syntactical #2793

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Issue2525 parsing syntactical #2793

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0b863bf
Adding syntactical
alastc Nov 15, 2022
3f6e89d
Adding syntactical
alastc Nov 15, 2022
1eaad46
More specific
alastc Nov 15, 2022
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
2 changes: 1 addition & 1 deletion guidelines/sc/20/parsing.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ <h4>Parsing</h4>
<p class="conformance-level">A</p>

<p>In content implemented using markup languages, elements have complete start and end
tags, elements are nested according to their specifications, elements do not contain
tags, elements are nested according to the syntactical rules of their specifications, elements do not contain
duplicate attributes, and any IDs are unique, except where the specifications allow
these features.
</p>
Expand Down
8 changes: 5 additions & 3 deletions understanding/20/parsing.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,15 @@ <h2>Intent of Parsing</h2>
<p>Since repair techniques vary among user agents, authors cannot assume that content
will be accurately parsed into a data structure or that it will be rendered correctly
by specialized user agents, including assistive technologies, unless the content is
created according to the rules defined in the formal grammar for that technology.
created according to the syntactical rules defined in the formal grammar for that technology.
In markup languages, errors in element and attribute syntax and
failure to provide properly nested start/end tags lead to errors that
prevent user agents from parsing the content reliably.
Therefore, the Success Criterion requires that the content can be parsed using only
the rules of the formal grammar.

the rules of the formal grammar.</p>

<p>
Markup languages have several types of requirement, this criterion is focused on the syntactical aspects. Some specifications (e.g. HTML) also include the "content model" which is about which elements can go inside other elements. The content model is not in the scope of this criterion.
</p>

<div class="note">
Expand Down