There are a number of quite attractive suggestions here. The idea that someone could enter a name to a tool that says "no, we would not build the name that way because..." is quite attractive, though perhaps only viable for simple denials. I hope some of the other ideas can move forward.
There is a rich review process of the details of each term which others will convey, and that will take place thoroughly for every suggested name, I am sure. That said there are two kinds of names that could be subject to routine conformance. Jonathan focused (I think) on constructions involving the body of the name, and I agree those will not be automatable for another 3-4 years (;->), if only because the definition has to be reality-checked. But where we are talking about adding generic modifiers, it seems to me a more automated approach is possible. If the meaning of the modifier is clear, then no matter what name it is applied to, the meaning of the resulting compound should be clear. If that is the case, then adding that modifier to an existing name should be verifiable mechanically. No? john On Mar 2, 2011, at 19:51, Cameron-smith, Philip wrote: > Hi All, > > The last time we discussed formalizing grammar and vocabulary, or an > ontology, it was clearly hard to get agreement. It would also be a lot of > hard work and could be a lot of work to amend and modify if it is done too > narrowly. > > I suggest we consider a weaker option, which I think would give us much of > the benefit at moderately cost, and could be a step on the road to a more > rigorous system. > > I suspect it would be fairly easy to take Jonathan's inferred grammar and > vocabulary system and attach meanings to each phrase and piece of grammar by > cutting and pasting from the existing std_name descriptions. > > We could then tweak our current practice on this mailing list so that when a > person proposes a std_name they should state (or perhaps there is a little > bit of code to check) that the proposed std_name conforms to the existing > grammar and vocabulary rules. I think most of us would then provide only > cursory scrutiny. Perhaps there could even be an automatic timer so that if > nobody objects within some time period (perhaps 1 month) then the name is > automatically accepted. Essentially the default decision for conforming > names would be 'acceptance'. I think this would also make the generation of > the text descriptions either automatic, or perhaps obsolete, in many cases > because they could be inferred from the grammar and vocabulary tables. > > This would provide faster acceptance for proposers, and allow this mailing > group to focus on the harder issues, primarily ones which want to modify or > extend the grammar and/or vocabulary. > > I think this is what have been doing in practice for a while, and I think > formalizing it a little would make it better for all. > > Best wishes, > > Philip > > ----------------------------------------------------------------------- > Dr Philip Cameron-Smith, p...@llnl.gov, Lawrence Livermore National Lab. > ----------------------------------------------------------------------- > > > >> -----Original Message----- >> From: cf-metadata-boun...@cgd.ucar.edu [mailto:cf-metadata- >> boun...@cgd.ucar.edu] On Behalf Of Jonathan Gregory >> Sent: Wednesday, March 02, 2011 5:37 AM >> To: Seth McGinnis >> Cc: cf-metadata@cgd.ucar.edu >> Subject: Re: [CF-metadata] standard_name modifiers >> >> Dear Seth >> >> I think we can devise systems which will develop *proposed* standard >> names >> that conform to existing patterns and lexicon. If they do, they are >> often >> uncontroversial and usually accepted. However we still need a manual >> approval >> process because there are sometimes choices about how a quantity might >> be >> described i.e. there's more than one possible conformant proposal, and >> there >> are special cases when there is a commonly used term we might want to >> employ. >> Apart from those reasons, there are also a quite often proposals which >> require >> new lexicon, new interpretations or new patterns. >> >> Best wishes >> >> Jonathan >> _______________________________________________ >> CF-metadata mailing list >> CF-metadata@cgd.ucar.edu >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > _______________________________________________ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata John Graybeal <mailto:jgrayb...@ucsd.edu> phone: 858-534-2162 Product Manager Ocean Observatories Initiative Cyberinfrastructure Project: http://ci.oceanobservatories.org Marine Metadata Interoperability Project: http://marinemetadata.org _______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
