• Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Profile-YAML
    • None
    • Hide

      Option1: create an attribute status definition by cut and paste the property one.
      Option2: create a generic status definition and use that one everywhere is needed.

      Show
      Option1: create an attribute status definition by cut and paste the property one. Option2: create a generic status definition and use that one everywhere is needed.

      It seems really strange that for defining the attribute status we use another definition's keyname description.
      If thoese are really the same than we should have a STATUS definition that is generic and all that need it use it.
      If there is something that is called "something status" should really be used just for "that something" and not for "also something else" somewhere else in the spec.

            Assignee:
            Unassigned
            Reporter:
            Luca Gioppo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: