Alistair Miles's Library tagged skos →  View Popular

Notice that one of the reason for refusing to use the paradimatic
broader/narrower/related also for mapping is linked to fundamental
considerations related to norm and authority.
On the one hand, creating paradigmatic relationships such as
skos:broader statement results from the core activity of KOS design,
which is supposed to imply e.g. certain soundness properties for the
resulting semantic network. Mapping is a different activity, where the
aim is not to create a new coherent KOS but to bridge two KOS with
relationships that may be of different qualitative and authoritative level.
My understanding is that the semantic commitment (with respect to the
original intended meaning of the linked concepts) is much stronger when
skos:broader than when using skos:broadMatch.
I would consider that this typically happens because a mapping link
between two schemes can be motivated by an application that has
requirements which are completely different from each of the ones that
guided the design of each mapped scheme.

This is actually why in the Primer [7] we have allowed for the use of
skos:broader *between* concept schemes and the use of skos:broadMatch
*within* concept schemes. Because these relations are of different
(epistemological??) level!

RESOLUTION: Even though it is acknowledged that SKOS semantic relation
properties will, in most applications, link conceptual resources that
stand within a same scheme, nothing in the SKOS model prevents their use
for concepts from different schemes. Similarly, even though it is
acknowledged that SKOS mapping relation properties will, in most
applications, link conceptual resources coming from different concept
schemes, nothing in the SKOS model prevents their use for concepts that
stand within a same scheme.

what i need is to be able to reorganize the hierarchy of the
concepts based on different schemes

to me this is valid only if the people that enrich
the concept scheme are different from the ones who own the scheme, because if
somebody owns the scheme that they can just create the missing skos:broader
instead of the skos:broadMatch