Include OpenTeacher version number in file format

Registered by Milan Boers

To make more drastic changes to the OpenTeacher file format (like https://blueprints.launchpad.net/openteacher/+spec/seperateresults), while keeping compatibility with old versions of the file format, the OpenTeacher XML file should include the OpenTeacher version number, so files that were made in older versions can be openend with other code.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
Marten de Vries
Definition:
Approved
Series goal:
Accepted for 3.x
Implementation:
Implemented
Milestone target:
milestone icon 3.0
Started by
Marten de Vries
Completed by
Marten de Vries

Related branches

Sprints

Whiteboard

Discussion:

~marten-de-vries: Isn't it possible to just use elements in the xml-file when they are supported? That's one of the ideas behind XML I thought. I understand it isn't possible to do this for really big changes, but we can think about doing one redesign of the file format ( with a new extension perhaps? ), and after that using that strategy. It doesn't matter if OT shows an error because of wrong content or because it's a new unsupported version.

UPDATE: JSON is a bit less extendable, maybe a version number would be nice. On the other hand, just using duck typing might work out too.

UPDATE: We'lll do it.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.