Skip to content

Drawing dependancy relationships#693

Open
Ellord207 wants to merge 2 commits intomasterfrom
nelrod/drawing-depends
Open

Drawing dependancy relationships#693
Ellord207 wants to merge 2 commits intomasterfrom
nelrod/drawing-depends

Conversation

@Ellord207
Copy link
Copy Markdown
Contributor

Relationships for Drawing Dependency

Introducing relationships used by the Drawing Production for relating Drawings to the Elements they depend on. These are in the Drawing Production Application layer without plans to promote anywhere else.

These relationships classes will assist with knowing when a Drawing is out of date and when it needs to be recreated.

@Ellord207 Ellord207 requested a review from a team as a code owner April 22, 2026 14:41
@Ellord207
Copy link
Copy Markdown
Contributor Author

Should these be in their own schema, like the Sheet Numbering are?

@diegoalexdiaz
Copy link
Copy Markdown
Contributor

Once proven, these relationships feel like should go to an application-level DrawingProduction schema. Its purpose could be framed as "Application-specific concepts that support data-authoring functionality in Drawing Production".

@Ellord207
Copy link
Copy Markdown
Contributor Author

After a side conversation, we have agreed that the schema should exist here for the moment.

| * See LICENSE.md in the project root for license terms and full copyright notice.
======================================================================================= -->
<ECSchema schemaName="DrawingProductionExperimental" alias="dpex" version="01.00.02" xmlns="http://www.bentley.com/schemas/Bentley.ECXML.3.2" description="This schema contains an experimental implementation of concepts associated with Drawing Production.">
<ECSchema schemaName="DrawingProductionExperimental" alias="dpex" version="01.00.03" xmlns="http://www.bentley.com/schemas/Bentley.ECXML.3.2" description="This schema contains an experimental implementation of concepts associated with Drawing Production.">
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be 01.00.02 upon release. As part of my last PR, I incremented the last digit of the WIP copy to 01.00.02.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants