[Yaml-core] IRC Meeting Minutes

[Clark C . E. <cc...@cl...>]

Ok.  We had an IRC chat today with Brian Oren and myself 
to address outstanding issues.  We resolved:

  1. Adoption of one space for indentation (for now)

  2. No in-line blocks  (this was a whim proposal)

  3. Back-tick to start private implicit types,
     all other implicit types are registered 
     and part of the formal YAML spec (appendix)

  4. On separators...

     a) Top level separators will not have 
        single-line content.

     b) The version format doesn't have an 
        indicator, thus looks like...

        --- YAML:1.0

     c) Two adjacent separators are an error. (See #11)

        In later versions, this may be extended 
        into a more general mechanism to allow 
        for "document level attributes" as described 
        by point #11 in Brian's last post.

  5. Implicit types

     a) We implicitly agreed that address line
        such-as: 328 Wittigin's way
        should be a !text item and should 
        not be an implicit scalar.

     b) We resolved that implicit types may
        contain whitespace.  However, we also
        agreed not to reserve any implicit types 
        which do allow whitespace for now.

        In this way we can further limit implict 
        types down the road to a single token.

     c) We implicitly agreed that Date, Time, 
        and DateTime will make it in as an 
        implicit type, following a single token 
        format limited ISO 8601  as described in 
        http://www.w3.org/TR/NOTE-datetime with
        slight modifications (no partial dates).

     d) See #3

  6. Base64 

     a) We agreed that !base64 is an explicit type.
        And for now we've agreed to include a
        preceding [= and trailing ] on base64 values.

     b) We did not discuss, but implicitly agreed 
        to "no next/multi-line implicits"

        (clark) I think with the new \- style, we
        may want to revisit this.

     c) We agreed to explore using !type!pipeline
        over the next few weeks.  Specifically
        examining round-trip issues.  If this is
        workable, we'd like to include pipeline 
        in 1.0; if not we can drop it for 1.0

  7.  The reference implicit type

     a) We've implicitly agreed to stick with *

  8.  Flow scalar starting with a quote...

     a) We've agreed to introduce a new style,
        denoted by \- which explicitly denotes
        a flow (and not quoted) next-line scalar.

        Note: This would allow implict types to
              appear in the next line scalar...
              this impact was not discussed.

              But... I think it's good.

  9.  An empty stream is a valid series of zero
      documents.  agreed.

  
  10. Empty strings must be explicit in top level 
      scalars (small error fix).  Examples:

      --- \
      ""
      --- \
      ~

  11. Brian's #11 issue.  We forbid adjacent separators
      to allow this in the future; but not now.

  12. Brian's use of the ~ null value for a key in 
      sparse lists was adopted.


I think that's it.  No new issues were raised.

Clark