Response to the Privacy & Security Self-Review Questionnaire for the RDF specifications

[pchampin]

Privacy & Security Self-Review Questionnaire

https://www.w3.org/TR/security-privacy-questionnaire

2.1 What information does this feature expose, and for what purposes?

→As a generic data model, RDF in itself or its implementations do not expose any information. The information represented in RDF, and for what purpose, is application-dependent.

2.2 Do features in your specification expose the minimum amount of information necessary to implement the intended functionality?

→Cf. 2.1.

2.3 Do the features in your specification expose personal information, personally-identifiable information (PII), or information derived from either?

→Cf. 2.1.

2.4 How do the features in your specification deal with sensitive information?

→Cf. 2.1.

2.5 Does data exposed by your specification carry related but distinct information that may not be obvious to users?

→Cf. 2.1.

2.6 Do the features in your specification introduce state that persists across browsing sessions?

→No

2.7 Do the features in your specification expose information about the underlying platform to origins?

→No

2.8 Does this specification allow an origin to send data to the underlying platform?

→No

2.9 Do features in this specification enable access to device sensors?

→No

2.10 Do features in this specification enable new script execution/loading mechanisms?

→No

2.11 Do features in this specification allow an origin to access other devices?

→No

2.12 Do features in this specification allow an origin some measure of control over a user agent’s native UI?

→No

2.13 What temporary identifiers do the features in this specification create or expose to the web?

→No

2.14 How does this specification distinguish between behavior in first-party and third-party contexts?

→The RDF family of specification is independent from browsers, and therefore the notions of first-party and third-party context do not apply.

2.15 How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?

→N/A, cf. 2.14.

2.16 Does this specification have both "Security Considerations" and "Privacy Considerations" sections?

→Yes

2.17 Do features in your specification enable origins to downgrade default security protections?

→No, cf. 2.14.

2.18 What happens when a document that uses your feature is kept alive in BFCache (instead of getting destroyed) after navigation, and potentially gets reused on future navigations back to the document?

→N/A, cf. 2.14.

2.19 What happens when a document that uses your feature gets disconnected?

→N/A, cf. 2.14.

2.20 Does your spec define when and how new kinds of errors should be raised?

→RDF specifications define error conditions when parsing documents in concrete syntaxes, but these error conditions depend exclusively on the data being parsed, not on the user’s context. Therefore, they should not represent a security or privacy issue.

2.21 Does your feature allow sites to learn about the user’s use of assistive technology?

→No

2.22 What should this questionnaire have asked?

→No suggestion.

Scope

This self-assessment applies to the whole family of RDF 1.2 specifications:

• RDF12-NEW
• RDF12-CONCEPTS
• RDF12-N-QUADS
• RDF12-N-TRIPLES
• RDF12-PRIMER
• RDF12-SCHEMA
• RDF12-SEMANTICS
• RDF12-TRIG
• RDF12-TURTLE
• RDF12-XML