-
Notifications
You must be signed in to change notification settings - Fork 2
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
Introduce semantic versioning on generated rdf #40
Comments
Looking at the implementation, there's the version of the XLSX file itself, but also of the generation code, right? |
andrawaag
added a commit
that referenced
this issue
Oct 5, 2022
Building @joshmoore point I adapted the schema to capture provenance of the source file (xls), the resulting RDF triples and the python script that generates the triples from the provided xls data. |
joshmoore
added a commit
that referenced
this issue
Oct 6, 2022
… file formats." This reverts commit f07fc5a.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #38 an issue with the chosen schema emerged. The fix needed a substantial change that it will probably introduce breaking changes in querying.
I propose to introduce semantic versioning. Since it is intended primarily for software development I propose to following definition when applied on data:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make a completely new schema.
MINOR version when you reshuffle a single branch
PATCH version when you make a change on a single node or triple.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
The text was updated successfully, but these errors were encountered: