Skip to content

Commit eae1a18

Browse files
ioggstreamgkellogg
authored andcommitted
Stub for security, interoperability and fragment identifier considerations.
1 parent 198f470 commit eae1a18

File tree

1 file changed

+32
-1
lines changed

1 file changed

+32
-1
lines changed

spec/index.html

Lines changed: 32 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -265,5 +265,36 @@ <h2>Basic Concepts</h2>
265265

266266
<p>FIXME.</p>
267267
</section>
268-
</body>
268+
269+
<section id="sec" class="informative">
270+
<h2>Security Considerations</h2>
271+
272+
<p>See the YAML media type registration.</p>
273+
</section>
274+
275+
<section id="int" class="informative">
276+
<h2>Interoperability Considerations</h2>
277+
278+
<p>
279+
For general interoperability considerations on the serialization of
280+
JSON documents in YAML, see [[YAML]].
281+
</p>
282+
283+
</section>
284+
285+
<section id="int" class="informative">
286+
<h2>Fragment identifiers</h2>
287+
288+
<p>
289+
YAML media type support both alias nodes and JSON Pointer [[RFC6905]]
290+
as fragment identifiers (see [[I-D.httpapi-yaml-mediatypes]]).
291+
Since named anchor are serialization details, when
292+
using alias nodes to reference nodes in external documents
293+
the implementation needs to be confident that the serialization of
294+
the resource is preserved.
295+
</p>
296+
297+
</section>
298+
299+
</body>
269300
</html>

0 commit comments

Comments
 (0)