Skip to content

Structure the references (normative, informative) #34

@Ostrzyciel

Description

@Ostrzyciel

I've recently been pointed to this: https://openengiadina.codeberg.page/rdf-cbor/

It looks very interesting... with some of the same goals as Jelly, but also some different ones. I think what is most relevant for us here is that there is something to learn from this spec.

Although Jelly is based on Protobuf which is not (and I doubt ever will be) a standard, it would make sense to have a references section, split into normative and informative references: https://openengiadina.codeberg.page/rdf-cbor/#name-references

Then, it would be clearer what documents are we referring to in the spec. We'd need to look into how to render such references with mkdocs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions