Skip to content

fix: added more details regarding direction and empty string #179

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

Merged
merged 1 commit into from
Feb 1, 2025
Merged

fix: added more details regarding direction and empty string #179

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
3 changes: 3 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,6 +255,9 @@ <h3><dfn>Literal</dfn> interface</h3>
<p>
<dfn>direction</dfn> is not falsy if the string is a directional language-tagged string.
In this case, the <code>direction</code> MUST be either be <code>"ltr"</code> or <code>"rtl"</code>.
Implementations supporting this feature should use an empty string when no direction is given.
<code>null</code> or <code>undefined</code> values are allowed to maintain compatibility with legacy
implementations.
</p>
<p>
<dfn>datatype</dfn> a <code>NamedNode</code> whose IRI represents the datatype of the literal.
Expand Down