OASIS OSLC Lifecycle Integration for Project Management of Contracted DeliveryIcon indicating the project type

OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery

Uploaded image for project: 'OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery'
  1. OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
  2. OSLCPROMCO-2

determine the proper namespace to use for our vocabulary(ies)

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None

      Description

      The contributed PROMCODE spec is in a namespace that does not resolve, i.e.: http://promcode.org/ns/pm#

      What is the policy for namespaces at OASIS, and what approach is the Core TC (and others) taking?

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          seanpk Sean Kennedy (Inactive) added a comment -

          Got a quick response from Steve Speicher:

          • the process and policy for this is something that is being discussed in the Core TC
          • his preference is to continue using http://open-services.net for continuity with existing OSLC specs
          Show
          seanpk Sean Kennedy (Inactive) added a comment - Got a quick response from Steve Speicher: the process and policy for this is something that is being discussed in the Core TC his preference is to continue using http://open-services.net for continuity with existing OSLC specs
          Hide
          Permalink
          robincover Robin Cover (Inactive) added a comment -

          As to HTTP-scheme URI references used to identify namespace names, the OASIS rules are published here in the Naming Directives:

          http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html

          With respect to TCs affiliated with the OASIS OSLC Member Section (like PROMCODE) and their specifications [1] and in general, with respect to the OASIS "OSLC" TCs' Work Products: some technical and policy issues about namespace URIs need to be discussed, and I plan to have such conversation with Steve Speicher (and possibly others) next week.

          • Robin

          https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2
          "The contributed PROMCODE spec is in a namespace that does not resolve, i.e.: http://promcode.org/ns/pm#
          [Not Found ; The requested URL /ns/pm was not found on this server.
          Apache/2.2.14 (Ubuntu) Server at www.promcode.org Port 80 ]
          What is the policy for namespaces at OASIS, and what approach is the Core TC (and others) taking?"

          Sean Kennedy commented
          https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2?focusedCommentId=37182&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-37182
          "Got a quick response from Steve Speicher:

          • the process and policy for this is something that is being discussed in the Core TC
          • his preference is to continue using http://open-services.net for continuity with existing OSLC specs"
          Show
          robincover Robin Cover (Inactive) added a comment - As to HTTP-scheme URI references used to identify namespace names, the OASIS rules are published here in the Naming Directives: http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html With respect to TCs affiliated with the OASIS OSLC Member Section (like PROMCODE) and their specifications [1] and in general, with respect to the OASIS "OSLC" TCs' Work Products: some technical and policy issues about namespace URIs need to be discussed, and I plan to have such conversation with Steve Speicher (and possibly others) next week. Robin https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2 "The contributed PROMCODE spec is in a namespace that does not resolve, i.e.: http://promcode.org/ns/pm# [Not Found ; The requested URL /ns/pm was not found on this server. Apache/2.2.14 (Ubuntu) Server at www.promcode.org Port 80 ] What is the policy for namespaces at OASIS, and what approach is the Core TC (and others) taking?" Sean Kennedy commented https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2?focusedCommentId=37182&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-37182 "Got a quick response from Steve Speicher: the process and policy for this is something that is being discussed in the Core TC his preference is to continue using http://open-services.net for continuity with existing OSLC specs"
          Hide
          Permalink
          seanpk Sean Kennedy (Inactive) added a comment -

          We've been the catalyst for dealing with this issue in the Core TC and with OASIS staff. Here is a note from Steve Speicher with a link to the latest details:

          "Note: I have tried to summarize this thread in the Core TC wiki [1] and what scenarios there are to we need to cover. Feedback on oslc-core@lists.oasis-open.org is welcome, especially if I missed any key scenarios or possible alternatives.

          [1]: https://wiki.oasis-open.org/oslc-core/VocabStableURINotes
          "

          Show
          seanpk Sean Kennedy (Inactive) added a comment - We've been the catalyst for dealing with this issue in the Core TC and with OASIS staff. Here is a note from Steve Speicher with a link to the latest details: "Note: I have tried to summarize this thread in the Core TC wiki [1] and what scenarios there are to we need to cover. Feedback on oslc-core@lists.oasis-open.org is welcome, especially if I missed any key scenarios or possible alternatives. [1] : https://wiki.oasis-open.org/oslc-core/VocabStableURINotes "

            People

            • Assignee:
              seanpk Sean Kennedy (Inactive)
              Reporter:
              seanpk Sean Kennedy (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: