Merge branch 'main' into 887/separate-concerns-between-types-and-exte…

…nsions

content/docs/specifications/glossary.md

@@ -66,7 +66,7 @@ Adherence to a specification does not imply that additional, non-specified prope
 }
 ```
 
-This flexibility enables specific communities to extend metadata as appropriate for the data they manage. As an example, the [Tabular Data Package](https://specs.frictionlessdata.io/tabular-data-package/) specification extends Data Package to the case where all the data is tabular and stored in CSV.
+This flexibility enables specific communities to extend Data Packages as appropriate for the data they manage. As an example, the [Fiscal Data Package](https://fiscal.datapackage.org) specification extends Data Package for publishing and consuming fiscal data.
 
 ### URL or Path
 

content/docs/standard/extensions.mdx

@@ -10,17 +10,7 @@ import { LinkCard, CardGrid } from "@astrojs/starlight/components"
 We want to help as much domain-specific Data Package extensions as possible. If you have one in mind or already started working, feel free to share opening a new issue or pull request.
 :::
 
-One of the key strengths of the Data Package Standard lies in its extensibility. While the standard provides a solid foundation for organizing and describing data, it also recognizes that diverse datasets have unique requirements. Data practitioners can extend the standard by incorporating custom metadata, validation rules, or specific constraints to suit their data's peculiarities. Below is the list of registered Data Package extensions:
-
-## General Use
-
-<CardGrid>
-  <LinkCard
-    title="Tabular Data Package"
-    description="A data package for tabular data, including spreadsheets and CSV files."
-    href="../../extensions/tabular-data-package"
-  />
-</CardGrid>
+One of the key strengths of the Data Package Standard lies in its extensibility. While the standard provides a solid foundation for organizing and describing data, it also recognizes that diverse datasets have unique requirements. Data practitioners can extend the standard by incorporating custom metadata, validation rules, or specific constraints to suit their data's peculiarities. Below is the list of well-known Data Package extensions:
 
 ## Domain Specific
 

profiles/dictionary/package.yaml

@@ -51,60 +51,6 @@ dataPackage:
       propertyOrder: 200
       options:
         hidden: true
-tabularDataPackage:
-  title: Tabular Data Package
-  description: Tabular Data Package
-  type: object
-  required:
-    - resources
-    - profile
-  properties:
-    profile:
-      "$ref": "#/definitions/profile"
-      enum: ["tabular-data-package"]
-      propertyOrder: 10
-    name:
-      "$ref": "#/definitions/name"
-      propertyOrder: 20
-    id:
-      "$ref": "#/definitions/id"
-      propertyOrder: 30
-    title:
-      "$ref": "#/definitions/title"
-      propertyOrder: 40
-    description:
-      "$ref": "#/definitions/description"
-      propertyOrder: 50
-      format: textarea
-    homepage:
-      "$ref": "#/definitions/homepage"
-      propertyOrder: 60
-    version:
-      "$ref": "#/definitions/version"
-      propertyOrder: 65
-    created:
-      "$ref": "#/definitions/created"
-      propertyOrder: 70
-    contributors:
-      "$ref": "#/definitions/contributors"
-      propertyOrder: 80
-    keywords:
-      "$ref": "#/definitions/keywords"
-      propertyOrder: 90
-    image:
-      "$ref": "#/definitions/image"
-      propertyOrder: 100
-    licenses:
-      "$ref": "#/definitions/licenses"
-      propertyOrder: 110
-    resources:
-      "$ref": "#/definitions/tabularDataResources"
-      propertyOrder: 120
-    sources:
-      "$ref": "#/definitions/sources"
-      propertyOrder: 200
-      options:
-        hidden: true
 dataResources:
   title: Data Resources
   description: An `array` of Data Resource objects, each compliant with the [Data Resource](/data-resource/) specification.