From: Clark C. E. <cc...@cl...> - 2004-09-05 01:00:01
|
David, Three comments: - The key insight in your proposal is that missing tags can be modeled as a "syntax shorthand" for unspecified-*. This makes the whole definition of tag resolution quite beside the point. - Both your and my proposals are too complicated, we are trying to 'define' a stage after parsing and before 'tag recognition'. However, this stage is simple to describe -- it is a YAML Transform. An application is free to do _anything_ they wish as long as it follows the YAML Representation Model. In fact, they may choose to do _nothing_ and leave the !unspecified tags as they are and build a digital signature. Or, they may wish to do quite a bit in this transform before loading, adding default values, re-arranging the graph to upgrade from an older version, etc. - I don't like the idea of a default-default tag. I'd much rather say that tag-specifiers like !! are simply not subject to default tag globalization. Also, if I put !tag in my document, I expect it to tell me "tag" in my model, and it would be really unexpected for things to be cooked without me explicitly asking for it. Having to turn this off sucks. My proposal is better here *wink* - We should take most of what wrote and add it as a 'informational' appendix explaining a 'recommended' default transformation between the parse result and the graph that is eventually recognized and then loaded. Cheers! Clark -- Clark C. Evans Prometheus Research, LLC. http://www.prometheusresearch.com/ o office: +1.203.777.2550 ~/ , mobile: +1.203.444.0557 // (( Prometheus Research: Transforming Data Into Knowledge \\ , \/ - Research Exchange Database /\ - Survey & Assessment Technologies ` \ - Software Tools for Researchers ~ * |