@open-resource-discovery/specification 1.15.0 → 1.16.0

package/dist/generated/spec/v1/schemas/OrdOverlay.schema.json

@@ -425,7 +425,7 @@
                 "root": {
                     "type": "boolean",
                     "const": true,
-                    "description": "Concept-level selector targeting the root of the document being patched.\nMUST be `true`.\n\nUse this selector to patch top-level properties of any JSON/YAML-based metadata format\nwithout coupling to specific structural paths. This is especially useful for:\n\n- Patching document-level metadata (title, description, version, contact info)\n- Adding or merging top-level sections (e.g. `components`, `tags`, `servers` in OpenAPI)\n- Extending the root object with new properties across format versions\n\nSupported metadata formats and typical use cases:\n\n**OpenAPI** (`openapi-v2`, `openapi-v3`, `openapi-v3.1+`):\n- Patch `info.description`, `info.title`, `info.contact`\n- Add `components.securitySchemes` or `components.schemas`\n- Add `tags`, `servers`, or `externalDocs`\n\n**AsyncAPI** (`asyncapi-v2`):\n- Patch `info` block, `servers`, `channels` at the root\n\n**OData CSDL JSON** (`csdl-json`):\n- Patch root-level `$Version`, `$EntityContainer`, or add namespace objects\n\n**ORD Document** (no specific `definitionType`):\n- Patch root-level ORD document properties\n\n**MCP / A2A** (any Specification ID):\n- Patch top-level metadata or add root-level tool/skill definitions\n\nThe `root` selector is equivalent to `jsonPath: \"$\"` but is preferred because it\nexplicitly communicates intent and is resilient to format differences where `$`\nmight have ambiguous semantics."
+                    "description": "Concept-level selector targeting the root of the document being patched.\nMUST be `true`.\n\nUse this selector to patch top-level properties of any JSON/YAML-based metadata format\nwithout coupling to specific structural paths. This is especially useful for:\n\n- Patching document-level metadata (title, description, version, contact info)\n- Adding or merging top-level sections (e.g. `components`, `tags`, `servers` in OpenAPI)\n- Extending the root object with new properties across format versions\n\nSupported metadata formats and typical use cases:\n\n**OpenAPI** (`openapi-v2`, `openapi-v3`, `openapi-v3.1+`):\n- Patch `info.description`, `info.title`, `info.contact`\n- Add `components.securitySchemes` or `components.schemas`\n- Add `tags`, `servers`, or `externalDocs`\n\n**AsyncAPI** (`asyncapi-v2`):\n- Patch `info` block, `servers`, `channels` at the root\n\n**OData CSDL JSON** (`csdl-json`):\n- Patch root-level `$Version`, `$EntityContainer`, or add namespace objects\n\n**MCP / A2A** (any Specification ID):\n- Patch top-level metadata or add root-level tool/skill definitions\n\nThe `root` selector is equivalent to `jsonPath: \"$\"` but is preferred because it\nexplicitly communicates intent and is resilient to format differences where `$`\nmight have ambiguous semantics."
                 }
             },
             "examples": [
@@ -762,7 +762,7 @@
                 "baseUrl": {
                     "type": "string",
                     "format": "uri-reference",
-                    "description": "Optional [base URL](../../spec-v1/index.md#base-url) of the system instance.\nBy providing the base URL, relative URLs in the overlay are resolved relative to it.",
+                    "description": "Optional [base URL](../../spec-v1/index.md#base-url) of the system instance.\nBy providing the base URL, relative URLs in the overlay are resolved relative to it.\n\nThe `baseUrl` MUST NOT contain a trailing slash.",
                     "pattern": "^http[s]?:\\/\\/[^:\\/\\s]+\\.[^:\\/\\s\\.]+(:\\d+)?(\\/[a-zA-Z0-9-\\._~]+)*$",
                     "examples": [
                         "https://example-sap-system.com",

package/dist/generated/spec/v1/types/Configuration.d.ts

@@ -16,7 +16,7 @@ export interface OrdConfiguration {
     /**
      * Optional [base URL](../index.md#base-url) that can be used to resolve the relative URLs to the ORD Documents.
      *
-     * The `baseUrl` MUST NOT contain a leading slash.
+     * The `baseUrl` MUST NOT contain a trailing slash.
      *
      * If you do not provide this property, the base URL is assumed to be the URL of the config endpoint without `/.well-known/open-resource-discovery` suffix.
      * This implies that either a `baseUrl` or only absolute URLs MUST be provided when no standardized well-known URI is used.