Skip to content

Commit

Permalink
style: Apply Prettier
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Sep 22, 2023
1 parent 5b1d4fa commit 36dee5f
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions exploration/0475-overriding-extending-namespacing.md
Original file line number Diff line number Diff line change
Expand Up @@ -271,23 +271,24 @@ _What other properties they have?_
### Choice of namespace separator
The choice of the `:` character as a separator is, as noted above, a considered part
of the design, but it is not required.
of the design, but it is not required.
Other characters are possible for the same purpose.
A concern is that `name-char` reserves `:`, `-`, and `.`, which are probably the
most likely candidates.
most likely candidates.
Choosing one of these characters would require altering the `name-char` (and
thus `name`) production.
Moving to use `NCName` instead of `Nmtoken` as a basis for `name` would address
the use of `:`.
Moving to `-` or `.` would not require alterations of the syntax if we decided
that namespacing is not formally a part of the specification but, rather, is
that namespacing is not formally a part of the specification but, rather, is
just a convention.
Of the remaining characters not currently in use, the most obvious candidates would
be `/` and `~`.
be `/` and `~`.
> Here are examples of the options:
>
> ```
> {$today :ns:function ns:option=foo}{+ns:a}{-ns:a}
> {$today :ns-function ns-option=foo}{+ns-a}{-ns-a}
Expand Down

0 comments on commit 36dee5f

Please sign in to comment.