From: Clark C . E. <cc...@cl...> - 2001-05-18 15:58:43
|
----- Forwarded message from "Clark C . Evans" <cc...@cl...> ----- Date: Fri, 18 May 2001 02:00:39 -0500 From: "Clark C . Evans" <cc...@cl...> Subject: Meeting Minutes Thank you all for our meeting. Please correct any of the items here if you find them to have error. Present: Brian Ingerson, Clark Evans, Neil Watkiss, Oren Ben-Kiki 1. Brian stated that he would invstigate Oren's Syntax and get back with us if it meets Perl's serilization requirements for hard references. If not, specify what alternatives we can use. 2. We agreed on Oren's reference (&*) syntax. 3. We agreed on having an optiona RFC 822 Header, this requires that a YAML text without this header must begin on line #2. Furthermore, if an RFC 822 Header is present, then it must include "X-YAML-Version: 1.0" 4. Brian said that he'd investiage the RFC a bit more specifically relating to the productions. (I'm not sure if this is necessary... ) 5. We talked at length about multi-line scalar text nodes. Thus far, we agreed on option D, due to assumed compatibility with RFC 822. Clark agreed to verify this compatibility. 6. Brian stated that the quoting mechanism was not good enough for source code or ASCII art, and backed option F. However, option F does not explicitly preserve trailing whitespace on a given line. So Brian suggested using > < pairs. Oren suggested using single quotes. Clark asked Brian to come up with something he likes and propose it. 7. We agreed, after some discussion, that a YAML parser must support MIME. We agreed implicity that it must support base64 encoding. 8. We didn't discuss this... but it should be mentioned that to (a) support unicode and (b) support RFC 822, our texts must be UTF-8. Thus a YAML parser/writer will default to UTF-8, although other encoding support is optional. 9. Clark agreed to make a "boostrap" C program and upload to source forge. Brian and Neil agreed to download and hack at will. 10. Oren mentioned that he was thinking of doing a Java or Javascript implementation. 11. Clark agreed to update the spec with the current agreements. 12. Brian mentioned that he'd show YAML to one of his Perl friends. (sorry I didn't catch his name) 13. Clark and Brian discussed the MIME usage. 14. Clark introduced a very short discussion on the need for a global mechanism to uniquely identify names in a non-language specific manner. 15. Clark agreed to write up the "single vs multi" line controversy and post to the list so that it is clearly understood. 16. We made little progress on the scalar indicator for lists, to colon or not to colon. It wasn't agreed, but Clark thinks this is someone else's monkey. If Oren and Brian can't agree within 7 days, Clark will put on the dictator cap. 17. It is nice to have Neil in on the talk! Ok. Thank you all for attending Kind Regards, Clark ----- End forwarded message ----- |