Hi Carl,
> IMHO as long contributor to standards - yes it makes sense. ...
>
> ... to change the URI of all classes and properties because some
> properties and some classes changed their semantic. .. mostly because to
> do otherwise would create massive editorial burden on KOS author'
>
Sure; no doubts about that. However this brings the question: who will
get the burden of this decision. This is a legitimate question that has
a different impact on different people.
I do think that if the entire namespace is changed, this put the burden
on hundred, eventually thousands, and even (in the futre) hundred of
thousands skos data publisher. If it is not, we put the burden on the
ontology development team.
I have no strong feeling about this matter, and I ahve no impact on any
decision. However this question interest me considering the increase of
such situations in many projects.
So, the question is: should we tell to 500 developers on 500 projects to
update their system, or to 20 or 30 people (in fact, there are only 2
editors) to manage the development and evolution of the ontology? I fear
the question is not that simple ;)
The problem with such "issues" is that I fear there is no answer to this
question that can resolve all issues....
Take care,
Fred