Promote "Metadata in Table Schema" recipe to the specs.

[pierrecamilleri]

Context and related issue :
fix #899

Migrated pull request from datapackage-v2-draft repo

Still to do on this PR:

• Move table schema to /standards/table-schema.md (cf. main)
• Move changelog to /overview/changelog.md (cf. main)
• Update wording so it aligns with Data Package (my pending PR)
• Update some links
• Fix invalid json example (it was an unintended change)
• Clarify if examples are borrowing title and path from Data Resource (I think they are, included in my PR) or if this is something completely separate.

[roll]

Thanks a lot for rebasing the PR @pierrecamilleri !

[pierrecamilleri]

@peterdesmet @roll

Almost there.

I added "partial" to qualify "Data Resource" in the suggestion of Peter concerning the documentation of top-level "examples" ; because an object with title and path is not a valid Data Resource (name is missing). Or do we want to impose a name property ? What do you think of this wording ?

[peterdesmet]

@pierrecamilleri thanks for the updates! Regarding:

Or do we want to impose a name property ? What do you think of this wording ?

I think we should simply stick to the Data Resource spec and require a name (over a title). I have made suggestions to the files to reflect this change.

[pierrecamilleri]

Hi all, we added you as a reviewer as you are a voting member and this PR is tagged "Requires 6 voting approvals" ! We would like this PR to land soon, if you can find the time to make a review it would be great !

[PietrH]

Looks good, I made some small textual suggestions.

[khughitt]

Looks good to me. 👍

[ezwelty]

End-of-year crunch so admittedly only a cursory review, but looks good to me.

[pschumm]

This looks ok to me.

[pierrecamilleri]

Thank you very much all for your quick review ! 🙏

@roll except for this last small wording decision, everything looks ready to me!

[roll]

Thanks a lot @pierrecamilleri!

I already voted yes. Can you please run npm run generate having the next branch merged and up-to-date so it will applies changes to v2.1 of the profiles instead of v2.0?

[pierrecamilleri]

npm run generated!
(sorry for the delay)

[johanricher]

Great work @pierrecamilleri 👏 Looks like it's ready to merge now 🚀

[roll]

Hi @pierrecamilleri,

Sorry for the slow communication due to the holiday season =)

Looks great!

We just need to remove any changes to public/profiles/2.0. from the diff to ensure published standard immutability.

[pierrecamilleri]

We just need to remove any changes to public/profiles/2.0. from the diff to ensure published standard immutability.

Done! (Sorry I have missed this)

[roll]

Amazing! Thanks!

[roll]

Merged. Here is a live preview of v2.1 - #1051