[topicmapmail] starting with topic maps: resources <-> topics
relationship?
Josema Alonso
josema@josema.net
Fri, 17 Oct 2003 10:45:44 +0200
> Why not just change the policies related to what can be posted to the web?
> You could insist that no page without DC would get put on a server. You
> still might want to be the person indexing the new pages, so create a
> workflow.
It is absolutely imposible. We do not have full control over many of the
subsites, for example.
And if you think I could force my designers to make it, is because you don't
know them ;-))
No, really, it's a particular environment. And this is not the only one.
There are many more like this one in Spain.
If I could have more power, I could make things a lot easier, but that's not
the case. This is a case where you have plain web designers. Think about
them being just a bit more than Dreamweaver users. Some of them even don't
know any HTML...and I can't do anything about it...unfortunately...
Too difficult to explain it all...
> Why use just one Topic Map file? The onotlogies used by these various
> colleges and departments are not going to be consistent. They must be
> consistent within themselves. So if you made each business unit do their
own
> Topic Map, they could do their own indexing as well. The idea that there
> will be only one ontology or taxonomy is false. You can see the parallels
in
>...
That's a good idea. I'm thinking about making just a high level topic map by
myself. Then I could assist them in making their own.
Anyway, I still need a solution for all the pages we have and I can't
control. Last time I took a look we had some 200K pages in our network and
many of them without title :-(
> Diversity provides a rich ecology. Semantic consistency eliminates
diversity
> and ecology. CMS and structured-text based single sourcing has the same
> effect. Soon you can't talk, because all the words that you use naturally
> have been redefined.
I understand the idea. Thanks :-)
> Being the IA doesn't mean doing everything yourself. Just establish the
> structure and enforce it with workflows and policy.
Oh, man, if I could...
Thanks for your opinions :-)