@@ -12229,11 +12229,16 @@ <h3>Examples</h3>
12229
12229
< section id ="security " class ="appendix ">
12230
12230
< h3 > Security Considerations</ h3 >
12231
12231
< p > See, < a href ="#iana-security "> Security Considerations</ a > in < a href ="#iana-considerations " class ="sectionRef "> </ a > .</ p >
12232
+ < p > Future versions of this specification
12233
+ may incorporate subresource integrity [[?SRI]] as a means of ensuring that cached and retrieved
12234
+ content matches data retrieved from remote servers; see < a href ="https://github.com/w3c/json-ld-syntax/issues/86 "> issue 86</ a > .</ p >
12232
12235
</ section >
12233
12236
12234
12237
< section id ="privacy " class ="appendix ">
12235
12238
< h3 > Privacy Considerations</ h3 >
12236
- < p > The retrieval of external contexts can expose the operation of a JSON-LD processor
12239
+ < p > The retrieval of external contexts can expose the operation of a JSON-LD processor,
12240
+ allow intermediate nodes to fingerprint the client application through introspection of retrieved resources
12241
+ (see [[?fingerprinting-guidance]]), and
12237
12242
and provide an opportunity for a man-in-the-middle attack.
12238
12243
To protect against this, publishers should consider caching remote contexts for future use,
12239
12244
or use the < a data-cite ="JSON-LD11-API#dom-jsonldoptions-documentloader "> documentLoader</ a >
@@ -12246,13 +12251,14 @@ <h3>Internationalization Considerations</h3>
12246
12251
properly record < a > JSON-LD Values</ a > which are < a > strings</ a > with left-to-right or right-to-left direction indicators.
12247
12252
Both JSON-LD and RDF provide a mechanism for specifying the language associated with
12248
12253
a string (< a > language-tagged string</ a > ), but do not provide a means of indicating
12249
- the direction of the string.</ p >
12254
+ the base direction of the string.</ p >
12250
12255
12251
12256
< p > Unicode provides a mechanism for signaling direction within a string
12252
12257
(see < a data-cite ="UAX9 "> Unicode Bidirectional Algorithm</ a > [[UAX9]]),
12253
12258
however, when a string has an overall base direction which cannot be determined by the
12254
12259
beginning of the string, an external indicator is required,
12255
- such as the [[HTML]] < a data-cite ="HTML/dom.html#the-dir-attribute "> dir attribute</ a > .</ p >
12260
+ such as the [[HTML]] < a data-cite ="HTML/dom.html#the-dir-attribute "> dir attribute</ a > ,
12261
+ which currently has no counterpart for < a > RDF literals</ a > .</ p >
12256
12262
12257
12263
< p > The issue of properly representing text direction in RDF is not something that
12258
12264
this Working Group can handle, as it is a limitation or the core RDF data model.
@@ -12262,7 +12268,9 @@ <h3>Internationalization Considerations</h3>
12262
12268
< p > Until a more comprehensive solution can be addressed in a future version of this
12263
12269
specification, publishers should consider this issue when representing strings
12264
12270
where the text direction of the string cannot otherwise be correctly inferred
12265
- based on the content of the string.</ p >
12271
+ based on the content of the string.
12272
+ See [[?string-meta]] for a discussion best practices for
12273
+ identifying language and base direction for strings used on the Web.</ p >
12266
12274
</ section >
12267
12275
12268
12276
< section class ="appendix informative preserve ">
0 commit comments