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.

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

Inconsistent use of the word 'plurality' in the annotations of 'object aggregate' #109

Open
avsculley opened this issue Sep 22, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@avsculley
Copy link

avsculley commented Sep 22, 2024

In the skos:definition plurality seems to mean greater than or equal to 1 whereas in the second skos:scopeNote it seems to mean greater than 1.
Screenshot 2024-09-22 at 11 19 11 AM

I am, of course, happy to submit a PR fixing this issue, if permitted. I think the fix is just to change the greater than or equal to symbol in the def to a greater than symbol.

@avsculley avsculley added the bug Something isn't working label Sep 22, 2024
@alanruttenberg
Copy link
Contributor

The definition says there is >= 1, and the scopenote clarifies that if there is only one, then at some other time there must be more than one.
If anything the Elucidation could be rewritten to reflect that membership is time dependent, or that a plurality (in the strict sense that plural means more than one) obtains at some time. Something like

An object aggregate is a material entity with one or more member parts at all times, and more than one member part at some time.

But I don't see the bug as stated. The second scopeNote says explicity that at some times there can be only one object, so I don't see how you can conclude >1

@avsculley
Copy link
Author

avsculley commented Sep 26, 2024

It says "but must at some time have a plurality of member parts" here it means more than one.

If the correct way to use plurality is to mean greater than or equal to one, then the scope note shouldn't use it to mean more than one.

I think your suggested fix works, since 'plurality' is no longer used in the def, and thus no longer means two different things across the annotation properties. Admittedly, my suggestion only fixed the use of the word 'plurality' whereas yours does that, and improves the model such that an important aspect of it is no longer relegated to the scope note.

@alanruttenberg
Copy link
Contributor

The correct use of plurality is greater than one. It's the definition that should be amended. Suggested:

An object aggregate is a material entity usually consisting of a plurality of objects as member parts, although at some times only a single object, which together form a unit.

For Barry to resolve.

@alanruttenberg alanruttenberg assigned phismith and unassigned johnbeve Sep 27, 2024
@phismith
Copy link

phismith commented Sep 27, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants