Independent specification about strictyaml HOT 7 OPEN

In any case I'd like to help any way I can with this. I'd love to see the rust community starting to use strictyaml.

from strictyaml.

it would be nice for it to be a repo

Technically, it already is a repo, just not on github (sr.ht doesn't use pull-requests but the more traditional mailing list and patches workflow). That said, I have set up a second repo here.

About the license, I'm just worried that some things may resemble the YAML spec, which explicitly states:

This document may be freely copied, provided it is not modified.

I don't think including parts of it in another document that doesn't describe itself as the yaml spec would count as modified.
I guess it would really depend on the intent of the document.

from strictyaml.

I've had the exact same thought, yes. I wasn't really sure how to get started with the spec though.

from strictyaml.

I've studied the yaml spec and https://hitchdev.com/strictyaml/ and started working on a draft over on sr.ht. It's not much at all yet (I hope i can work on it a bit this weekend). Contributions are welcome. Are you fine with sending patches to my public inbox or should I setup a mirror on github? (or do you want to create an org? or include it in this repo?) Also, is CC0 a good license for a specification?

from strictyaml.

This looks good so far.

I don't mind where this goes (it can always be moved later), but it would be nice for it to be a repo.

CC0 seems good, yes.

from strictyaml.

it would be nice for it to be a repo

Technically, it already is a repo, just not on github (sr.ht doesn't use pull-requests but the more traditional mailing list and patches workflow). That said, I have set up a second repo here.

About the license, I'm just worried that some things may resemble the YAML spec, which explicitly states:

This document may be freely copied, provided it is not modified.

from strictyaml.

The obstacle I'm facing is that existing formal grammars lack:

• a formal definition (ABNF's definition in ABNF is ambiguous, although there is A Formalization of the ABNF Notation and a Verified Parser for ABNF Grammars, A. Coglio)
• proper Unicode support (see this IETF draft for an attempt to add it to ABNF)
• parameters in rules (they're used in the YAML spec, but they aren't specified anywhere AFAIK)

So, it might be necessary to define a formal grammar, e.g. using leanprover/lean.

from strictyaml.