Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BCF 2.1: Update xml schema for viewpoints #85

Merged
merged 1 commit into from
Jul 26, 2016
Merged

Conversation

jasollien
Copy link
Contributor

No description provided.

@jasollien jasollien force-pushed the bcf-2-1-viewpoints branch 2 times, most recently from 5726843 to be3dc5b Compare June 20, 2016 10:56
@pbuts
Copy link
Contributor

pbuts commented Jul 11, 2016

I think having a visibility for the set and for individual components is confusing (especially when the component visibility has a default value). It also adds data overhead.

We already need rules around the xml schema to inform implementers how to interpret and create the different sets, so we can easily make a statement that:

  • the set defines the visibility
  • components included in the set are the exceptions to the set's visibility
  • components that are selected or colored are always visible

I also want to propose to specify the visibility as attribute of the sets (Components, Spaces, SpaceBoundaries, Openings), not as attributes of the unnamed sequence or complex type.

@jasollien
Copy link
Contributor Author

  1. The set defines visibility: (I guess that's what you are referring to in your last line as well) I agree.
  2. Components included in the set are exceptions: I partly agree. However it is also possible to have components with the same visibility as the default in the set, if you want to export selection/coloring etc.
  3. Components that are selected or colored are always visible: As we decided in Bratislava, If I remember correctly, It is allowed to export hidden, selected/colored objects, but it is considered bad practice.

We may talk more about this in todays hackathon :)

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.

None yet

3 participants