Replies: 2 comments 2 replies
-
Add a clause called Exception with all the usual facets.
|
Beta Was this translation helpful? Give feedback.
-
Have hit this as well. I think we used to be able to prohibit facets in applicability with I've used negation regexs as a workaround. It's not clear to me artificially restricted the regex flavour. As this is just an implementors agreement it would seem relatively simple to change in 1.0 vs a schema update. E.g. find all entities except those with names starting 'IGNORE_' ...
</ids:entity>
<ids:attribute>
<ids:name>
<ids:simpleValue>Name</ids:simpleValue>
</ids:name>
<ids:value>
<xs:restriction base="xs:string">
<xs:pattern value="^(?!IGNORE_.*$).*" />
</xs:restriction>
</ids:value>
</ids:attribute>
</ids:applicability> |
Beta Was this translation helpful? Give feedback.
-
I want to have a requirement that takes all Walls that don't have the "FireRating" property. In other words, I want an applicability to include IFCWALL entity and a property allowing any name/pset except "FireRating" and "Pset_WallCommon". I thought I could do that with a pattern, but I see that XML flavour doesn't really support a negation lookahead. Has anyone found a way to express it?
Beta Was this translation helpful? Give feedback.
All reactions