From: Jason D. <ja...@in...> - 2002-10-21 03:22:19
|
Has there been any discussion about a SAX-like API for YAML? I'm not suggesting it be included in the spec but I find the section on the Serial Model (as well as the other models) difficult to parse. Something a little more concrete might help me (and others?) here. It might also provide good feedback as to what might need to be cleared up in the spec. Maybe we could start a Wiki page to work on this. A great start would be something like the definition for the ContentHandler interface in SAX. Jason |
From: Brian I. <in...@tt...> - 2002-10-21 05:31:27
|
On 20/10/02 19:54 -0700, Jason Diamond wrote: > Has there been any discussion about a SAX-like API for YAML? I'm not > suggesting it be included in the spec but I find the section on the > Serial Model (as well as the other models) difficult to parse. Something > a little more concrete might help me (and others?) here. It might also > provide good feedback as to what might need to be cleared up in the > spec. > > Maybe we could start a Wiki page to work on this. A great start would be > something like the definition for the ContentHandler interface in SAX. I finally got to meet Oren in person this weekend. It was a good time. We were able to cover topics very quickly. We mainly concentrated on the issues remaining to create a final version of the spec suitable for a six month freeze. This mainly consisted of the information model rewrite. Oren and I agree on what needs to be done. If Clark agrees (he and Oren are meeting later this week) then we should have a final spec quite soon. Speaking of Wiki, I've put some of the basis of the information models section on the Wiki. http://wiki.yaml.org/yamlwiki/YamlTerminology http://wiki.yaml.org/yamlwiki/YamlAxioms This is from the conversations that oren and I had. It's a work in progress. Cheers, Brian |
From: why t. l. s. <yam...@wh...> - 2002-10-21 05:41:32
|
Brian Ingerson (in...@tt...) wrote: > I finally got to meet Oren in person this weekend. It was a good time. We > were able to cover topics very quickly. We mainly concentrated on the issues > remaining to create a final version of the spec suitable for a six month > freeze. This mainly consisted of the information model rewrite. Oren and I > agree on what needs to be done. If Clark agrees (he and Oren are meeting > later this week) then we should have a final spec quite soon. This is incredibly crazy good. Seriously, this is sooo good to hear. Glad the meeting went good. The wiki stuff is great. _why |
From: why t. l. s. <yam...@wh...> - 2002-10-21 06:04:30
|
Jason Diamond (ja...@in...) wrote: > Has there been any discussion about a SAX-like API for YAML? Hey, Jason. Have you seen the libyaml code at all? Or more specifically, the Pod file describing its API? I find it to be very SAX-like. Basically, there's four primary event handlers: alias_handler, keyed_handler, series_handler, leaf_handler. A number of other derived handlers: document_notify, keyed_check, keyed_set, series_push. Neil has a great Pod file going into a few examples and to how their events are processed. So that's one idea. I think, in general, we're not focused on a SAX-like API because it might detract from our huge goal of providing data serialization to the people of this planet. I mean we kinda had a big struggle over how to expose the Parser (Builder) API. The spec lies so closely to the way that we write implementations... The libyaml API only proves that some semblance of SAX will be needed to get our jobs done, though. If you haven't seen the Pod, let me know and I'll pass in on. _why |
From: Jason D. <ja...@in...> - 2002-10-21 06:15:45
|
On Sun, 2002-10-20 at 23:14, why the lucky stiff wrote: > Jason Diamond (ja...@in...) wrote: > > Has there been any discussion about a SAX-like API for YAML? > > Hey, Jason. Have you seen the libyaml code at all? Or more specifically, > the Pod file describing its API? I haven't seen it. The yaml.org website says that it's "still private". > I find it to be very SAX-like. Basically, there's four primary event handlers: > alias_handler, keyed_handler, series_handler, leaf_handler. A number of other > derived handlers: document_notify, keyed_check, keyed_set, series_push. > > Neil has a great Pod file going into a few examples and to how their events > are processed. So that's one idea. > > I think, in general, we're not focused on a SAX-like API because it might > detract from our huge goal of providing data serialization to the people > of this planet. I mean we kinda had a big struggle over how to expose the > Parser (Builder) API. The spec lies so closely to the way that we write > implementations... I'm working on an implementation right now and think that the spec isn't as clear as it could be (maybe that's what Brian's referring to when he mentioned the "information model rewrite"). > The libyaml API only proves that some semblance of SAX will be needed to > get our jobs done, though. If you haven't seen the Pod, let me know and > I'll pass in on. That sounds exactly like what I'm looking for! Jason |