Skip to content

Plain name IRI fragments can use unicode #1359

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

Closed
wants to merge 2 commits into from
Closed

Plain name IRI fragments can use unicode #1359

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f4b7306
Plain name IRI fragments can use unicode
handrews Dec 5, 2022
8e52bac
Correct the ABNF
awwright Mar 27, 2023
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
25 changes: 21 additions & 4 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -516,13 +516,30 @@
locally named schemas.
</t>
<t>
Plain name fragments MUST start with a letter ([A-Za-z]) or underscore ("_"),
followed by any number of letters, digits ([0-9]), hyphens ("-"),
underscores ("_"), and periods ("."). This matches the US-ASCII part of XML's
Plain name fragments MUST follow XML's
<xref target="xml-names">NCName production</xref>, which allows for compatibility
with the recommended plain name <xref target="W3C.REC-xptr-framework-20030325">syntax</xref> for
XML-based media types.
XML-based media types. For convenience, the NCName syntax is reproduced here in ABNF form, using
a minimal set of rules:
<cref>
Note that the previous syntax for plain name fragment is a subset of this syntax,
which used only the first line of each of the NCNameStartChar and NCNameChar rules.
</cref>
</t>
<sourcecode type="abnf"><![CDATA[
NCName = NCNameStartChar *NCNameChar

NCNameStartChar = "_" / ALPHA
/ %xC0-D6 / %xD8-F6 / %xF8-2FF
/ %x370-37D / %x37F-1FFF
/ %x200C-200D / %x2070-218F
/ %x2C00-2FEF / %x3001-D7FF
/ %xF900-FDCF / %xFDF0-FFFD
/ %x10000-EFFFF

NCNameChar = NCNameStartChar / "-" / "." / DIGIT
/ %xB7 / %x0300-036F / %x203F-2040
]]></sourcecode>
<t>
All fragment identifiers that do
not match the JSON Pointer syntax MUST be interpreted as
Expand Down