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.

Sign up for GitHub

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

Jump to bottom

Define 'can save?' for Domain Attribute Instances #230

Open
GoogleCodeExporter opened this issue May 15, 2015 · 2 comments
Open

Define 'can save?' for Domain Attribute Instances #230

GoogleCodeExporter opened this issue May 15, 2015 · 2 comments
Labels
auto-migrated Component-Model Milestone-Release0.7 Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

What new or enhanced feature are you proposing?
Currently, 'can save?' is only defined for DomainIterators. This condition 
should be extended to DomainAttributeInstances.

What goal would this enhancement help you achieve?
More consistent metamodel, with respect to the design philosophy of Properties. 
That is, a DAI is not a Property because it may contain 
Operations/Conditions/Events.

Original issue reported on code.google.com by soundasleep on 21 Mar 2011 at 2:45
@GoogleCodeExporter
Copy link
Author 

Also, the 'save' operation is already defined for Domain Attribute Instances, 
but no converse 'can save?' condition is defined.

Original comment by soundasleep on 21 Mar 2011 at 2:45

@GoogleCodeExporter
Copy link
Author 

mass tagging old issues to future work

Original comment by soundasleep on 26 Sep 2011 at 9:54

  • Added labels: Milestone-Release0.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Model Milestone-Release0.7 Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter