Page MenuHomePhabricator

Use draft 4 of JSON Schema specification
Closed, DuplicatePublic

Description

This is a tracking bug for migrating EventLogging to version 4 of the JSON Schema specification.

Completion of this enhancement is contingent on implementing and/or verifying support in mediawiki-jsondata, python-jsonschema and EventLogging's JavaScript code.


Version: unspecified
Severity: enhancement
URL: http://tools.ietf.org/html/draft-zyp-json-schema-04

Details

Reference
bz44809

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:14 AM
bzimport set Reference to bz44809.
bzimport added a subscriber: Unknown Object (MLST).
ori created this task.Feb 9 2013, 4:08 AM

[moving from MediaWiki extensions to Analytics product - see bug 61946]

Restricted Application added a project: Analytics. · View Herald TranscriptDec 5 2017, 2:00 PM
phuedx added a comment.EditedDec 5 2017, 2:12 PM

Per T182000#3809548, the server-side JSON Schema validators support draft 3 of JSON Schema. AFAICT this is not the case for the client-side validator.

Wow, I didn't know this task existed. I have so many desires and ideas on how to make all EventLogging schemas way better. The EventLogging python codebase supports draft 4, you just have to declare it in your schema. However, the tricky bit is the EventCapsule, as it is the 'meta' schema that contains the event schemas, and it is the one that declares the JSONSchema version.

I'd really love to get rid of the EventCapsule altogether one day. BTW: https://wikitech.wikimedia.org/wiki/User:Ottomata/Stream_Data_Platform

fdans edited projects, added Analytics-Kanban; removed Analytics.Dec 11 2017, 5:08 PM
Nuria edited projects, added Analytics; removed Analytics-Kanban.Mar 22 2018, 4:18 PM