ISSUE-153

Last Call Comment: SKOS namespace change question

State:
CLOSED
Product:
SKOS
Raised by:
Sean Bechhofer
Opened on:
2008-10-02
Description:
Raised by Tim Berners-Lee in [1]:

Reading http://www.w3.org/TR/2008/WD-skos-reference-20080829/ ,

I sympathize very much with the people who want to keep the namespace  
the same.
  We're trying to get critical mass and cutting some of the data off  
and letting it float away by itself it is costly. I don't generate  
skos myself, but I have come across it.

Some people think it's important. I strongly suggest giving new names  
(within the same namespace)  to the five things which have changed,  
especially if they're rather obscure.

You have of course to evaluate the damage if you were to just make an  
erratum to skos 2005.

Did you in 2005 make a say about the change rules for skos 2005
I suggest to use new names and not change the namespace.

Tim

[1] http://lists.w3.org/Archives/Public/public-swd-wg/2008Sep/0084.html
Related emails:
  1. ISSUE-153: Last Call Comment: SKOS namespace change question (from dean+cgi@w3.org on 2008-10-02)
  2. Re: Comments on SKOS namespace change question (from sean.bechhofer@manchester.ac.uk on 2008-10-02)
  3. ISSUE-153: Comments on SKOS namespace change question (from simon.jupp@manchester.ac.uk on 2008-10-02)
  4. Status of LC comments (from sean.bechhofer@manchester.ac.uk on 2008-10-06)
  5. meeting record: 2008-10-07 SWD WG (from swick@w3.org on 2008-10-07)
  6. SKOS Namespace [ISSUE-153 and ISSUE-175] (from sean.bechhofer@manchester.ac.uk on 2008-10-31)
  7. Re: SKOS Namespace [ISSUE-153 and ISSUE-175] (from schreiber@cs.vu.nl on 2008-10-31)
  8. Re: [ALL] Agenda - Nov 04 2008 SWD telecon - 1600 UTC (from alistair.miles@zoo.ox.ac.uk on 2008-11-04)
  9. Re: [ALL] Agenda - Nov 04 2008 SWD telecon - 1600 UTC (from aisaac@few.vu.nl on 2008-11-04)
  10. [SKOS] ISSUE-153 / ISSUE-175 (was Re: [All] Agenda - Dec 02 2008 SWD telecon - 1600 UTC) (from alistair.miles@zoo.ox.ac.uk on 2008-12-02)
  11. ISSUE-153 draft response (from sean.bechhofer@manchester.ac.uk on 2008-12-02)
  12. [SKOS] Update on Last Call Comments (from alistair.miles@zoo.ox.ac.uk on 2008-12-02)
  13. Re: ISSUE-153 draft response (from alistair.miles@zoo.ox.ac.uk on 2008-12-02)
  14. Re: [SKOS] Update on Last Call Comments (from sean.bechhofer@manchester.ac.uk on 2008-12-02)
  15. ISSUE-153 Last Call Comment: SKOS namespace change question (from sean.bechhofer@manchester.ac.uk on 2008-12-02)
  16. meeting record: 2008-12-02 SWD WG telecon (from aisaac@few.vu.nl on 2008-12-03)

Related notes:

2008-10-06: See also: http://lists.w3.org/Archives/Public/public-swd-wg/2008Oct/0000.html http://lists.w3.org/Archives/Public/public-swd-wg/2008Oct/0004.html http://lists.w3.org/Archives/Public/public-swd-wg/2008Oct/0028.html

2008-11-10: ACTION: Accept

2008-12-11: CHANGE-TYPE: Editorial

2008-12-11: RESOLUTION: This was an issue that has been debated at length in the WG (see for example [2,3]) and the WG have seen merit in both options. The Last Call Draft proposes a new namespace. Recent discussions [4] have seen the WG return to a position where the SKOS vocabulary would be defined using the existing namespace URI. We do not intend to change the property names of the key semantic relations skos:broader and skos:narrower, as it was felt that this would effectively negate any benefit from retaining the namespace. This will, however, result in a change to the semantics of these relationships. However, as highlighted in [5], in principle applications should be able to make use of the machine-readable published schema. There may be impact on previously published vocabularies, which users will need to be made aware of. Note also that "old" vocabulary (for example skos:subject) will no longer be defined in the skos namespace. Historical versions of the schema will, however still be made available (although not at the SKOS namespace URI). Our proposal is thus to revert to the original SKOS namespace URI, and to add an appendix to the reference document (see [6]) discussing the issues above.

2008-12-15: Closed without response from commenter.

2008-12-16: COMMENTER-RESPONSE: None