Inverse of PartOf

[CBenghi]

Discussing with a few implementers we have identified the possibility to add to 1.0 the inverse facet of PartOf.

It could be called HasParts, or something of that sort. It would work exactly like PartOf, but identify the container, instead of the contained.

This would resolve specifications like walls with fire resistant doors should also be fire resistant.

If implementers think it is easy to achieve it would make for a powerful feature in 1.0 or 1.1

[berlotti]

I don't see this as an option for 1.0.

There is a clear use-case defined very early on that projects start with requirements that are further specified over time.
Adding more 'specifications' is possible with 'PartOf' without having to change the original (more generic) requirements.

Great to discuss in 1.x or 2.x but I we cannot change scope for 1.0 now.

[aothms]

This would resolve specifications like walls with fire resistant doors should also be fire resistant.

I'm not so sure btw. If the hypothetical HasParts is fully symmetric to PartOf, wouldn't it only be able to express:

"walls with doors should be fire resistant" which seems to have less utility.

[CBenghi]

You are quite right, it was a rushed result of a chat with one implementer. I've already tagged it for the next version, with room for improvement. Thanks

…

On Tue, Oct 3, 2023, 19:48 Thomas Krijnen ***@***.***> wrote: This would resolve specifications like walls with fire resistant doors should also be fire resistant. I'm not so sure btw. If the hypothetical HasParts is fully symmetric to PartOf, wouldn't it only be able to express: "*walls with doors* should be fire resistant" which seems to have less utility. — Reply to this email directly, view it on GitHub <#200 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJY7MPHLH742CATZYYZZXLX5RFVRAVCNFSM6AAAAAA5Q3G2TCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGQ2DMOBSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>