v1.9.7

Changed

• Allowing disabled as "hidden property" in Data Products for backward compatibility
  • The property was removed in favor of lifecycleStatus
  • This may be cleaned up / removed again in the future

v1.9.6

Added

• Added lifecycleStatus to data products, which replaces the boolean disabled property.

Fixed

• Renamed some instances of sap-csn-interop-v1 to sap-csn-interop-effective-v1 (inconsistency)
  • Bugfix release. So far, this was not used yet, as CSN Interop Effective is still in development.

Removed

• Removed optional disabled property on data products, as the new lifecycleStatus supersedes it.

v1.9.5

Changed

• Renamed one Data Product type enum value from base to primary.
  • BREAKING change, but introduced as a patch, as the Data Product interface is still in beta phase.

Infrastructure

• Schemas published on NPMJS.org under @sap/open-resource-discovery package name.

v1.9.4

Changed

• Renamed sap:hdlf-delta-sharing:v1 implementation standard to sap:delta-sharing:v1 to be more generic and not technology specific.
  • Incompatible change, but part of the "beta" Data Products, so we'll introduce it as a bugfix

Added

• added sap-csn-interop-effective-v1 as a standardized resource definition format for API and event resources

v1.9.3

Added

• added optional visibility to Consumption Bundle
  • Some consumption bundle access types are only meant for internal or private purposes. Especially when we have internal APIs, their assigned Consumption Bundles are likely internal, too.
  • If visibility is not given, default is public (to ensure backward compatibility)

v1.9.2

Added

• Added localId to Packages, for consistency with other ORD resources
• Added public link to the SQL interface specification for SAP ecosystem.

Changed

• Data Product shortDescription and description are now mandatory
  • This is a breaking change, but as the Data Product concept as a whole is beta, we'll introduce it as a patch change.

v1.9.1

Added

• Added back FAQ page (can be found under "Details" navbar item)
• Added autogenerated class diagrams for ORD Documents and Configuration Interface.
• Added optional systemTypeRestriction to EventResourceIntegrationAspect
  • This can be used to limit the event publisher system type, which can be used to setup the subscription accordingly.
• Added explicit statement that the same resource definition type MUST NOT be provided more than once.
  • This was already implied, but not stated explicitly.
• Added two new (optional) SHOULD statements regarding deprecation and sunset lifecycle.
  • We think they represent common sense / practice and help with validating a good usage of the related attributes.
  • If successors is given, the described resource SHOULD set its releaseStatus to deprecated.
  • If a resource is deprecated without defining its successors, a sunsetDate SHOULD be provided.
• Clarification on consumer expectations toward lastUpdate property.

Changed

• Renamed the term application namespace to system namespace
  • This is more consistent with the existing ORD terminology around system type
  • As it's only used as a term and not in the interface, this is not a breaking change

v1.9.0

Added

• Added new (lightweight) Group and Group Type concept
  • Adds a new partOfGroups attribute on ORD resources
  • Adds two new top level concepts to the ORD document: Group and Group Type
  • This can be used to define custom group types and assign ORD resources to them
  • With this, custom taxonomies can be built that are either centrally or decentrally defined.
• Added relatedEntityTypes to Entity Types
  • This allows to define that Entity Types are related to other Entity Types (e.g. from a different namespace)
• Added clarification that an ORD Aggregator MUST bump lastUpdated if the provider didn't do it, but it detected a change.
• Added explicit Access Strategy description for open, defining how local and global tenant headers can be optionally passed on.
• Added new Detail Articles:
  • How To Adopt ORD as a Provider detail page
  • System Landscape Model detail page
  • Grouping and Bundling detail page

Changed

• Providing the sunsetDate for a deprecated resource is now only recommended instead of mandatory (compatible change)
  • "If the releaseStatus is set to deprecated, the sunsetDate SHOULD be provided (if already known)."
  • "Once the sunset date is known and ready to be communicated externally, it MUST be provided here."

v1.8.5

Release 1.8.5

v1.8.1

Changed

• Fix: Data Products need to have at least one output port
  • This is implied through the definition of a Data Product
  • Breaking change that we'll push as a bugfix, as so far it was clear to have at least one output port