Skip to content

Make Sea Level an individual. Make other consequent changes to Sea Level, Altitude, and Ratio Measurement Information Content Entity #886

Open

Description

@michaelrabenberg

Apropos of #883 ...

  1. I suggest making https://www.commoncoreontologies.org/ont00000722 (Sea Level) an individual.

Relatedly:

  1. I suggest replacing Sea Level's skos:definition with the following: "The Fiat Surface that divides the spheroid composed of Earth and its atmosphere and that occupies the two-dimensional spatial region that corresponds to the mean level of calm water in the Earth’s oceans."

  2. The skos:definition of https://www.commoncoreontologies.org/ont00000787 (Altitude) is the following: "A Height that inheres in a Site that externally connects an Independent Continuant to either the surface of the Earth or the Earth's mean Sea Level." In light of how Sea Level is defined, I suggest replacing this skos:definition with the following: "A Height that inheres in a Site that externally connects an Independent Continuant to either the surface of the Earth or Sea Level."

  3. One skos:example in https://www.commoncoreontologies.org/ont00001022 (Ratio Measurement Information Content Entity) is "a measurement of the barometric pressure at 1,000 feet above sea level." I suggest capitalizing 'sea level' in this example.

Activity

  1. alanruttenberg commented on Jun 18, 2026

    @alanruttenberg
    Contributor

    Altitude should be renamed "Altitude above sea level", since altitude alone is ambigious to (at least) whether the height is measured from the geoid, sea level, the surface of the earth, or the ellipsoid. Or remove sea level from the definition and leave something fuzzy (not sure what - maybe "surface or proxy for surface of Earth".). I'd rather the latter, since that would move what surface is being used over to the measurement (ICE) side.

    Also, why does it inhere in a site rather than being a relational quality between an independent continuant and Earth, which seems to me clearer than having to invent a site.

  2. johnbeve commented on Jun 26, 2026

    @johnbeve
    Contributor

    @alanruttenberg 100% agreement on your point about relational quality. Similar remarks apply to a few other classes in the Quality Ontology..

  3. self-assigned this
    on Jun 26, 2026
  4. added
    for 2.2 releaseThese are changes we would like to see addressed under the 2.2 release
    on Jun 26, 2026
  5. added theissue type on Jun 26, 2026
  6. added this to the 2.2 Release milestone on Jun 26, 2026
  7. moved this from Backlog to In progress in CCO Project Boardon Jun 28, 2026
  8. added and removed
    for 2.2 releaseThese are changes we would like to see addressed under the 2.2 release
    on Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions