Major 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?
| Field | Original Value | New Value |
|---|---|---|
| Proposal | I am going to follow up with OASIS and the Core TC to find out the latest. | |
| 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? |
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 |
| Status | New [ 10000 ] | Open [ 1 ] |
| Summary | determine the proper namespace to use for our vocabulary(ies) | the PROMCODE TC should have a representative/liaison in the OSLC Core TC |
| Summary | the PROMCODE TC should have a representative/liaison in the OSLC Core TC | determine the proper namespace to use for our vocabulary(ies) |
| Description |
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 |
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? |
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"
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
"
Got a quick response from Steve Speicher: