How to ask for two attributes in form of an "AND" condition?

[masterblogger]

I have a usecase which requires to check if the content of two attributes are filled (equal using the facet definition) / have a specific values (using the values definition). Both attributes should be filled / have some values inside to be apply to the information requirements.
Using the IFCClasses isn't possible because other instances with the identical IFCClass won't require those information.

Example: There are severval Enities as IfcValve in the model, but only those valves which have the attribut "operational relevant" with the value "yes" require the attribute "field designation" which itself is requiring to be filled.

In my point if view the two snippes should be combined:

Asking for the attribute operational relevant

<attribute minOccurs="1" maxOccurs="1">
  <name>
    <simpleValue>operational relevant</simpleValue>
  </name>
  <value>
    <simpleValue>yes</simpleValue>
  </value>
</attribute>

Asking for the attribute field designation

<attribute minOccurs="1" maxOccurs="1">
  <name>
    <simpleValue>field designation</simpleValue>
  </name>
</attribute>

As far as i search the documentation and the examples [https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-attribute.md] this (edge?) case isn't documented yet with examples.

My Questions are: Has it been thought about it to implement such an AND Condition in the IDS ? If so what would be syntax ?

[Moult]

I want all valves with operational relevant to have a field designation.

• Applicability:
  • Property operational relevant = yes
• Requirement
  • Property foo

Is that what you wanted?

[NickNisbet]

This is

Applicability: Valve Relevant Requirement Field identifier

Logically this is not(valve) or not(relevant) or field_identifier

Sent whilst away from my desk.

Regards,

Nick.

Nicholas Nisbet FRSA MA(Cantab) DipArch(UNL) Fellow: Royal Society of Arts Fellow: buildingSMART International & UKI Chapter Director: AEC3 UK Ltd Web: http://www.aec3.comhttp://www.aec3.com/ E-mail: @.@.> Direct: +44 (0) 1494 714 933 Mobile: +44 (0) 781 616 8554 Registered Address: 46 St Margaret's Grove, Great Kingshill, High Wycombe, Bucks, HP15 6HP, UK

Vice-Chair: buildingSMART UK Chapter Convenor: buildingSMART Regulatory Room

********** Confidentiality Notice **********. This e-mail and any file(s) transmitted with it, is intended for the exclusive use by the person(s) mentioned above as recipient(s). This e-mail may contain confidential information and/or information protected by intellectual property rights or other rights. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender and delete the original and any copies of this e-mail and any printouts immediately from your system and destroy all copies of it.

On 26 Jul 2023, at 07:48, Joern Rettweiler @.***> wrote:



I have a usecase which requires to check if the content of two attributes are filled (equal using the facet definition) / have a specific values (using the values definition). Both attributes should be filled / have some values inside to be apply to the information requirements. Using the IFCClasses isn't possible because other instances with the identical IFCClass won't require those information.

Example: There are severval Enities as IfcValve in the model, but only those valves which have the attribut "operational relevant" with the value "yes" require the attribute "field designation" which itself is requiring to be filled.

In my point if view the two snippes should be combined:

Asking for the attribute operational relevant

operational relevant yes

Asking for the attribute field designation

field designation

As far as i search the documentation and the examples [https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-attribute.md] this (edge?) case isn't documented yet with examples.

My Questions are: Has it been thought about it to implement such an AND Condition in the IDS ? If so what would be syntax ?

— Reply to this email directly, view it on GitHubhttps://github.com/buildingSMART/IDS/issues/176, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABYIIJLD6MHZQ3VS2VI2EGTXSC4TVANCNFSM6AAAAAA2YDIZEA. You are receiving this because you are subscribed to this thread.Message ID: @.***>