NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Wenli, Core is not to be a conformance class on its own. Clients would need to be compliant to core plus one or more extensions.Core would specify the equivalent of CV_DomainObject with no detail on the geometric objects.
These would be two conformance classes with corresponding compliance tests: - Core + 2D extension would say CV_DomainObject only contains 2D geometric objects. - Core + 3D extension would say CV_DomainObject contains 3D geometric objects.
George On Oct 5, 2008, at 12:10 AM, Wenli Yang wrote:
Aaron and George,I think that the main reason to require only 2D in core was to maximize potential implementations. Note that core does not imply the core concept of a (grid) coverage. Core means any sever/client must implement the capability defined as "core capability". Requiring n-D actually does not cause a problem in server implementation because a server can always offer only 2D coverage. However, it is not the case to client implementation. If n-D is required, then a client must be able to talk to a n-D coverage server, even if it needn't n-D data, otherwise it will not be considered compliant.Regards, Wenli
galeon archives: