From: Stefan S. <s...@xs...> - 2002-09-12 07:16:42
|
yam...@li... (2002-09-11 22:42): > Date: Wed, 11 Sep 2002 17:12:04 -0700 > Subject: Re: [Yaml-core] Models debriefing > From: ir...@ms... (Mike Orr) > > I'm not fond of wikis for editing long documents though. It's fine for > adding short comments to a piece, but when you try to cut and paste > something that's bigger than a TEXTAREA, it pastes to some other part > of the document from where your cursor is, in the middle of a word even, > and then you have to go cut it out and try again. It's the browsers' > fault, but grrr. > I see a web page on which several YAML-documents are combined where you can edit each node by itself. A "toc"-editor would allow reordering of elements. We could ditch markup in favour of a YAML backend with something like yod (in the ruby parser package) as middleware. volunteers? :-) s. |
From: Oren Ben-K. <or...@ri...> - 2002-09-12 16:38:02
|
ir...@ms... [mailto:ir...@ms...] wrote: > This brings up a radical question: what do we need the models > for anyway? I'm not saying eliminate them, but rather keep > them in perspective. They are evolving from "the only way > you may access YAML data" to something like examples, ways > you *can* access the data. Perhaps they should be introduced > that way in the spec, to encourage people to not see them as > limiting, but rather as giving a helping hand. I agree whole heartedly with a single exception. According to the current spec, and the models we've discussed so far, it is OK to reorder the keys in a map without breaking any conforming YAML implementation reading the document; and it is invalid to use duplicate keys in a map. Other than that, sure, models are to _help_ people in processing YAML. Actually, the above restriction is _also_ in order to help, but it is much less obvious that it does. Have fun, Oren Ben-Kiki |
From: why t. l. s. <yam...@wh...> - 2002-09-12 14:14:51
|
Stefan Schmiedl (s...@xs...) wrote: > I see a web page on which several YAML-documents are combined > where you can edit each node by itself. A "toc"-editor would > allow reordering of elements. Perhaps we could borrow some xmlStorageSystem code [http://pycs.sourceforge.net/] for this idea. That's the closest thing I could think of. I haven't looked at WebDAV in the last little while but can't you do HTTP remote editing with file locking? I'm sure we can find something generic to use, then hack in YAML-specific features. > We could ditch markup in favour of a YAML backend with something > like yod (in the ruby parser package) as middleware. I don't know if Yod is good to use or not. I mean I kind of designed it out of necessity and I don't know if it's structure is agreeable. I could definitely use some peer review. I use type ids throughout, which doesn't seem to be too popular, but I find them incredibly useful for loading this entire structure quickly into classes. I'm attaching the current docs in Yod for YAML.rb, so you can get a picture. Generated HTML is at http://yaml4r.sf.net/doc/ and CHM output is avaiable in the file section of http://sf.net/projects/yaml4r/. I'm still working on man pages. _why |
From: why t. l. s. <yam...@wh...> - 2002-09-12 14:21:48
Attachments:
yamlrb.yod
|
Here's the Yod docs from YAML.rb. _why |
From: Brian I. <in...@tt...> - 2002-09-12 18:42:03
|
The #DOMAIN proposal has never really been accepted or denied. The idea is that you declare the domain of a document up front. And then all types of the form !/foo fall under that domain. It is a compliment (not a replacement) to the '^' shorthand. My rationale is that the Domain is stated at the top of the document, rather than anywhere in the document, and that it can't change. Change might be confusing to a reader because they must search backwards from the shorthand version. Anyway here's the diff: On 12/09/02 08:31 -0600, why the lucky stiff wrote: > --- #YAML:1.0 !yaml4r.sf.net,2003/yod/^Document > Title: Yaml.rb -- Yaml for Ruby > Table of Contents: > - Preface > Preface: !^Page > - !^Paragraph > > What is YAML? From the specification: > > - !^Quote > > YAML(tm) (rhymes with 'camel') is a --- #YAML:1.0 #DOMAIN:yod.yaml4r.sf.net,2003 !/Document Title: Yaml.rb -- Yaml for Ruby Table of Contents: - Preface Preface: !/Page - !/Paragraph > What is YAML? From the specification: - !/Quote > YAML(tm) (rhymes with 'camel') is a I will say that in doing this, I changed the domain to put yod in the front. This saved me from !/yod/Quote. Perhaps this proposal isn't that compelling. I really don't care for !^foo. !/foo seems better. A compromise would be to use ^ for the initial marker, and then '/' for the shorthands: --- #YAML:1.0 !yaml4r.sf.net,2003/yod/^Document Title: Yaml.rb -- Yaml for Ruby Table of Contents: - Preface Preface: !/Page - !/Paragraph > What is YAML? From the specification: - !/Quote > YAML(tm) (rhymes with 'camel') is a I rather like that better. Any other takers? Cheers, Brian |