Re: Subject Indicator Pages for standard PSIs

Benjamin Bock <[email protected]>
Newsgroups gmane.text.xml.xtm.general
Message-ID <[email protected]>
Hi Lars,

On Wed, Nov 10, 2010 at 4:33 PM, Lars Heuer <[email protected]> wrote:
> Hi Benjamin,
>
> [...]
>> I added this information to all PSIs.
>
> Good.
>
> [TMDM glossary terms]
>> No matter how useless they are from a TMDM perspective (I find them to
>> be valuable from a TMRM perspective)
>
> Please explain why they are valuable from a TMRM perspective.

The TMDM should be a legend from the TMRM perspective. To describe a
legend, one needs terms - and this is IMHO exactly what these subject
identifiers are about.

>
>
> [...]
>> Regarding "unwanted things": I also created
>> http://psi.topicmaps.org/iso13250/model/name-type with a note that it
>> is wrong and should not be used and pointed to the correct identifier.
>
> Hmmm.. Shouldn't we either not publish it or if you think it's
> valuable to have such an IRI, create a permanent redirect (301) to the
> new PSI?

I first thought about a redirect, too. But then I thought: If we just
redirect, nobody will know the reason, i.e. nobody will know the
status of the old PSI.
As a consequence, that would mean that all PSIs on this page would
always have the status "stable" or be forwarded to their stable
successor. In this case, we could just leave out the verbal status and
describe the status using the HTTP code. Or the publishing date as
last modified header?  :-)
I agree that it should not be listed on
http://psi.topicmaps.org/iso13250/model/ - but this would have needed
another change in the generator logic I was too lazy to do yet.

Best regards,
Benjamin

>
> Best regards,
> Lars
> --
> Semagia
> <http://www.semagia.com>
>
> <http://www.topicmaps.de/mailinglist/> German Topic Maps mailing list
> <http://tinytim.sourceforge.net/> Open Source Topic Maps engine
> <http://mappa.semagia.com/> Mappa - Python Topic Maps engine
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.