🚀 Release v2.1

content/docs/overview/changelog.md

@@ -6,6 +6,12 @@ sidebar:
 
 This document includes all meaningful changes made to the **Data Package standard**. It does not cover changes made to other documents like Recipes or Guides.
 
+## v2.1
+
+##### `schema.fieldsMatch` (fixed)
+
+[fieldsMatch](/standard/table-schema/#fieldsMatch) has been corrected from array to string to match its definition ([#965](https://github.com/frictionlessdata/datapackage/issues/965)).
+
 ## v2.0
 
 This release includes a rich set of specification improvements to make Data Package a finished product (see [announcement](https://frictionlessdata.io/blog/2023/11/15/frictionless-specs-update/)). All changes were reviewed and accepted by the Data Package Working Group.

content/docs/standard/data-package.mdx

@@ -3,7 +3,7 @@ title: Data Package
 description: A simple container format for describing a coherent collection of data in a single package. It provides the basis for convenient delivery, installation and management of datasets.
 sidebar:
   order: 1
-profile: /profiles/2.0/datapackage.json
+profile: /profiles/2.1/datapackage.json
 authors:
   - Rufus Pollock
   - Paul Walsh
@@ -129,7 +129,7 @@ Packaged data resources are described in the `resources` property of the package
 
 A root level Data Package descriptor `MAY` have a `$schema` property that `MUST` be a profile as per [Profile](/standard/glossary/#profile) definition that `MUST` include all the metadata constraints required by this specification.
 
-The default value is `https://datapackage.org/profiles/1.0/datapackage.json` and the recommended value is `https://datapackage.org/profiles/2.0/datapackage.json`.
+The default value is `https://datapackage.org/profiles/1.0/datapackage.json` and the recommended value is `https://datapackage.org/profiles/2.1/datapackage.json`.
 
 :::note[Backward Compatibility]
 If the `$schema` property is not provided but a descriptor has the `profile` property a data consumer `MUST` validate the descriptor according to the [Profiles](https://specs.frictionlessdata.io/profiles/) specification.

content/docs/standard/data-resource.mdx

@@ -3,7 +3,7 @@ title: Data Resource
 description: A simple format to describe and package a single data resource such as an individual table or file. The essence of a Data Resource is a locator for the data it describes. A range of other properties can be declared to provide a richer set of metadata.
 sidebar:
   order: 2
-profile: /profiles/2.0/dataresource.json
+profile: /profiles/2.1/dataresource.json
 authors:
   - Rufus Pollock
   - Paul Walsh
@@ -159,7 +159,7 @@ If a resource has `profile` property that equals to `tabular-data-resource` or `
 
 A root level Data Resource descriptor `MAY` have a `$schema` property that `MUST` be a profile as per [Profile](/standard/glossary/#profile) definition that `MUST` include all the metadata constraints required by this specification.
 
-The default value is `https://datapackage.org/profiles/1.0/dataresource.json` and the recommended value is `https://datapackage.org/profiles/2.0/dataresource.json`.
+The default value is `https://datapackage.org/profiles/1.0/dataresource.json` and the recommended value is `https://datapackage.org/profiles/2.1/dataresource.json`.
 
 :::note[Backward Compatibility]
 If the `$schema` property is not provided but a descriptor has the `profile` property a data consumer `MUST` validate the descriptor according to the [Profiles](https://specs.frictionlessdata.io/profiles/) specification.

content/docs/standard/table-dialect.mdx

@@ -3,7 +3,7 @@ title: Table Dialect
 description: Table Dialect describes how tabular data is stored in a file. It supports delimited text files like CSV, semi-structured formats like JSON and YAML, and spreadsheets like Microsoft Excel. The specification is designed to be expressible as a single JSON-compatible descriptor.
 sidebar:
   order: 3
-profile: /profiles/2.0/tabledialect.json
+profile: /profiles/2.1/tabledialect.json
 authors:
   - Rufus Pollock
   - Paul Walsh
@@ -148,7 +148,7 @@ Database formats is a group of formats accessing data from databases like SQLite
 
 A root level Table Dialect descriptor `MAY` have a `$schema` property that `MUST` be a profile as per [Profile](/standard/glossary/#profile) definition that `MUST` include all the metadata constraints required by this specification.
 
-The default value is `https://datapackage.org/profiles/1.0/tabledialect.json` and the recommended value is `https://datapackage.org/profiles/2.0/tabledialect.json`.
+The default value is `https://datapackage.org/profiles/1.0/tabledialect.json` and the recommended value is `https://datapackage.org/profiles/2.1/tabledialect.json`.
 
 ### `header`
 

content/docs/standard/table-schema.mdx

@@ -3,7 +3,7 @@ title: Table Schema
 description: A simple format to declare a schema for tabular data. The schema is designed to be expressible in JSON.
 sidebar:
   order: 4
-profile: /profiles/2.0/tableschema.json
+profile: /profiles/2.1/tableschema.json
 authors:
   - Rufus Pollock
   - Paul Walsh
@@ -86,7 +86,7 @@ The way Table Schema `fields` are mapped onto the data source fields are defined
 
 A root level Table Schema descriptor `MAY` have a `$schema` property that `MUST` be a profile as per [Profile](/standard/glossary/#profile) definition that `MUST` include all the metadata constraints required by this specification.
 
-The default value is `https://datapackage.org/profiles/1.0/tableschema.json` and the recommended value is `https://datapackage.org/profiles/2.0/tableschema.json`.
+The default value is `https://datapackage.org/profiles/1.0/tableschema.json` and the recommended value is `https://datapackage.org/profiles/2.1/tableschema.json`.
 
 #### `fieldsMatch` {#fieldsMatch}
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "datapackage.org",
   "type": "module",
-  "version": "2.0",
+  "version": "2.1",
   "engines": {
     "node": "^20.0.0",
     "npm": "^10.0.0"

profiles/dictionary/schema.yaml

@@ -123,16 +123,14 @@ tableSchemaField:
     - "$ref": "#/definitions/tableSchemaFieldDuration"
     - "$ref": "#/definitions/tableSchemaFieldAny"
 tableSchemaFieldsMatch:
-  type: array
-  item:
-    type: string
-    enum:
-      - exact
-      - equal
-      - subset
-      - superset
-      - partial
-    default: exact
+  type: string
+  enum:
+    - exact
+    - equal
+    - subset
+    - superset
+    - partial
+  default: exact
 tableSchemaPrimaryKey:
   oneOf:
     - type: array