Skip to content

Release 9.1.0 #192

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

Merged
merged 2 commits into from
Mar 1, 2020
Merged

Release 9.1.0 #192

merged 2 commits into from
Mar 1, 2020

Conversation

sa-bpelakh
Copy link
Collaborator

I removed gistWiki, as discussed, and reformatted ReleaseNotes as Markdown, adding a 9.1.0 section.

@sa-bpelakh sa-bpelakh requested a review from rjyounes February 28, 2020 23:17
@sa-bpelakh
Copy link
Collaborator Author

This will also close #123

@rjyounes rjyounes merged commit a03b4bb into develop Mar 1, 2020
@rjyounes rjyounes deleted the release-9.1.0 branch March 1, 2020 18:20
@uscholdm
Copy link
Contributor

uscholdm commented Mar 3, 2020

I just took a good look at all the changes from 9.0.0 and noticed a large number of changes with disjoints. I do not recall any discussions about that. The affected file is gistTop. They all came in with commits by Rebecca on Jan 29 relating to Issue 153. But that issues does not mention disjoints. I searched through all the issues around then and none mention disjoints. So how the heck did this happen?

A lot of the changes are dubious. Here are a few:

  • A geopoint can now be an intention
  • a magnitude can now be a language
  • an organization can also now be a language
  • a PhysicalIdentifiableItem can now be an Organization

Michael

@uscholdm
Copy link
Contributor

uscholdm commented Mar 3, 2020

I looked into this a bit further. The file compare seems to say that a geopoint used to be but no longer is disjoint with an intention. Similar for the other examples. However, when I load the ontology, the disjoints seem correct. So the question becomes:

  • when I look at the file comparison, why does it seem like disjoints have moved all over the place?

It rather defeats the purpose of looking at file differences.

@sa-bpelakh
Copy link
Collaborator Author

@uscholdm Michael, I think one of the changes that was made during this release is a more consistent reformat of the files. It should improve things going forward, but may have resulted in some weird diffs for this release. As long as it is sound when loaded, we should be good for now.

@rjyounes
Copy link
Collaborator

rjyounes commented Mar 3, 2020

@sa-bpelakh I haven't looked at the files, but why would reformatting cause changes to disjointness axioms? And does this mean that if we use ontology-toolkit instead of the old serializer in our projects we should expect a lot of reformatting on the first run?

@sa-bpelakh
Copy link
Collaborator Author

@rjyounes I don't think the serializer changed the axioms, it just made the diffs less obvious. We can examine the specific axioms Michael is referencing to validate that they have not changed.

The commit hooks on the repo should use the serializer - if you see non-clean diffs in a pull request, that is usually the cause. The bundle functionality in ontology-toolkit that I use to package the release re-runs the standard serializer on each OWL file, just to be sure.

@rjyounes
Copy link
Collaborator

rjyounes commented Mar 3, 2020

@uscholdm @sa-bpelakh OK, who is going to examine the files?

@uscholdm
Copy link
Contributor

uscholdm commented Mar 3, 2020

The commit hooks on the repo should use the serializer
We need to ensure that everyone has it set up, and is using the exact same .jar file.

@uscholdm
Copy link
Contributor

uscholdm commented Mar 3, 2020

Another thing that would be nice to have in our ontology toolkit is a script that mushes all the gist files into one ontology. Then we could use Protégé to do an ontology compare. Dean Allemang did this for his work. Neat trick.

@uscholdm
Copy link
Contributor

uscholdm commented Mar 3, 2020

I haven't looked at the files, but why would reformatting cause changes to disjointness axioms?

I don't get it either. I also saw one of the commits that did a fresh serialize, and I did my compare from there to 9.1 hoping the disjoint differences would go away. Did not work, they were still there.

@rjyounes
Copy link
Collaborator

rjyounes commented Mar 3, 2020

@uscholdm @Jamie-SA @sa-bpelakh I am going to contact Jamie and ask him not to post the new files until we sort this out.

@rjyounes
Copy link
Collaborator

rjyounes commented Mar 3, 2020

@sa-bpelakh As the release manager, it would be up to you to figure this problem out. Do you have the bandwidth? I know you are traveling. We can postpone the release until you are back home.

@Jamie-SA
Copy link
Contributor

Jamie-SA commented Mar 3, 2020

I had done most of the release. I will undo the easy parts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants