Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Compute an additional IC score using only subClassOf. #144

Merged
merged 1 commit into from
Feb 8, 2024
Merged

Compute an additional IC score using only subClassOf. #144

merged 1 commit into from
Feb 8, 2024

Conversation

balhoff
Copy link
Member

@balhoff balhoff commented Feb 8, 2024

No description provided.

@balhoff balhoff merged commit a96c858 into master Feb 8, 2024
1 check passed
@balhoff balhoff deleted the subclass-ic branch February 8, 2024 16:13
dosumis
dosumis reviewed Feb 8, 2024
View reviewed changes
Copy link
Contributor

@dosumis dosumis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@gaurav gaurav mentioned this pull request Feb 12, 2024
Open
@gaurav
Copy link

gaurav commented Feb 12, 2024

Do you think it would be useful to incorporate this into Babel cliques? It sounds like vocab:normalizedSubClassInformationContent might be more common than vocab:normalizedInformationContent, so we could set it up so that we download both sets of predicates and values, then use the normalizedSubClassInformationContent only if there is no normalizedInformationContent present. What do you think? I'm tracking this at Babel at TranslatorSRI/Babel#238

@balhoff
Copy link
Member Author

balhoff commented Feb 12, 2024

@gaurav both values should be present for all terms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dosumis dosumis dosumis left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@balhoff @gaurav @dosumis