[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCPROMCO-2) determine the proper namespace to use for our vocabulary(ies)
[ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37214#comment-37214 ] Robin Cover commented on OSLCPROMCO-2: -------------------------------------- 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" > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]