[wp-trac] [WordPress Trac] #51092: Create a JSON schema for Privacy and Other Related Disclosures

[WordPress Trac]

#51092: Create a JSON schema for Privacy and Other Related Disclosures
----------------------------------------------+-----------------------
 Reporter:  carike                            |       Owner:  (none)
     Type:  feature request                   |      Status:  new
 Priority:  normal                            |   Milestone:  5.6
Component:  Privacy                           |     Version:
 Severity:  normal                            |  Resolution:
 Keywords:  needs-privacy-review 2nd-opinion  |     Focuses:  rest-api
----------------------------------------------+-----------------------

Comment (by azaozz):

 Replying to [comment:30 TimothyBlynJacobs]:
 > I'll leave that for the privacy team. My point about using JSON schema
 is it provides us a good way to validate that if we do want structured
 data, which I think is the privacy team's goal.

 Right. This question was raised when the initial discussion happened,
 around two years ago if I'm not mistaken, and don't think there's been a
 clear answer yet.

 > Why should it not be? If it is made available over the REST API, it is
 easier for other consumers to access that data. It'd also make it easier
 for a React powered front-end. It being available over the REST API also
 doesn't preclude it from being accessed in different ways as well.

 I'm still thinking we're talking apples and oranges here :)

 - Where the data that needs validation comes from? Static file(s), one
 supplied by core and (eventually) a few supplied by plugins.
 - When should the validation happen? On every request of... what? Or once
 after a plugin is installed and then the result is saved in the DB? Or....
 how is that going to work efficiently?
 - What happens when the validation fails? The plugin supplying the data
 is... rejected (deleted, disabled, or... rejected how)?
 - Does it make sense for such validation to be in core at all, or maybe
 better to be on accepting plugins to the plugins directory, or..?
 - What happens then the schema needs to be changed? Re-validation?

 Generally validating static, non-editable files in core seems... unwise?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51092#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform