javamoney
  1. javamoney
  2. JAVAMONEY-54

Define the ItemFormat instances and styles to be required by an implementation

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.4-EDR1
    • Fix Version/s: 0.5
    • Component/s: API
    • Labels:
      None

      Description

      • Define exactly what ItemFormat implementation must be provided by the (reference) implementation.
      • Along with that for each ItemFormat the according supported LocalizationStyle attributes must be defined.
      • Define which FormatToken implementations must be provided by the (reference) implementtion.
      • Similarly define the supported LocalizationStyle attributes.

      Since when working with FormatToken}}s there are ultiple tokens in place, we need to define an "addressing" scheme, so attributes in a {{LocalizationStyle passed can be either

      • match to several tokens (unspecified)
      • match exact to one target token (explicit)

      The mechanism/naming scheme should be made explicit and be discussed and also added to the specification/TCK.

        Activity

        atsticks created issue -
        atsticks made changes -
        Field Original Value New Value
        Assignee atsticks [ atsticks ]
        Description * Define exactly what {{ItemFormat}} implementation must be provided by the (reference) implementtion.
        * Along with that for each {{ItemFormat}} the according supported {{LocalizationStyle}} attributes must be defined.
        * Define which {{FormatToken}} implementations must be provided by the (reference) implementtion.
        * Similarly define the supported {{LocalizationStyle}} attributes.

        Since when working with {{FOrmatToken}}s there are ultiple tokens in place, we need to define an "addressing" scheme, so attributes in a {{LocalizationStyle}} passed can be either
        * match to several tokens (_unspecified_)
        * match exact to one target token (_explicit_)

        The mechanism/naming scheme should be made explicit and be discussed and also added to the specification/TCK.
        * Define exactly what {{ItemFormat}} implementation must be provided by the (reference) implementation.
        * Along with that for each {{ItemFormat}} the according supported {{LocalizationStyle}} attributes must be defined.
        * Define which {{FormatToken}} implementations must be provided by the (reference) implementtion.
        * Similarly define the supported {{LocalizationStyle}} attributes.

        Since when working with {{FormatToken}}s there are ultiple tokens in place, we need to define an "addressing" scheme, so attributes in a {{LocalizationStyle}} passed can be either
        * match to several tokens (_unspecified_)
        * match exact to one target token (_explicit_)

        The mechanism/naming scheme should be made explicit and be discussed and also added to the specification/TCK.
        atsticks made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        atsticks made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        keilw made changes -
        Component/s API: Core Artifacts [ 14820 ]
        Component/s API: Advanced formatting and parsing [ 14822 ]
        atsticks made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            atsticks
            Reporter:
            atsticks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: