Clarify trailing / on topic names

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • 3.1.1
    • Affects Version/s: 3.1.1
    • Component/s: core
    • None
    • Hide

      WD16
      1. line 1518 Existing text

      "Also, because the single-level wildcard matches only a single level, "sport/+" does not match "sport".

      Replacement text
      'Also, because the single-level wildcard matches only a single level, "sport/+" does not match "sport" but it does match "sport/" '

      2. Line 1559

      Existing: 'A leading "/" creates a distinct Topic Name or Topic Filter'

      Replacement: 'A leading or trailing "/" creates a distinct Topic Name or Topic Filter'

      3. Line 1559 Add a new bullet saying

      A Topic Name or Topic Filter consisting only of the "/" character is valid

      Show
      WD16 1. line 1518 Existing text "Also, because the single-level wildcard matches only a single level, "sport/+" does not match "sport". Replacement text 'Also, because the single-level wildcard matches only a single level, "sport/+" does not match "sport" but it does match "sport/" ' 2. Line 1559 Existing: 'A leading "/" creates a distinct Topic Name or Topic Filter' Replacement: 'A leading or trailing "/" creates a distinct Topic Name or Topic Filter' 3. Line 1559 Add a new bullet saying A Topic Name or Topic Filter consisting only of the "/" character is valid
    • Hide

      Fixed in WD17

      Show
      Fixed in WD17

      Section 4.7 mentions that adding a leading / to a topic name makes it into a different topic, but doesn't say the same for a trailing / Readers might infer that a trailing / therefore doesn't change the topic name, but in order for other statements in the spec to be consistent it does. So to clarify this we need to mention triailing / explicitly

            Assignee:
            Unassigned
            Reporter:
            Peter Niblett (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: