Realising v1.9.0

[Alcoz]

We will be releasing version 1.9.0 on 4 October, which improves the model for logistical information on products and orders.

Added

Class

• Temperature, subClassOf: QuantitativeValue.

ObjectProperty

• containerInformationOf, domain: skos:Concept and (skos:broader value ContainerInformation) and (skos:inScheme value DFC_ProductGlossary_Facet), subPropertyOf: facetOf, inverseOf: hasContainerInformation.
• hasContainerInformation, domain: DefinedProduct, subPropertyOf: hasFacet, inverseOf: containterInformationOf.
• deliveredAt, domain: DeliveryOption.
• pickedUpAt, domain: PickupOption.
• hasPaymentMethod, domain: Order, inverseOf: paidWith.
• paidWith, domain: PaymentMethod, inverseOf: hasPaymentMethod.
• hasTemperature, domain: SuppliedProduct, inverseOf: hasTemperature.
• isTemperatureOf, domain: Temperature, inverseOf: hasTemperature.

DataProperty

• minValue, domain: QuantitativeValue, range: float, subPropertyOf: value.
• maxValue, domain: QuantitativeValue, range: float, subPropertyOf: value.
• accessibilityInfo, domain: DeliveryOpiton, range: string.
• deliveryConstraint, domain: DeliveryOption, range: string.
• frozen, domain: SuppliedProduct, range: boolean.
• refrigerated, domain: SuppliedProduct, range: boolean.

Changed

• Domain hasMainContact: Enterprise -> (Enterprise or PhysicalPlace).
• Domain hasPhoneNumber: Agent -> (Agent or PhysicalPlace).

Removed

• Facets classes

ObjectProperty

• refersTo.
• uses.

[RaggedStaff]

I'm just wondering... I think a lot of these changes are related to Logistics work (and therefore not required for FDC development). Would it make more sense for this to be v2.0.0 ? 🤔

[lecoqlibre]

Semantic versioning:

MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes