Admin message

WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Strange pattern for DPs in SAREF4BLDG
SAREF4BLDG introduces many DPs, with no domain and a XSD Datatype as a range (xsd:string (53), xsd:boolean (18), or xsd:integer (9), xsd:nonNegativeInteger (1)). SAREF4BLDG defines architectural ODPs that, given a DP p typically applied to a Class c with a certain datatype d, defines this DP with a range d, and a universal restriction on c that all values for p are d. In other words, declared sub-classes of s4bldg:Device have universal local restrictions on these DPs, and re-state the datatype is always what it should be. For example: ⊤ ⊑ ∀ s4bldg:frameSize . xsd:string s4bldg:ElectricMotor ⊑ ∀ s4bldg:frameSize . xsd:string This second axiom is useless and could be deleted to avoid redundancy.
issue