Closed ronaldtse closed 3 years ago
@ronaldtse lets also add attribute
name to syntax, like this:
data_type "Banking Information" {
attribute "art code"
attribute "CCT Number"
}
primitive Integer
enum Address {
attribute "Mr."
attribute "Mrs."
}
I think we can add "attribute" for easier parsing for data type, but let's allow a shorthand notation.
For enum, those are not "attributes" but data instances. Calling them attribute
s is misleading. We can use entry
or something like that. But still I prefer having a shorthand notation.
I think we can add "attribute" for easier parsing for data type, but let's allow a shorthand notation.
For enum, those are not "attributes" but data instances. Calling them
attribute
s is misleading. We can useentry
or something like that. But still I prefer having a shorthand notation.
Ok, got you, lets introduce short notation: when entry for enum
or class
does not equal to predefined names(generalizes| aggregation|method) will treat as a field
for class or entry
for enum?
Yeah, e.g.:
class A {
my_attr1
attribute my_attr2
}
enum A {
my_val1
entry my_val2
}
?
Done in #49
e.g.
Thoughts?
Originally from: https://www.slideshare.net/iscrquinter/uml-omg-fundamental-certification-2