-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable view of previous versions of competencies and frameworks, and rollback. #499
Comments
As far as I am concerned, this relates to CredentialEngine/Schema-Development#563 on ghosting and that any solution should be navigable (i.e., linked data). |
I agree, though I do question if history tracking should be at the level of the data schema instead of at the data format or system / content-negotiation / protocol level. Taking into account what you said about the value of describing what things were vs now, this probably warrants a substantial discussion. Git, for instance, has methods of describing what things were and how they have changed in great detail, and it is schema and format neutral, It'd need some sort of content negotiation layer to be HTTP compliant, but illustratively, that makes some sense. |
This needs a synchronous discussion with Jeanne present. |
Method: The owner of an object should be able to retrieve its history (the part of the history that the owner was an owner). Affects: Eduworks/ec#35 |
Can this be closed? |
We haven't started work on this yet. |
Will require ways to explore versioning. See referenced issues.
The text was updated successfully, but these errors were encountered: