Add migration scripts for version 12

[rjyounes]

@Jamie-SA I was thinking this would be a good issue for @coltonglasgow to work on, if he has the bandwidth. What do you think?

Here I am listing all issues that show up in the Release Project

• precedes/follows - nothing to do (seems nothing was done or it was done previously) - part of removing inverses, so included in additional
• Integrate new rdf-toolkit - nothing to do
• Scope note adjusments on domainIncludes and rangeIncludes - nothing to do
• Upgrade rdf-toolkit.jar to version 1.14.2 to suppress NamedIndividual assertions - nothing to do
• pre-commit hook not running - nothing to do
• Define unit of measure for percent - nothing to do - goes with issue Representing Percents #785
• Add windows support to setup - nothing to do
• Representing Percents - Removed class gist:Percentage

For each case where a gist:Precentage object with just a gist:numericValue ${value} exists, could we create a gist:Magnitude with gist:hasUnitOfMeasure gist:_percent and gist:numericValue ${value}? For all other cases, we could warn the user that they are using a deprecated class and we couldn't automatically convert it.

• Adapt tools/setup.sh for Windows users - nothing to do
• Small modifications to bundle.yaml - nothing to do
• Update skos:definition of gist:nonConformingLabel - nothing to do
• Reword definition of gist:nonConformingLabel - nothing to do
• Remove references to gistDeprecated from bundle.yaml - nothing to do
• Issues relating to TimeZone and TimeZoneStandard - report/warn if being used YES - also properties that were removed
• Remove Inverses - report/warn about usage of removed properties.

Remove existing triples and add the ones with inverses, reversing the subject and object? In the ontology, you would need to change restrictions owl:onProperty <deleted-property> to owl:onProperty [ owl:inverseOf ]`. Same for domains and ranges.

• Fix Project and Task - See below
• Rework Event and Task Classes - Report/warn using removed classes and update changed classes
• Update annotations on gist:isAllocatedBy - nothing to do
• Added TimeInterval class - nothing to do
• Remove distinction between Intergovernmental Organization Treaty Organization - replace gist:TreatyOrganization with gist:IntergovernmentalOrganization
• Removed dateTime restrictions from Contingent Event - Nothing to do
• Explicitly defined subClassOf - nothing to do
• Broaden text definition of gist:isAllocatedBy - nothing to do

In Review Tasks:

• Shouldn't gist use a PURL for its namespace IRI?
  • Change gist namespace from https://ontologies.semanticarts.com/gist/ to https://w3id.org/semanticarts/gist/ in instance data
  • Change gist ontology IRIs in all ontology files from https://ontologies.semanticarts.com/o/gist* to https://w3id.org/semanticarts/gist*

  Update gist prefix on all classes and properties (warn first)
  Maybe break this out into separate queries for s, p, o, and g separated by semi colons

[rjyounes]

@Jamie-SA I made an initial pass through this and x'ed out some items, removed question marks, and added some TBDs which I have to look at later.

For terms that are being removed, do you typically issue only a warning?

[Jamie-SA]

For terms that are being removed, do you typically issue only a warning?

It depends. If there is no replacement then that is about all we can do. In the case of removing an inverse property we could suggest changes or actually update data (or provide the update query) to use the inverse instead.

[coltonglasgow]

[ ] Representing Percents - Removed class gist:Percentage

@Jamie-SA, for each case where a gist:Precentage object with just a gist:numericValue ${value} exists, could we create a gist:Magnitude with gist:hasUnitOfMeasure gist:_percent and gist:numericValue ${value}? For all other cases, we could warn the user that they are using a deprecated class and we couldn't automatically convert it.

[uscholdm]

[ ] Representing Percents - Removed class gist:Percentage

@Jamie-SA, for each case where a gist:Precentage object with just a gist:numericValue ${value} exists, could we create a gist:Magnitude with gist:hasUnitOfMeasure gist:_percent and gist:numericValue ${value}? For all other cases, we could warn the user that they are using a deprecated class and we couldn't automatically convert it.

There never was a unit gist:_percent, do we have one now with a conversion of .01 to base (gist:_each). I tihnk that is correct, but ti was never the way we did things. IF we do, then I think your suggestion make sense. It would be good to see sample triepls input and output to/from the script.

M.

[rjyounes]

Yes, gist:_percent got added along with the removal of gist:Percentage.

[coltonglasgow]

@Jamie-SA, I have updated the task list above with action items. Please review the updated list with proposed migrations. Once approved, I will begin working on the migrations.

[stevenchalem]

@uscholdm, would you be able to approve the pull request(s), since @rjyounes is out of the office?

[uscholdm]

I would not be able to judge whether the scripts are good. Better to ask a developer