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

Jump to bottom

Update [URI] to reference RFC3986 (#504). #505

Merged
merged 3 commits into from
Dec 23, 2017
Merged

Update [URI] to reference RFC3986 (#504). #505

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c592b37
Update [URI] to reference RFC3986 (#504).
skynavga Dec 23, 2017
3f9e4cb
Expand SPACE to XML whitespace characters (#504).
skynavga Dec 23, 2017
f7b9d1c
Merge branch 'master' into issue-0504-update-uri-rfc
skynavga Dec 23, 2017
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
17 changes: 9 additions & 8 deletions spec/ttml2.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1109,7 +1109,7 @@ glyph metrics, and other data used in the character to glyph mapping and renderi
<label>[fragment identifier]</label>
<def>
<p>A syntactic subset of a <loc href="#content-value-uri">&lt;uri&gt;</loc> value that adheres to the
fragment identifer syntax defined by <bibref ref="uri"/>, &sect; 4.1.</p>
fragment identifer syntax defined by <bibref ref="uri"/>, &sect; 3.5.</p>
</def>
</gitem>
<gitem id="terms-glyph-area">
Expand Down Expand Up @@ -6570,7 +6570,6 @@ respectively.</p>
<p>A &lt;supports-function&gt; value expression evaluates to <code>true</code> if the specified feature or extension
designator is (semantically) supported by the <loc href="#terms-content-processor">content processor</loc>.</p>
</div3>

<div3 id="content-value-uri">
<head>&lt;uri&gt;</head>
<p>A &lt;uri&gt; value expression is used to specify a URI <bibref ref="uri"/>.</p>
Expand All @@ -6588,10 +6587,12 @@ designator is (semantically) supported by the <loc href="#terms-content-processo
</tbody>
</table>
<p>The value syntax of the <code>xsd:anyURI</code> data type must adhere to the definition specified by <bibref ref="xsd-2"/>, &sect;3.2.17.</p>
<note role="clarification"><p>For avoidance of doubt, characters designated to be excluded in a URI by <bibref ref="uri"/>, &sect;2.4.3,
<emph>Excluded US-ASCII Characters</emph>, do not appear in an unescaped form in the lexical representation of a <code>&lt;uri&gt;</code> value.</p></note>
<note role="clarification">
<p>For avoidance of doubt, characters designated to be excluded in a URI by <bibref ref="uri"/>, &sect;2,
<emph>Characters</emph>, and, more specifically, SPACE (U+0020) characters,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why call out SPACE characters particularly?

Copy link
Collaborator Author

@skynavga skynavga Dec 23, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In RFC2396, the following were explicitly excluded in 2.3.4 (meaning they are escaped)

control     = <US-ASCII coded characters 00-1F and 7F hexadecimal>
space       = <US-ASCII coded character 20 hexadecimal>

while these are not explicitly excluded in the RFC3986 in section 2 (though perhaps one may consider this implied).

But I see that calling out SPACE alone is not sufficient, and I really want all XML whitespace characters, so I am elaborating this point in the newest commit in this branch, which perhaps you can approve.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I never got the chance to approve this or not since you merged it so quickly, but I'm fine with it as luck has it. If you're going to ask me to approve though, it'd be polite to give me the opportunity to do so!

do not appear in an unescaped form in the lexical representation of a <code>&lt;uri&gt;</code> value.</p>
</note>
</div3>

</div2> <!-- content-value-expressions -->
</div1> <!-- content -->
<div1 id="embedded-content">
Expand Down Expand Up @@ -24946,9 +24947,9 @@ href="http://www.unicode.org/reports/tr14/tr14-17.html">http://www.unicode.org/r
</bibl>
<bibl id="uri" key="URI">T. Berner-Lee, R. Fielding, and L. Masinter,
<titleref
href="http://www.rfc-editor.org/rfc/rfc2396.txt">Uniform Resource Identifiers (URI): Generic Syntax</titleref>,
RFC 2396, August 1998, IETF. (See
<xspecref href="http://www.rfc-editor.org/rfc/rfc2396.txt">http://www.rfc-editor.org/rfc/rfc2396.txt</xspecref>.)
href="http://www.rfc-editor.org/rfc/rfc3986.txt">Uniform Resource Identifiers (URI): Generic Syntax</titleref>,
RFC 3986, January 2005, IETF. (See
<xspecref href="http://www.rfc-editor.org/rfc/rfc3986.txt">http://www.rfc-editor.org/rfc/rfc3986.txt</xspecref>.)
</bibl>
<bibl id="utc" key="UTC">
Recommendation TF.460-6,
Expand Down