BEY and BESY

Paul Lambert <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <[email protected]>
Thanks Steve,  I appreciate the dialog  ...  in the embedded forums I usually lurk YAML and human readable is a foreign concept.  

Here's where the mini design stands:

Binary Encodable Schema in YAML (BESY)
Binary Encoded YAML (BEY)
 - BESY is valid a YAML document
 - (YAML data + BESY schema for the data) enables conversion to/from BEY
 - (BEY data + BESY schema for the data) enables conversion to/from YAML
 - YAML data created with BESY may be subject to additional type checking and constraints
 - BEY encoding could be same as protobuf (exact encoding TDB or could be multiple)

One of my main goals is to allow a YAML-like syntax to be used in designing protocols for lower layer protocols and constrainedd devices.  I suspect the TLV crowd will have a similar response to YAML as this forum has to binary encoding :-)   

If/when the design reaches the next level I'll post a pointer to this list ...


Paul

> -----Original Message-----
> From: Steve Schafer [mailto:steve-bHQK/pGi2DVWk0Htik3J/[email protected]]
> Sent: Tuesday, June 14, 2011 5:26 AM
> To: Paul Lambert
> Cc: [email protected]
> Subject: Re: [Yaml-core] Reg: PyYAML grammar
> 
> On Mon, 13 Jun 2011 17:20:45 -0700, you wrote:
> 
> >Take a look a protobuf as an example of combining human readable and
> >binary encodings if you want to see a worked hybrid.
> 
> Protobuf and YAML are quite different things. They complement each
> other, but neither is a replacement for the other. The protobuf binary
> encoding is primarily an "over the wire" format; no one ever looks at
> it, except very rarely (during debugging). YAML is more of an endpoint
> format. As such, YAML -> protbuf ... protobuf -> YAML can be a
> perfectly
> reasonable thing to do.
> 
> The most successful computer/computer and computer/human protocols are
> heavily layered, with each layer having a well-defined set of
> responsibilities. Using the OSI model as the analogy, protobuf lives
> near the presentation/session (6/5) layer boundary, whereas YAML lives
> near the application/presentation (7/6) layer boundary.
> 
> -Steve Schafer

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.