Should the TRS specification be standalone or part of the Core multi-part specification?

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: None
    • Hide

      Leave TRS as a separate OASIS OSLC specification that just happens to be developed by the Core TC. It can have a lifecycle separated and more or less independent from the rest of Core.

      Show
      Leave TRS as a separate OASIS OSLC specification that just happens to be developed by the Core TC. It can have a lifecycle separated and more or less independent from the rest of Core.

      Should TRS be done by the OASIS Core TC, but as a separate specification, not part of the core multi-part specification? TRS seems independent of Core and should be published as a separate specification, even though its done by the Core TC.

            Assignee:
            James Amsden (Inactive)
            Reporter:
            James Amsden (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: