search

ISO-TC211 / StandardsTracker

This GitHub repository lets you - our users - log and track issues that you find with our standards and other document. Tag the issue with the standard or standards effected; we will assign it to the relevant group(s) within TC 211.
11 stars 0 forks source link

"boundary" is an attribute, not operation #338

Open isotc211 opened 3 years ago

isotc211 commented 3 years ago

Justification: In 10.3.2.3 and 10.3.3, there describes "boundary operation", but boundary is an attribute of Topology. Proposal: change all(4 cases) the "boundary operation" into "boundary attribute".

isotc211 commented 3 years ago

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology. (In reply to ISO/TC 211 WG9, Information management from comment #1)

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology.

I agree almost all the points of yours. However, my point is that the "boundary" is attribute in UML.

isotc211 commented 3 years ago

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology. (In reply to ISO/TC 211 WG9, Information management from comment #1)

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology.

I agree almost all the points of yours. However, my point is that the "boundary" is attribute in UML.

isotc211 commented 3 years ago

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology. (In reply to ISO/TC 211 WG9, Information management from comment #1)

Boundary is both a attribute and an operation. Any geometric object is also a topological object.

The distinction between the two is just a view of geometry objects, and topology is a view of the relationships of geometric objects. Either venue can be associated to each other, but they can also work apart.

The two are mostly interchangeable. For example, the geometry of a "ellipsoidal" object which can be put through a map projection, with (theoretically) both the ellipsoidal and the planar geometry have the same topology, but not the same geometry (the metric is bungled but the topology is preserved). A geoidal representation of a geometry is close to real-world, but neither the geoid nor the map geometry is reality, but they usually have the same topology.

I agree almost all the points of yours. However, my point is that the "boundary" is attribute in UML.