-
Notifications
You must be signed in to change notification settings - Fork 17
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
Naming of packages, classes and attributes #6
Comments
Note from the meeting in Southampton: Real world name vs UML names. Using tagged values and aliases. |
Prefixes have some value too - ref discussion on ISO-TC211/19115-2Revision#19 |
Agenda item at the HMMG meeting i Sydney. |
The prefixes are redundant; namespaces meet the requirements that motivated the introduction of the prefixes. If a class name is to be redefined (not imported) in a model, it should be given a name that distinguishes it from the other class. |
I agree with Steve, except that prefixes may have some value for human readability of the models. |
Closed, but referenced in #29 |
Use some text from the desciption of important changes in the new 19107, regarding not using prefixes
Rules from standards - camelcase etc.
The text was updated successfully, but these errors were encountered: