AndCheck, OrCheck vs RASE

[VladimirAlexiev]

RASE dictates a certain evaluation logic (R are evaled as "and", E are evaled as "not-or", etc). So why do we need AndCheck, OrCheck? https://github.com/Accord-Project/aec3po/blob/5fb6f7e2b8b9f0f208caeeab68461aa8b3c0dfcd/src/aec3po.ttl#L14

[beachtom]

My vote would be for removing And Or - as we will use RASE in ACCORD.

However, if we want to offer multiple approaches - we could leave this - but we should make it clear in the documentation

[VladimirAlexiev]

• I think we agreed that we should capture RASE. We should include alternative means only if proven necessary.
• The structure and meaning (logical evaluation) of RASE is shown in https://github.com/Accord-Project/bcrl/blob/main/RASE.md#nisbetfuturevirtualconstruction2008
• We don't need AndCheck: these are simply several Requirements attached to the same check
• However, I don't see how RASE can express "Or". Selection and Application are evaluated as disjunction ("or"), but there's a "not" in front
• I also have to admit that The difference between Selection and Application is not entirely clear to me...

Closely related to https://github.com/Accord-Project/aec3po/issues/9

[beachtom]

Most ORs are not really OR they are AND with applicabilities inside.

But in the case we need a very explicit OR it can be done with a set of Exception Boxes

[VladimirAlexiev]

@beachtom can you give some examples?

[beachtom]

So an example would be something like:

A door must comply with one of the following: A) Red doors should be 5 m wide B) Blue doors must be 5.5m wide

This looks like an OR - but it is actually a set of And with multiple applicabilities. Certainly in the UK I found true OR things very rare. But we need to support them in any case.

[VladimirAlexiev]

Here's another OR example:

An accessible door:

• must be motorized, OR
• must have opening force at the edge LTE 50 Newton

Guess we can represent it like this:

• Requirement: opening force at the edge LTE 50 Newton
  • Exception: type is Motorized

But should we burden the SME to do this refactoring? And how does he decide which OR branch to put as main Requirement, and which as subsidiary Exception?

[beachtom]

So I would RASE Tag that as: [R1] [A1]An accessible doorp[/A1] [E1]must be motorized[/E1], OR [E2]must have opening force at the edge LTE 50 Newton[/E2] [/R1]

This will translate down to R1 = !A1 || E1 || E2