Mandatory image

[raphaelbastide]

Specimen.png from wikipedia if available?

[davelab6]

Making some mandatory means having a way to check for it; so the rules about what is mandatory belong in a software project that has policies and checks for compliance with them, and then communicates a pass/fail of the check with an appropriate level of importance; checks with a mandatory status that fail will give a big red warning :)

But this isn't something that belongs in this project, I think; its something that belongs in eg https://github.com/xen/bakery/

[raphaelbastide]

Ok, so if I understand you well, there will be no optional or mandatory notice in the specification. Everything can be complete or not. Mandatory aspect will be software side.
It means that I can fill not all the lines in the METADATA.yml for instance, if my font is not complete or if I am not the original designer. Do you agree?

[davelab6]

there will be no optional or mandatory notice in the specification

Well, there is the specification and then there is an reference implementation of the specification. So far we have just created a reference implementation with 0 byte files laid in with file names and directory tree structures. When we are happy with this prototype, we can write a specification for it. The specification will have such MUST SHOULD MAY notices. And then we can write a lint tool to check any implementation against the specification. We need those 3 things.

It means that I can fill not all the lines in the METADATA.yml for instance, if my font is not complete or if I am not the original designer. Do you agree?

I am happy for the specification to have plenty of MAY statements and for the lint tool to allow people to 'package' fonts they didn't create, even proprietary ones.