8000 Conflict between Image and Imaging Instrument definitions · Issue #666 · CommonCoreOntology/CommonCoreOntologies · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Conflict between Image and Imaging Instrument definitions #666

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
Open
gregfowlerphd opened this issue May 12, 2025 · 0 comments
Open

Conflict between Image and Imaging Instrument definitions #666

gregfowlerphd opened this issue May 12, 2025 · 0 comments

Comments

@gregfowlerphd
Copy link
Contributor

The definition for the former class reads:

An Information Bearing Artifact that is designed to carry an Information Content Entity that represents some entity owing to a visual isomorphism between the carrying artifact and the entity.

However, the definition for the latter--

A Material Artifact that is designed to produce images (visual representations) of an entity.

--appears to contain a different definition of the term ‘image’, according to which an image is simply a visual representation.

Presumably this sort of conflict ought to be avoided. Perhaps in this case this can be done by modifying the Imaging Instrument definition as follows:

A Material Artifact that is designed to produce Images of an entity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gregfowlerphd
0