This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#79: Handling and formatting of vector quantities in CF -----------------------------+---------------------------------------------- Reporter: lavergne | Owner: [email protected] Type: enhancement | Status: reopened Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: vector -----------------------------+---------------------------------------------- Comment (by markh): Replying to [comment:64 lavergne]: > I do not really see where (or how) to put a "break" and conclude. Do we have to reach 100% agreement? or have some voices more weight than others? How to we take the final decision in such a ticket? My view is that we need to reach a consensus on what represents a good enough solution, without any strong objections to the approach left outstanding. I feel that there is a good case for adding extra structure to this proposal, in order to meet a set of use cases which we have for specifying and working with vector quantities. I have tried to stress how important it is for our use of this feature that we can precisely define the role of a component within the scope of the vector container, we feel this is a crucial factor in delivering the benefit we seek. I also think it needs careful consideration how this new type of assocation will scale in the future of CF. The opportunity to semantically group data variables has not been present in CF before, it's posential applications are not yet clear but there may be many. For this reason I think it will be a very valuable approach for us to take to define a type for the vector container, so that if other containers are required in the future their usage can be clearly separated from what we decide here. For these reasons I have strong objections to the simplified solution and I urge those who favor the simplified solution to reconsider my position. I do not think that the solution I presented in [comment:55 comment:55] adds a lot of complexity, it feels clear and self describing to me, whilst it brings significant benefit to the people I work with. This is why I am continuing to request that it is implemented by the community. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/79#comment:65> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
