solid
Resource Revisions
Is there a standard way to represent resource revisions, e.g. like a wiki or more like a git revgraph?
{"@type": "schema:Thing",
"__:revid": "...",
"__:parents": [ ],
"__:schemaVersion": "0.1"
}
- This segues into moderation log resolution.
I'm not sure. I think the closest thing that comes to that is the Prov ontology.
You might also find it helpful to look at:
- the Memento protocol
- (especially) DAT project's Decentralized Archive Transport (Dat) protocol
Just a thought: could we imagine a new kind of container (a "versioning container") in which each PUT of a resource would automatically create a new revision of this resource ?
@zoggy sure, we've been wanting something like this for a while. So, it's definitely on the medium-term roadmap.
@dmitrizagidulin thanks. IIUC, memento and DAT solve for resource-revisions on-top-of an existing thing with an HTTP interface.
Maybe a wiki would be a good use case.
Use cases / applications where this feature would be {useful, tested, necessary}:
- A wiki with revisions (e.g. just like mediawiki)
... As an aside, the OpenAnnotation / Web Annotation specs are designed to be "fuzzy" enough so that in-text annotations will stay anchored to the same place when the other page content changes (so, for e.g. mediawiki, Hypothesis comments may or may not be a substitute for a Talk page)