From: Clark C. E. <cc...@cl...> - 2003-10-11 03:51:51
|
Hello. This is just to add another "request" to our future bucket. A friend of mine, Alex, had emailed me privately to ask if we would consider adding a way for a YAML document to name where it came from, so that a client program could put forth an interface and then use REST (PUT/POST) methods to update the document over HTTP. Anyway, as this really isn't the document's content, it is more like a directive kinda item... something like... --- %ORIGIN:http://clarkevans.com/docs/this.yaml > This document actually came from http://clarkevans.com/docs/this.yaml if you want to change it, do a HTTP PUT after you have authenticated. ... Best, Clark |
From: Oren Ben-K. <or...@be...> - 2003-10-11 09:08:18
|
Clark C. Evans [mailto:cc...@cl...] wrote: > --- %ORIGIN:http://clarkevans.com/docs/this.yaml > > This document actually came from > http://clarkevans.com/docs/this.yaml > if you want to change it, do a HTTP PUT > after you have authenticated. > ... -1. Instead: --- !meta-data/document origin: http://clarkevans.com/docs/this.yaml author: Alex: !pgp/signature ... approvals: Clark: !pgp/signature ... Oren: !pgp/signature ... =: This document actually came from http://clarkevans.com/docs/this.yaml if you want to change it, do a HTTP PUT after you have authenticated. ... Have fun, Oren Ben-Kiki |
From: Brian I. <in...@tt...> - 2003-10-11 16:53:36
|
This brings up a question I have which is: How do we associate a schema document(s) with a yaml document? It would seem to me that this would have to be a directive. Of course we need a schema language first. Since it is likely that more than one schema language might evolve; we may want to make the schema attaching facility allow this. Musing... Cheers, Brian On 11/10/03 11:07 +0200, Oren Ben-Kiki wrote: > Clark C. Evans [mailto:cc...@cl...] wrote: > > --- %ORIGIN:http://clarkevans.com/docs/this.yaml > > > This document actually came from > > http://clarkevans.com/docs/this.yaml > > if you want to change it, do a HTTP PUT > > after you have authenticated. > > ... > > -1. Instead: > > --- !meta-data/document > origin: http://clarkevans.com/docs/this.yaml > author: > Alex: !pgp/signature ... > approvals: > Clark: !pgp/signature ... > Oren: !pgp/signature ... > =: > This document actually came from > http://clarkevans.com/docs/this.yaml > if you want to change it, do a HTTP PUT > after you have authenticated. > ... > > Have fun, > > Oren Ben-Kiki > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core |
From: Oren Ben-K. <or...@be...> - 2003-10-11 17:43:47
|
Brian Ingerson [mailto:in...@tt...] wrote: > This brings up a question I have which is: > > How do we associate a schema document(s) with a yaml > document? It would seem to me that this would have to be a directive. No. You do it like this: --- !my.own.com/tag/identifying/contents # stuff ... Schema == set of valid values == type => tag. If you have a few minutes I'd love to hear why you thinks formats are necessary. I think I have a proof that they are not... Then again it sounds like you intend formats to play a somewhat different rols than before. Have fun, Oren Ben-Kiki |