Eno seems interesting. I don’t know that it’s interesting enough to exist over existing formats, but it’s in the YAML/Config format/TOML family and sort of a cousin to Markdown/Settext/Wikiformat (as all these data formats are).
It doesn’t seem to have a spec per se and the documentation is silent about primitive datatypes, which is annoying. Looking at the Python library’s documentation suggests that it uses an on demand coercion approach…basically, you coerce an element when you retrieve it from the parsed structure:
>>> from enopy import loaders, parse
>>> doc = parse("""
... publish: yes
... location: 36.987094, -25.091719
... contact: contact@faulty
... """)
>>> doc.boolean('publish')
True
>>> doc.lat_lng('location')
{ 'lat': 36.987094, 'lng': -25.091719 }
>>> doc.email('contact')
ValidationError: 'contact' must contain a valid email address, for instance 'jane.doe@eno-lang.org'.
I can’t say I’m a big fan of this API. It seems really dreadful to have the field name as a string inside a coercing function call on the document which magically gets the right “loaders”? I mean, you have to specify the type of everything including built in structured types? Yeek.
Ok there does seem to be a generic interface:
>>> document = enopy.parse(input)
>>> document.element('title')
<class Field name="title" value="Artfest 2018">
>>> document.element('tags')
<class List name="tags" items=2>
>>> document.element('content')
<class Section name="content" items=14>
This feels like a step back from e.g. JSON. And this documentation hurts me!
Still, it’s kinda interesting and one could always layer a different API on top.
