Fwd: Breaking change between YAML 1.1 and 1.2 with multiple documents
Trans <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <CAEu+kw2q1HJyu2rJSNWc3Gdg0EkvPY8xAn0v3qveq128hDJBDw@mail.gmail.com> |
I suppose the %YAML tag could be done away with if context is always the defining factor. When there is a question then it would be up to the "protocol" to specify. That might be as simple as a file extension, e.g. `.yaml12` or part of a handshake before data transmission. Yet these approaches feel a bit haphazard, where as the directive feels reliable, albeit I'm not sure there is a parser out there that can handle both 1.1 and 1.2 documents (except is so far as they are compatible). Perhaps directives "smell" b/c they have never really been embraced? I certainly can imagine things like a %SCHEMA directive. Another might be a digital %SIGNATURE directive. And so on. But even so, I get the same gut feeling that they're not quite right. So, perhaps the smell is just that these directives aren't in YAML format. Could the specification be generalize such that all documents are streams, and then directives are just a preceding YAML "header" document with a `!!directives` type? Hmm.. of course that assumes the type of the directive document it known ... well the other directives wouldn't have that problem. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Yaml-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yaml-core