UML Human-Usable Textual Notation Avatar
  1. OMG Specification

UML Human-Usable Textual Notation — Closed Issues

  • Acronym: HUTN
  • Issues Count: 10
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

On page 6-13, production rule [31]

  • Key: HUTN-14
  • Legacy Issue Number: 6701
  • Status: closed  
  • Source: Queensland University of Technology ( Jim Steel)
  • Summary:

    : On page 6-13, production rule [31] states:
    [31] AssocInstance := 32:AssocInstance | 35:InfixAssocLink
    This should be 32:AssocBlock, not 32:AssocInstance
    Proposed Resolution: On page 6-13, in section 6.7, replace
    "[31] AssocInstance := 32:AssocInstance | 35:InfixAssocLink"
    with
    "[31] AssocInstance := 32:AssocBlock | 35:InfixAssocLink"

  • Reported: HUTN 1.0b1 — Wed, 17 Dec 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

page 3-1, in section 3.2, "Input Stream Conformance

  • Key: HUTN-13
  • Legacy Issue Number: 5997
  • Status: closed  
  • Source: Queensland University of Technology ( Jim Steel)
  • Summary:

    on page 3-1, in section 3.2, "Input Stream Conformance":

    • "For a given combination of MOF model and HUTN Configuration" should
      be replaced with "For all given combinations of MOF models and HUTN
      Configurations".
  • Reported: HUTN 1.0b1 — Wed, 16 Jul 2003 04:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

classifier level attributes

  • Key: HUTN-12
  • Legacy Issue Number: 5876
  • Status: closed  
  • Source: DSTC ( Anna Gerber)
  • Summary:

    The document does not address how classifier level attributes are
    represented by HUTN

  • Reported: HUTN 1.0b1 — Mon, 3 Mar 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section 1.3 : Add text regarding the France Telecom implementation of HUTN

  • Key: HUTN-11
  • Legacy Issue Number: 5816
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Below the proposed text:
    France Telecom has developped since 1997 a MOF based model repository tool [Belaunde99] and has
    implemented since 1999 facilities to import and export textual human usable specifications that use a
    Java-like syntax (the notation was originnally named JMI) and a hierarchical identification system. The
    implementation uses a generic parser that is connected at run time to the API's generated from the MOF
    compliant metamodel definitions (No intermediate BNF parser generation is then used). France Telecom has
    provided feedback to the submitters based on its original implementation.

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Update the list of persons in the acknowledgments paragraph

  • Key: HUTN-10
  • Legacy Issue Number: 5815
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Issue : Preface : Update the list of persons in the acknowledgments paragraph
    In the current submission only two persons are mentioned (Kerry Raymond and Keith Duddy). Other
    persons such as Jim Steel and Mariano Belaunde should appear.

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The identification mechanism need to be more flexible

  • Key: HUTN-9
  • Legacy Issue Number: 5814
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Issue : The identification mechanism need to be more flexible to make easier the automatic production
    of HUTN renderings from modeling tools.
    The proposed identification mechanism is too rigid and very difficult to manage appropriately when
    HUTN renderings are produced automatically from use case tools.

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Excessive indentation due to the blocks used to delimit the package content

  • Key: HUTN-8
  • Legacy Issue Number: 5813
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Issue : Excessive indentation due to the blocks used to delimit the package contents.
    According to the current draft, the top-level definitions of a package instance need to be put inside
    a block delimited by open and close brackets. This is not very user-friendly in the sense that it
    introduces excessive indentation that could be avoided.
    Suggestion for resolution: Use a one-line delimiter convention (such as 'package "xxxxxx";') meaning
    that all the above definitions until the next delimiter are part of the package content. Note that the same
    kind of notation is found in the Java language to declare packages.
    This delimiter convention may be optional or mandatory (to be discussed).

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section 6.5: Need to improve readability when referencing instances

  • Key: HUTN-7
  • Legacy Issue Number: 5810
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Issue Section 6.5: Need to improve readability when referencing instances.
    Inside the class contents, due to the multiple short-hands, it's not always clear whether an instance is
    being defined (fully represented) or is being referenced .
    To avoid any possible confusion and improve readability, a "ref" prefix keyword could be added.
    Suggestion for resolution: Add the "ref" keyword in ClassInstanceRef
    [23] ClassInstanceRef := ('ref' (<ClasName>? 14:ClassRefString) ) | ExternalObjRef
    Need discussion : should the "ref" keyword be optional or mandatory?

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Issue : Section 6.3

  • Key: HUTN-6
  • Legacy Issue Number: 5809
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Issue : Section 6.3 : Ambiguous meaning when omitting opening and closing brackets
    In 6.3 in the first paragraph it's said that opening and closing brackets should be optionnaly omitted
    if the instance has no contents. This is error prone and ambiguous since one cannot distinguish between
    a definition without contents from a contained instance whose definition (full representation) is forwarded.
    Suggestion for resolution: remove the sentence (open and close brackets are not allowed to be omitted).

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Issue : Section 6.5

  • Key: HUTN-5
  • Legacy Issue Number: 5808
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • Summary:

    Issue : Section 6.5 : Missing where to put the full representation of a non inlined contained instance.
    According to the specification, a contained instance maybe represented by a full representation
    of the instance or by a reference to the instance. However, in the latter case, the specification does
    noy say nothing about where to place the full representation of the contained instances that are not
    inlined.
    Suggestion for resolution:
    In the second paragraph, after "or by a reference to the instance.", add the following sentence:
    "In the latter case the full representation of the contained instance must appear as a top level
    definition in the content of the current package.
    In addition, in order to distinguish between these "forwarded" definitions and the other
    "top-level" definitions we should consider introducing a prefix keyword (such as "forward",
    to be added in the ClassHeader).

  • Reported: HUTN 1.0b1 — Mon, 13 Jan 2003 05:00 GMT
  • Disposition: Resolved — HUTN 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT