[OASIS Issue Tracker] (OSLCPROMCO-2) determine the proper namespace to use for our vocabulary(ies)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37241#comment-37241 ] 

Sean Kennedy commented on OSLCPROMCO-2:
---------------------------------------

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 
"

> determine the proper namespace to use for our vocabulary(ies)
> -------------------------------------------------------------
>
>                 Key: OSLCPROMCO-2
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Task
>            Reporter: Sean Kennedy
>            Assignee: Sean Kennedy
>
> 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? 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)