On 26/11/01 18:50 -0500, Clark C . Evans wrote:
> Ok. I've posted a new version of the spec on
> line at http://yaml.org/cce-13.html and it'd
> be cool to get some feedback.
location: Status Of This Document
problemo: Paragraph is not properly justified
old: serialized form native
new: serialized form, native
old: module that provides for parser or emitter
new: module that provides parser or emitter
old: must provide or obtain from the application.
new: must provide to or obtain from the application.
problemo: Please change the Perl link to http://www.perl.com
or at least use.perl.org.
old: introduce a unique of handling whitespace.
new: introduce a unique method of handling whitespace.
old: YAML and XML information model are starkly different
new: YAML and XML information models are starkly different
old: are a keyed collection
new: are keyed collections
old: requires mapping, conventions, or an alternative
programming component, a document object model
new: requires mapping conventions, or an alternative
programming component (eg a document object model
old: Conformant YAML texts
new: Conformant YAML streams
old: occupation: baseball
new: occupation: baseball player
old: given : !text Chris
new: given : !str Chris
note: multiple occurances
problemo: what is this?
old: learned alot
new: learned a lot
old: supports both scalar values (string, integer)
new: supports both scalar values (string, integer, real)
old: Exceptions to this guide line
new: Exceptions to this guideline
problemo: This whole section went so far above my head I
couldn't even make sense of it. Could you possibly translate
it for human consumption? Or at least try explaining it
to someone (like me) who could translate it into humanese
prognosis: If you don't make this simple for people to
understand, then people (like me) are going to ignore
it and risk implementing non-conformant processes.
old: may extends information model
new: may extend the information model
old: reserved_indicators ::= '^' | '@'
new: reserved_indicators ::= '^' | '@' | '%'
old: stream contains more then
new: stream contains more than
old: Once an anchor was used
new: Once an anchor is used
alias : &02 *01
again : *02
problemo: I thought this was not allowed...
: This key had to be escaped.
could be this: |
"\a": This key had to be escaped.
old: unlike a folded scalar, a plain scalar may start in-line
new: unlike a folded scalar, a plain scalar must start in-line
old: Using an implicit text transfer method allows overcoming
new: Using an explicit text transfer method allows overcoming
this is an error, no? : |
third: <html><head><title>Embedded HTML!</title></head>
<body><p class="none">This can even
have embedded HTML since there is no
escaping, and since < (the starting character)
is not an indicator!</p></body>
because: it fails implicit regexes
fix: use quotes
old: deserialize the node to any native native
new: deserialize the node to any native
note: this shows up in more than one sentence
old: Name: org.yaml.ptr
new: Name: org.yaml.ref
note: we decided to make pointer be reference
On the whole, this document is really shaping up. The new structure with
the tutorials at the top really helps.
Good work guys!