[ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Kennedy updated OSLCPROMCO-2:
----------------------------------
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?
was:
It is fine to have more than one to ensure regular coverage.
I suggest we only need volunteers, not nominees.
I note that Lonnie is already a member:
https://www.oasis-open.org/committees/membership.php?wg_abbrev=oslc-core
The Core TC is meeting bi-weekly, and the next meeting is May 1 at 10 AM EDT:
https://www.oasis-open.org/apps/org/workgroup/oslc-core/calendar.php
> 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)
