Optional fields and `schema.fieldsMatch` clarification

[roll]

What Data Package version are you using?

v2

Describe the Issue

Current wording for e.g. equal:

equal: The data source MUST have exactly the same fields as defined in the fields array. Fields MUST be mapped by their names.

Consider we have this schema (? for optional field):

- field
- field1?
- field2?
- field3?

In this case current wording required to have data like this (if not optional fields are set):

field,field1,field2,field3
value,'','',''
...

On the other hand a file like this would be completely compatible to the intent of schema:

field
value
...

I think we need to clarify that we need required fields present not just all of them with optional filled with nulls

Participation

• I am willing to submit a pull request for this issue.