tm4j-users — Forum for users of the TM4J API or apps developed by this project.

[TM4J-users] unloading Topic Maps ?

[thomas f. <tho...@et...>]

Hi everyone

I'd like to unload/close the Topic Maps I have added in my
TopicMapProvider (for instance if a user wants to open a topic map, edit
it, and then save it or close it). The TopicMapProvider
interface doesn't seem to give that possibility. There is the 'close'
function, but it is not doing anything at the moment.

Can I do that ? How ?

Thanks !

Tom

[TM4J-users] Re: Beginning Question

[Niko P. <nik...@um...>]

Hi Cheng,
to add all jars in a directory, you can use the following script-snippets:

UNIX:
MY_DIR=/yourpath
unset CLASSPATH
for i in ${MY_DIR}/lib/* ; do
  if [ "$CLASSPATH" != "" ]; then
    CLASSPATH=${CLASSPATH}';'$i
  else
    CLASSPATH=$i
  fi
done

DOS:
@echo off
SET MYDIR=c:\yourpath
SET CLASSPATH=
echo %MYDIR%
for %%i in (%MYDIR%\*.jar) do call :append %%i
echo %CLASSPATH%
exit 0
:append
set CLASSPATH=%CLASSPATH%;%*
goto :eof


hope this helps...

regards,
niko

hug...@so... wrote:

> hi,
> I am begin with java and tm4j.I have build all tm4j.But I didn't know how
> can added all of the jar files in the lib directory to my CLASSPATH.I also want to know how to load it.
> Because my error is can't resolve symbol....
>
> thanks
> Cheng

Re: [TM4J-users] BaseUrl

[Kal A. <ka...@te...>]

Glad it worked! Thanks for the bug report - I'll put it in the
SourceForge tracker.

Cheers,

Kal

Niko Popitsch wrote:
> 
> Hi Kal,
> 
> Thanks for your answer. I tried this with the following code and it worked:
>         [...]
>         TopicMapFactoryImpl tmfi = new TopicMapFactoryImpl();
>         tmfi.setBaseLocator( baseLocator );
>         TopicMap tm = tmfi.createTopicMap( baseLocator );
>         [...]
> 
>  My problem was not only to set the right base locator but to avoid a NULL
> base locator in my topic maps. Because i want to use the original
> ResourceLocators to be used when i store the map to disk. I discovered the
> xtmWriter.setExportResourceIDs( true ); method to achieve this - but if the
> base locator is null, a NullpointerException is thrown (maybe this should be
> checked in the code ?).
> 
> Anyway,
> thanks a lot,
> regards
> 
> Niko
> 
> Kal Ahmed wrote:
> 
> > Hi Niko,
> >
> > xml:base only specifies the base URL to be used when resolving
> > references to locations outside the document being parsed (this is
> > consistent with the xml:base spec). To set the base locator of the topic
> > map itself, you should pass the Locator in to the TopicMapProvider
> > method you are using to get the TopicMap object (either createTopicMap()
> > or addTopicMap()).
> >
> > Hope this helps,
> >
> > Kal
> >
> > On 20 Mar 2002 13:52:37 +0100, Niko Popitsch wrote:
> > > HI,
> > > I am new with tm4j and so - for testing purposes - I wrote a small class
> > > that loads a topic map file (the A.xml file from the resource/test
> > > directory) - a code snippet can be found below.
> > > In this file the xml:base attribute in the root element is set to
> > > "http://ideabank.csir.co.za/A.xml"
> > > now I load this file and everything works fine. But if i output the
> > > ResourceLocator, the output is
> > > http://topicmap.techquila.com/default#n
> > > (i.e. the DEFAULT_BASE_URL of the XMLBuilder).
> > >
> > > The TopicMap.getBaseLocator() method of the loaded tm returns null.
> > >
> > > What did i miss here ?
> > > My unserstanding was, that - if there is an xml:base attribute specified
> > > - it is parsed by the XMLBuilder and passed to the topicmap. Am I wrong?
> > > If yes - how can i set the base locator?
> > >
> > > thanks,
> > > niko
> > >
> > > -------------------------------------------------------
> > >       saxParser = new SAXParser();
> > >       TopicMap tm = new TopicMapImpl();
> > >       XTMBuilder xtmBuilder = new XTMBuilder( tm );
> > >       XTMParser xtmParser  = new XTMParser( xtmBuilder );
> > >       saxParser.setContentHandler( xtmParser );
> > >       saxParser.parse( src );
> > >       TopicMap topicMap = xtmBuilder.getTopicMap();
> > > -------------------------------------------------------
> > >
> > >
> > > _______________________________________________
> > > Tm4j-users mailing list
> > > Tm4...@li...
> > > https://lists.sourceforge.net/lists/listinfo/tm4j-users
> > >
> > >

Re: [TM4J-users] BaseUrl

[Niko P. <nik...@um...>]

Hi Kal,

Thanks for your answer. I tried this with the following code and it worked:
        [...]
        TopicMapFactoryImpl tmfi = new TopicMapFactoryImpl();
        tmfi.setBaseLocator( baseLocator );
        TopicMap tm = tmfi.createTopicMap( baseLocator );
        [...]

 My problem was not only to set the right base locator but to avoid a NULL
base locator in my topic maps. Because i want to use the original
ResourceLocators to be used when i store the map to disk. I discovered the
xtmWriter.setExportResourceIDs( true ); method to achieve this - but if the
base locator is null, a NullpointerException is thrown (maybe this should be
checked in the code ?).

Anyway,
thanks a lot,
regards

Niko

Kal Ahmed wrote:

> Hi Niko,
>
> xml:base only specifies the base URL to be used when resolving
> references to locations outside the document being parsed (this is
> consistent with the xml:base spec). To set the base locator of the topic
> map itself, you should pass the Locator in to the TopicMapProvider
> method you are using to get the TopicMap object (either createTopicMap()
> or addTopicMap()).
>
> Hope this helps,
>
> Kal
>
> On 20 Mar 2002 13:52:37 +0100, Niko Popitsch wrote:
> > HI,
> > I am new with tm4j and so - for testing purposes - I wrote a small class
> > that loads a topic map file (the A.xml file from the resource/test
> > directory) - a code snippet can be found below.
> > In this file the xml:base attribute in the root element is set to
> > "http://ideabank.csir.co.za/A.xml"
> > now I load this file and everything works fine. But if i output the
> > ResourceLocator, the output is
> > http://topicmap.techquila.com/default#n
> > (i.e. the DEFAULT_BASE_URL of the XMLBuilder).
> >
> > The TopicMap.getBaseLocator() method of the loaded tm returns null.
> >
> > What did i miss here ?
> > My unserstanding was, that - if there is an xml:base attribute specified
> > - it is parsed by the XMLBuilder and passed to the topicmap. Am I wrong?
> > If yes - how can i set the base locator?
> >
> > thanks,
> > niko
> >
> > -------------------------------------------------------
> >       saxParser = new SAXParser();
> >       TopicMap tm = new TopicMapImpl();
> >       XTMBuilder xtmBuilder = new XTMBuilder( tm );
> >       XTMParser xtmParser  = new XTMParser( xtmBuilder );
> >       saxParser.setContentHandler( xtmParser );
> >       saxParser.parse( src );
> >       TopicMap topicMap = xtmBuilder.getTopicMap();
> > -------------------------------------------------------
> >
> >
> > _______________________________________________
> > Tm4j-users mailing list
> > Tm4...@li...
> > https://lists.sourceforge.net/lists/listinfo/tm4j-users
> >
> >

[TM4J-users] BaseUrl

[Niko P. <nik...@um...>]

HI,
I am new with tm4j and so - for testing purposes - I wrote a small class
that loads a topic map file (the A.xml file from the resource/test
directory) - a code snippet can be found below.
In this file the xml:base attribute in the root element is set to
"http://ideabank.csir.co.za/A.xml"
now I load this file and everything works fine. But if i output the
ResourceLocator, the output is
http://topicmap.techquila.com/default#n
(i.e. the DEFAULT_BASE_URL of the XMLBuilder).

The TopicMap.getBaseLocator() method of the loaded tm returns null.

What did i miss here ?
My unserstanding was, that - if there is an xml:base attribute specified
- it is parsed by the XMLBuilder and passed to the topicmap. Am I wrong?
If yes - how can i set the base locator?

thanks,
niko

-------------------------------------------------------
      saxParser = new SAXParser();
      TopicMap tm = new TopicMapImpl();
      XTMBuilder xtmBuilder = new XTMBuilder( tm );
      XTMParser xtmParser  = new XTMParser( xtmBuilder );
      saxParser.setContentHandler( xtmParser );
      saxParser.parse( src );
      TopicMap topicMap = xtmBuilder.getTopicMap();
-------------------------------------------------------

Re: [TM4J-users] starting problems / log4j

[Kal A. <ka...@te...>]

Hi,

At 22:49 12/03/2002 +0100, Ste...@gm... wrote:
>Hello,
>
>I have some problems getting started with tm4j.
>What I want to do is basically just read/write XTM-files into/from a memory
>model. I use VisualAge 3.5 with JDK 1.2.2 (source codes imported into
>repository)
>I try to run the sample code from the Developer's Guide to read/write
>from/to XTM-Files and I got the following errors:
>
>log4j:ERROR No appenders could be found for category
>(org.tm4j.topicmap.utils.XTMWriter).
>log4j:ERROR Please initialize the log4j system properly.
>
>What is log4j all about? It's not mentioned in any of the documentation.

Log4J is a system logging tool from Apache - it supports a wide range of 
runtime-configurable logging options - for more information on it, see 
http://jakarta.apache.org/log4j/docs/index.html. Log4J was a recent 
addition to TM4J and has not been documented yet - though it should be and 
I will be adding a bug regarding this

You need to add the following lines to your code:

import org.apache.log4j.BasicConfigurator;


Then somewhere in your code before calling any TM4J APIs, add:

BasicConfigurator.configure();

This will use the default configuration approach of Log4J which is to look 
for a file called log4j.properties on your CLASSPATH (see the Log4J 
documentation for more details on this). You can also use different 
Configurator classes depending upon your applications requirements and you 
can force particular logging options too.

One word of warning though - TM4J currently does not use Log4J very 
consistently. This will be cleaned up as we develop 0.7.0

Cheers,

Kal

>regards,
>
>
>-Stephan Grimm-
><Ste...@gm...>
>GERMANY
>
>
>
>--
>GMX - Die Kommunikationsplattform im Internet.
>http://www.gmx.net
>
>
>_______________________________________________
>Tm4j-users mailing list
>Tm4...@li...
>https://lists.sourceforge.net/lists/listinfo/tm4j-users

[TM4J-users] starting problems / log4j

[<Ste...@gm...>]

Hello,

I have some problems getting started with tm4j.
What I want to do is basically just read/write XTM-files into/from a memory
model. I use VisualAge 3.5 with JDK 1.2.2 (source codes imported into
repository)
I try to run the sample code from the Developer's Guide to read/write
from/to XTM-Files and I got the following errors:

log4j:ERROR No appenders could be found for category
(org.tm4j.topicmap.utils.XTMWriter).
log4j:ERROR Please initialize the log4j system properly.

What is log4j all about? It's not mentioned in any of the documentation.

regards,


-Stephan Grimm-
<Ste...@gm...>
GERMANY



-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

Re: [TM4J-users] TopicMapUtil - Memory Implementation (Bug or Feature)

[Kal A. <ka...@te...>]

At 12:14 28/02/2002 +0100, you wrote:
>Hi,
>
>i've got a little question about...
>org.tm4j.topicmap.memory.getObjectsOfType(Topic,Collection)
>
>Why does it return only Topic and Association objects?
>What about other topicmap objects like Occurences and Members, which are 
>also instances of a specific type?

Thats a bug! I've added it to the SourceForge bug tracker  (ID = 523824). 
The fix is trivial so I will aim to have it fixed for inclusion in 0.6.1.

Cheers,

Kal

[TM4J-users] TopicMapUtil - Memory Implementation (Bug or Feature)

[<kgu...@no...>]

Hi,

i've got a little question about...
org.tm4j.topicmap.memory.getObjectsOfType(Topic,Collection)=20

Why does it return only Topic and Association objects?
What about other topicmap objects like Occurences and Members, which are =
also instances of a specific type?


Regards Kai G=FClzau

[TM4J-users] Survey results

[Kal A. <ka...@te...>]

Hi all,

Unfortunately, SourceForge's survey system seems to have let us down - very 
few questions had any results logged for them at all. So rather than try 
and repeat that experiment, I have entered all of the proposed features as 
tasks in the SourceForge Task tracker 
(http://sourceforge.net/pm/?group_id=27895). As you will see, there are 
currently 3 subprojects - Unassigned, 0.6.1 and 0.7.0. My feeling now is 
that 0.6.1 should contain only bug fix tasks (in fact, there is probably no 
need to enter tasks as they are already tracked in the bug system). I have 
added what I think are the key priorities for 0.7.0 to the 0.7.0 
subproject. If anyone would like to volunteer for any of these tasks, that 
would be great!. If any one would like to propose another task for the 
0.7.0 release, please let me know - I would not mind moving some more of 
the tasks into 0.7.0, but only if we have volunteers to do the extra work.

Cheers,

Kal

Re: [TM4J-users] beginner's question

[Kal A. <ka...@te...>]

Hi Brian,

Unfortunately, the example with TheBrain interface has been removed from 
the distribution now because Natrificial (the developers of TheBrain) 
removed the free download of the SDK from their site. To get started with 
some example apps, you could take a look at the two command-line 
applications org.tm4j.topicmap.cmd.Stats.java (and the StatsProcessor.java 
app) and org.tm4j.topicmap.cmd.Merge.java.

Hope this helps you get started - if you have any specific API questions, 
please feel free to ask!

Cheers,

Kal

At 09:01 17/02/2002 -0500, Brian Wolf wrote:
>I am new to topic maps. Except for whats  in the developers guide, I do 
>not find any example code in the distribution, or applications (saw 
>reference to example  with TheBrain  interface somewhere) Am I looking in 
>the wrong places?

[TM4J-users] beginner's question

[Brian W. <br...@kn...>]

I am new to topic maps. Except for whats  in the developers guide, I do =
not find any example code in the distribution, or applications (saw =
reference to example  with TheBrain  interface somewhere) Am I looking =
in the wrong places?

[TM4J-users] TM4J 0.7.0 Features Survey

[Kal A. <ka...@te...>]

Please take a few minutes to complete the survey now online at:

https://sourceforge.net/survey/survey.php?group_id=27895&survey_id=12717

This will help us prioritise features to be developed in 0.7.0 and beyond. 
This survey will be active from today through to Monday.

Feel free to continue discussion on the mailing lists too!

Cheers,

Kal

Re: [TM4J-users] Way to find _implicit_ topics ?

[Kal A. <ka...@te...>]

Hi Tom,

The short answer to your question is "No". A longer answer is "No, not 
directly, but perhaps with a little coding trickery..."

Implicit topics are only created under the following conditions:
         1) A topic is referred to via a <topicRef> element
         2) A subject is referred to via a <subjectIndicatorRef> element 
anywhere other than inside a <subjectIdentity> element.
         3) Three implicit topics are created to represent the XTM 
class-instance association and its roles

In case (1) the generated topic has only a resourceID property (determined 
from the -href- attribute of the <topicRef> element)
In case (2) the generated topic has only a single value for the 
subjectIndicator property (the value specified in the -href- attribute of 
the <subjectIndicatorRef> element
In case (3) the generated topics have only a single value for the 
subjectIndicator property (these values can be found specified as strings 
in org.tm4j.topicmap.XTMPSI

In all cases, the generated topics should have no other properties.

So, from this you could infer that a topic is an implicit topic if:
         a) It has only a resourceID property or
         b) It has only a single value for the subjectIndicator property

Implicit topics should have no values for any property other than the ID 
property.

In fact, any topic which conforms to either (a) or (b) could be ** treated 
** as an implicit topic regardless of its original source (because it could 
be serialised using a topicRef or subjectIndicatorRef). TM4J does not 
directly support this right now - though you could create your own export 
processor to handle this (use org.tm4j.topicmap.utils.XTMWriter.java  as a 
starting point).

Thinking this through, it might be useful to have some way of determining 
which topics actually existed in the imported XTM file(s) and which were 
created as implicit topics - a simple boolean flag managed by the 
XTMBuilder should suffice. I'll add it to the list of possible features for 
0.7.0

Cheers,

Kal

At 13:47 13/02/2002 +0100, Thomas Francart wrote:
>Hi all
>
>I'm quite new to TM4J ; I was wondering if there was a way to distinguish 
>between implicit and "explicit" topics, once the Topic Map is loaded ? ( I 
>am using the memory implementation for the moment ).
>
>Thanks !
>
>Tom

[TM4J-users] Way to find _implicit_ topics ?

[Thomas F. <tho...@ut...>]

Hi all

I'm quite new to TM4J ; I was wondering if there was a way to =
distinguish between implicit and "explicit" topics, once the Topic Map =
is loaded ? ( I am using the memory implementation for the moment ).

Thanks !

Tom

Re: [TM4J-users] TM4J 0.7.0 Features (Long)

[Gerd M. <Ger...@sm...>]

Hi,

I'd like to add one more issue, although I don't think that this will be part
of 0.7.0. I think we need a query language and I vote for Tolog. Maybe my
company will hire a student in the next few months who will write his
diploma thesis about Tolog. I'll get back to you if I know more about it.

Also I'm particular interested in developing the TM4J frontends for Cocoon
and the graph visualisation. If I can spare some time I'll give a helping
hand on this issues.

Best Regards,
gerd

> Now that 0.6.0 has been released, I am starting work on collecting the 
> features list for 0.7.0. Below is a list of some of the features I have in 
> mind. I would like to hear from anyone that has suggestions for additional 
> features. I would like to make the release cycle for 0.7.0 much shorter 
> than we had for 0.6.0, but that does mean that , without a lot of help, not 
> all of these features will make it in to the release. What I am proposing 
> to do is to collect together a list of the features proposed and create a 
> survey on SourceForge which we can all vote in and then try and partition 
> the voted on list into 0.7.0 and post-0.7.0 features.
> 
> Here are the features I have so far:
> 
> Locator resolution interfaces [REQUIRED]
>    The current Locator interface provides no way to retrieve the data at 
> the end of the locator.
>    This is *required* in order to be able to properly support the mergeMap 
> feature (see below).
>    This would probably take the form of a separate LocatorResolver 
> interface which would return
>    a data stream for a given Locator. The architecture for this would be 
> flexible and support
>    plug-in extensibility for different locator notations. This feature 
> would include the following
>    sub-features:
>    o  Pluggable URI resolution implementation
>    o    http: URI resolution
>    o    file: URI resolution
>    o  Catalog-based locator resolution implementation
> 
> ID round-tripping [REQUIRED]
>    Support the direct mapping of -id- attribute values in the input XTM 
> file into the value of the
>    ID property of the Java objects created by the XTMBuilder. This would 
> enable complete
>    round-tripping of -id- attribute values in most trivial cases. When 
> loading multiple XTM files
>    into a single TopicMap object, some additional attribute processing may 
> be required to
>    prevent DuplicateObjectIDExceptions getting thrown (alternatively, this 
> could just happen...)
> 
> Merge-map support [REQUIRED]
>    This is the last major piece of XTM support required for TM4J.
> 
> External topic reference processing [REQUIRED]
>    This is the *other* last major piece of XTM support required for TM4J ;-)
> 
> More flexible indexing architecture
>    Split the indexes away from the TopicMap object - this would make it 
> easier to interface
>    with persistent storage systems which provide an alternative means of 
> query (e.g. Ozone
>    or an RDBMS). It would also significantly simplify the TopicMap 
> implementations.
>    Elements of this feature include:
>      o  Basic index interface
>      o  In-memory Index implementations
>      o  Ozone Index implementations
> 
> Rework DOM implementation to work on XML-DB (http://www.xmldb.org/index.html)
>    XML-DB is a standard API for XML repositories, which is based on DOM and
>    XPath. The work already started on the DOM implementation should be pretty
>    straightforward to port to XML-DB. The original intention of building a 
> TM4J interface
>    on an in-memory DOM structure does not need to be abandoned - the two
>    could probably be supported by a single interface.
> 
> JDBC/RDBMS implementation
>    Apparently some people still like relational systems...
> 
> New TMNav architecture
>    This would include:
>    o  TMNav browser implementation
>    o  Touchgraph visualisation
>    o  TMNav editor implementation
> 
> Improve consistency of use of Log4J
>    o  Ensure only Log4J is used for logging warnings/errors
>    o  Ensure command line apps and other apps initialise Log4J correctly
>    o  Create default Log4J initialisation object
> 
> Support for ISO Topic Map Syntax
>    o  Support at least import of topic maps in ISO syntax (with the
>        HyTime links replaced with URI references.
> 
> Dynamic web publishing application (based on Cocoon)
>    o  Cocoon generator for topic maps
>    o  Some XSLT templates for viewing topics
>    o   Additional utility classes for extracting and sorting topic names,
>        occurrences associations etc.
> 
> Static/dynamic web publishing application (based on Velocity)
>    o Utility classes for extracting and sorting topic names, occurrences,
>       associations etc.
>    o Configurable framework for using Velocity templates to view topic map
>       objects
>     o Wrapper application to allow deployment in a servlet container
>     o Wrapper application to allow invocation of the processing from the 
> command line
> 
> Support Canonical XTM output
>    This could form the basis for conformance testing.
>    See http://www.ontopia.net/topicmaps/materials/cxtm.html for a description
>    of Canonical XTM format
> 
> Support LTM input
>    This is a simple text format for topic maps (without the XML verbosity)
>    See http://www.ontopia.net/download/ltm.html for a description of LTM.
> 
> Please note, this is not a closed list ! If you have other suggestions, 
> feel free to add them. And just because something is not initially 
> suggested or not voted in for release 0.7.0 does not necessarily mean that 
> it cannot be included in that release - as long as some one is willing to 
> take on the work.
> 
> I look forward to hearing your thoughts!
> 
> Cheers,
> 
> Kal
> 
> 
> _______________________________________________
> Tm4j-users mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-users


________________________________________________________________
Gerd Mueller                                    ge...@sm...     
SMB GmbH                                  http://www.smb-tec.com

[TM4J-users] TM4J 0.7.0 Features (Long)

[Kal A. <ka...@te...>]

Hi,

Now that 0.6.0 has been released, I am starting work on collecting the 
features list for 0.7.0. Below is a list of some of the features I have in 
mind. I would like to hear from anyone that has suggestions for additional 
features. I would like to make the release cycle for 0.7.0 much shorter 
than we had for 0.6.0, but that does mean that , without a lot of help, not 
all of these features will make it in to the release. What I am proposing 
to do is to collect together a list of the features proposed and create a 
survey on SourceForge which we can all vote in and then try and partition 
the voted on list into 0.7.0 and post-0.7.0 features.

Here are the features I have so far:

Locator resolution interfaces [REQUIRED]
   The current Locator interface provides no way to retrieve the data at 
the end of the locator.
   This is *required* in order to be able to properly support the mergeMap 
feature (see below).
   This would probably take the form of a separate LocatorResolver 
interface which would return
   a data stream for a given Locator. The architecture for this would be 
flexible and support
   plug-in extensibility for different locator notations. This feature 
would include the following
   sub-features:
   o  Pluggable URI resolution implementation
   o    http: URI resolution
   o    file: URI resolution
   o  Catalog-based locator resolution implementation

ID round-tripping [REQUIRED]
   Support the direct mapping of -id- attribute values in the input XTM 
file into the value of the
   ID property of the Java objects created by the XTMBuilder. This would 
enable complete
   round-tripping of -id- attribute values in most trivial cases. When 
loading multiple XTM files
   into a single TopicMap object, some additional attribute processing may 
be required to
   prevent DuplicateObjectIDExceptions getting thrown (alternatively, this 
could just happen...)

Merge-map support [REQUIRED]
   This is the last major piece of XTM support required for TM4J.

External topic reference processing [REQUIRED]
   This is the *other* last major piece of XTM support required for TM4J ;-)

More flexible indexing architecture
   Split the indexes away from the TopicMap object - this would make it 
easier to interface
   with persistent storage systems which provide an alternative means of 
query (e.g. Ozone
   or an RDBMS). It would also significantly simplify the TopicMap 
implementations.
   Elements of this feature include:
     o  Basic index interface
     o  In-memory Index implementations
     o  Ozone Index implementations

Rework DOM implementation to work on XML-DB (http://www.xmldb.org/index.html)
   XML-DB is a standard API for XML repositories, which is based on DOM and
   XPath. The work already started on the DOM implementation should be pretty
   straightforward to port to XML-DB. The original intention of building a 
TM4J interface
   on an in-memory DOM structure does not need to be abandoned - the two
   could probably be supported by a single interface.

JDBC/RDBMS implementation
   Apparently some people still like relational systems...

New TMNav architecture
   This would include:
   o  TMNav browser implementation
   o  Touchgraph visualisation
   o  TMNav editor implementation

Improve consistency of use of Log4J
   o  Ensure only Log4J is used for logging warnings/errors
   o  Ensure command line apps and other apps initialise Log4J correctly
   o  Create default Log4J initialisation object

Support for ISO Topic Map Syntax
   o  Support at least import of topic maps in ISO syntax (with the
       HyTime links replaced with URI references.

Dynamic web publishing application (based on Cocoon)
   o  Cocoon generator for topic maps
   o  Some XSLT templates for viewing topics
   o   Additional utility classes for extracting and sorting topic names,
       occurrences associations etc.

Static/dynamic web publishing application (based on Velocity)
   o Utility classes for extracting and sorting topic names, occurrences,
      associations etc.
   o Configurable framework for using Velocity templates to view topic map
      objects
    o Wrapper application to allow deployment in a servlet container
    o Wrapper application to allow invocation of the processing from the 
command line

Support Canonical XTM output
   This could form the basis for conformance testing.
   See http://www.ontopia.net/topicmaps/materials/cxtm.html for a description
   of Canonical XTM format

Support LTM input
   This is a simple text format for topic maps (without the XML verbosity)
   See http://www.ontopia.net/download/ltm.html for a description of LTM.

Please note, this is not a closed list ! If you have other suggestions, 
feel free to add them. And just because something is not initially 
suggested or not voted in for release 0.7.0 does not necessarily mean that 
it cannot be included in that release - as long as some one is willing to 
take on the work.

I look forward to hearing your thoughts!

Cheers,

Kal

Re: [TM4J-users] topic's id

[Kal A. <ka...@te...>]

Hi,

The best way to identify a topic (or other topic map object) is to use the 
resourceLocator property of TopicMapObject 
(TopicMapObject.getResourceLocator()). The ID property is an internal 
unique id assigned when the topic map is loaded, the actual value of the 
-id- attribute is resolved against the address of the topic map itself to 
create a new URI which is stored as the resourceLocator of the object. With 
TM4J 0.6.0 TopicMapObject.getResourceLocator() returns a Locator object 
which you can test against a Locator which represents the full URI of the 
object you want.

TopicMap tm;

// Load the topic map here

// Generate the locator of the object we want to retrive by resolving #id 
against the base locator of the topic map
Locator loc = tm.getBaseLocator().resolveRelative("URI", "#mytopic");
// Get the
TopicMapObject tmo = tm.getObjectByResourceLocator(loc);

In TM4J 0.5.0, TopicMapObject.getResourceID() and 
TopicMap.getObjectByResourceID() perform the same function, but with 
strings rather than Locator objects.

Hope this helps,

Kal

At 13:29 15/01/2002 +0100, you wrote:
>i have developled a topic map with TM4J.
>After several tries i have found that the id of a topic changes itself 
>frequently ( each time when the topic map is
>parsed and the id is automatically provided by the system).
>I would like to ask by which mean a topic in a topic map can be 
>identified?? Id? Basename+scope? and with which
>method?
>
>with best regards.
>Yuan Yanping

[TM4J-users] topic's id

[Yanping Y. <yps...@cs...>]

i have developled a topic map with TM4J.
After several tries i have found that the id of a topic changes itself =
frequently ( each time when the topic map is=20
parsed and the id is automatically provided by the system).
I would like to ask by which mean a topic in a topic map can be =
identified?? Id? Basename+scope? and with which
method?=20

with best regards.
Yuan Yanping

Re: [TM4J-users] Software Design and tm4j

[<ka...@te...>]

Hi Hans-Gerd,

"gmx" <Han...@gm...> wrote:
>Hello,
>
>Thank you for this wonderfull API.
>
>I have a design-question. I want to use a
>digital whiteboard in a multiuser learn environment as graphical user
>interface for a topic map. The topicmap function is one new feature that is
>added by me to this project. I'm a student in informatic and this is my
>final work.
>
>I make classes that implements the interfaces and have an associated
>Topic-Object, created with the concrete implemtation TopicImpl, in my class.
>
>Looks like this:
>
>public class SteamTopic implements Topic
>{
>
>  /** The Topic-Object for the Topic. Look in Techquila-Api for more
>Information about
>   * this object. It is used in this class to represent the semantic-view on
>the topic.
>   */
>  Topic sTopic;
>
>  /** The grafical representation of the topic-object. It is inherited from
>the
>   * whiteboard-components.
>   */
>  GraphicComponent sTopicRepresentation;
>
>  /**
>   * Adds an occurrence to this Topic.
>   * @param occurs The Occurrence to be added.
>   */
>  public void addOccurrence(Occurrence occurs)
>  {
>    sTopic.addOccurrence( occurs );
>    // and my special stuff, I need at this point
>  }
>  // The other methods, implemented in the same matter.
>
>I'm at the beginning of the implementation and I want to ask you, if this is
>the right design to use your API. I'm not experienced in programming big
>applications and design. At the moment I make just a little prototype to
>test the function and usability of the whiteboard for this purpose but I
>want to reuse my code in the project (sometime in the next month).
>

This looks like a good starting point. Of course, the only problem is the amount of typing that you have to do (to provide implementations of all of the methods of the Topic interface), but the only other real option is to inherit from one of the Topic implementations (which would then restrict you to a single implementation).


BTW if you are using TM4J 0.5.0 for this work, be warned that the next release of TM4J has a large number of interface changes and you might be better off using the latest CVS tree instead.

>It is very unusal for me, that there are deprecated methods in an interface.
>Is this a good design? I have never heard about deprecated methods in
>interfaces so this is a very intresting question for me.
>

I put the deprecation markings in the interfaces (rather than in the implementations) because it is my understanding that the deprecation (like other Javadoc tags) is "inherited" by all implementations of the interface. Does anyone else know if I am mistaken in that ?

Cheers,

Kal

[TM4J-users] Software Design and tm4j

[gmx <Han...@gm...>]

Hello,

Thank you for this wonderfull API.

I have a design-question. I want to use a
digital whiteboard in a multiuser learn environment as graphical user
interface for a topic map. The topicmap function is one new feature that is
added by me to this project. I'm a student in informatic and this is my
final work.

I make classes that implements the interfaces and have an associated
Topic-Object, created with the concrete implemtation TopicImpl, in my class.

Looks like this:

public class SteamTopic implements Topic
{

  /** The Topic-Object for the Topic. Look in Techquila-Api for more
Information about
   * this object. It is used in this class to represent the semantic-view on
the topic.
   */
  Topic sTopic;

  /** The grafical representation of the topic-object. It is inherited from
the
   * whiteboard-components.
   */
  GraphicComponent sTopicRepresentation;

  /**
   * Adds an occurrence to this Topic.
   * @param occurs The Occurrence to be added.
   */
  public void addOccurrence(Occurrence occurs)
  {
    sTopic.addOccurrence( occurs );
    // and my special stuff, I need at this point
  }
  // The other methods, implemented in the same matter.

I'm at the beginning of the implementation and I want to ask you, if this is
the right design to use your API. I'm not experienced in programming big
applications and design. At the moment I make just a little prototype to
test the function and usability of the whiteboard for this purpose but I
want to reuse my code in the project (sometime in the next month).

It is very unusal for me, that there are deprecated methods in an interface.
Is this a good design? I have never heard about deprecated methods in
interfaces so this is a very intresting question for me.

Thank you for your help

Hans-Gerd Wiegard

Re: Re: [TM4J-users] topic IDs

[Martin S. <hu...@we...>]

Hi,

I thought that the ID's are generated for the sake of merging.
getResourceID() is all I needed.

Thank You

Martin Stockhammer

Kal Ahmed <ka...@te...> schrieb am 18.12.01:
> Hi Martin,
>=20
> The topic IDs have not been lost - they are available using the method=20
> getResourceID(). The reason for having a different (internal) identifier=
=20
> for objects is that using topic map merging it is possible to get object=
s=20
> in a single TM4J TopicMap which have come from multiple different XTM=20
> files, and so it is useful to have a single, guaranteed unique identifie=
r=20
> (which is what getID() returns) as well as the originally assigned=20
> identifier (which is what getResourceID() returns).
>=20
> When you export the file, the internal, guaranteed unique IDs are used.=20
> However, you can override this behaviour by creating your own=20
> TopicMapWalker which passes the value from getResourceID() to its handle=
r=20
> rather than the value of getID().
>=20
> Hope this helps,
>=20
> Kal
>=20
> At 08:18 18/12/2001 +0100, Martin Stockhammer wrote:
> >Hello,
> >
> >after importing a topic map from an xtm-file I recognised that the
> >topic IDs of the XTM-File are ignored. Why =3F
> >
> >I would like to use the IDs of the file, because they are better readab=
le.
> >
> >If I export the topic map to a file, are the new IDs used=3F
> >
> >Greetings
> >
> >Martin Stockhammer
> >mailto:hu...@we...
> >
> >
> >=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F
> >Darf es ein bisschen mehr sein=3F Mehr Speicher, mehr Mail, mehr Erlebnis=
,
> >mehr Pr=E4mie, mehr WEB.DE.  Der WEB.DE Club - http://club.web.de
> >
> >
> >=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> >Tm4j-users mailing list
> >Tm4...@li...
> >https://lists.sourceforge.net/lists/listinfo/tm4j-users
>=20
>=20
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Tm4j-users mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-users=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!=20
Beim WEB.DE Lottoservice: http://tippen2.web.de/=3Fx=3D13

Re: [TM4J-users] topic IDs

[Kal A. <ka...@te...>]

Hi Martin,

The topic IDs have not been lost - they are available using the method=20
getResourceID(). The reason for having a different (internal) identifier=20
for objects is that using topic map merging it is possible to get objects=20
in a single TM4J TopicMap which have come from multiple different XTM=20
files, and so it is useful to have a single, guaranteed unique identifier=20
(which is what getID() returns) as well as the originally assigned=20
identifier (which is what getResourceID() returns).

When you export the file, the internal, guaranteed unique IDs are used.=20
However, you can override this behaviour by creating your own=20
TopicMapWalker which passes the value from getResourceID() to its handler=20
rather than the value of getID().

Hope this helps,

Kal

At 08:18 18/12/2001 +0100, Martin Stockhammer wrote:
>Hello,
>
>after importing a topic map from an xtm-file I recognised that the
>topic IDs of the XTM-File are ignored. Why ?
>
>I would like to use the IDs of the file, because they are better readable.
>
>If I export the topic map to a file, are the new IDs used?
>
>Greetings
>
>Martin Stockhammer
>mailto:hu...@we...
>
>
>___________________________________________________________________________=
___
>Darf es ein bisschen mehr sein? Mehr Speicher, mehr Mail, mehr Erlebnis,
>mehr Pr=E4mie, mehr WEB.DE.  Der WEB.DE Club - http://club.web.de
>
>
>_______________________________________________
>Tm4j-users mailing list
>Tm4...@li...
>https://lists.sourceforge.net/lists/listinfo/tm4j-users

[TM4J-users] topic IDs

[Martin S. <hu...@we...>]

Hello,

after importing a topic map from an xtm-file I recognised that the
topic IDs of the XTM-File are ignored. Why =3F

I would like to use the IDs of the file, because they are better readable.=


If I export the topic map to a file, are the new IDs used=3F

Greetings

Martin Stockhammer
mailto:hu...@we...


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F
Darf es ein bisschen mehr sein=3F Mehr Speicher, mehr Mail, mehr Erlebnis,=20
mehr Pr=E4mie, mehr WEB.DE.  Der WEB.DE Club - http://club.web.de

Re: [TM4J-users] TM4J project web site & XTM (was RE: new member)

[Kal A. <ka...@te...>]

Its taken a little while to get round to answering this ...sorry about that!

At 12:32 23/11/2001 +0100, you wrote:
>Hello again!
>
>[Kal]
> > After all, the (IMHO) best servlet container is Tomcat, and thats open
> > source... I would be interested to see how far an XSLT-only implementation
> > could get. I know that at least one consultant has successfully used XSLT
> > as a means of publishing topic maps.
>
>Which company was this?

The company was Cogitech (www.cogx.com) - you can find some more examples 
and some interesting papers on creating and publishing both topic maps and 
RDF using XSLT.

>[Kal]
> > Apart from the ability to swap stylesheets, what other advantages does
> > Cocoon offer ? Can anyone summarize them for us ?
>
>Not that this is anywhere near a decent *summary*, but there's a few things
>I've noticed in Cocoon which don't seem to be implemented as nicely in
>Velocity. Nonetheless I wouldn't say I were an expert at either, mind you.
>
>* Better XSLFO support: wouldn't it be awesome to be able to browse, say,
>the TM4J dev guide, in XHTML, on-line and at the same time have a PDF version
>of same available at one click, all of which is generated from a single XTM
>source tree?
>
>* Nice built-in caching of XSLT output.
>
>* No nitty-gritty special scripting language, just pure Java and XML for
>Markup nerds like me. OK, I admit that last comment wasn't quite useful. :-)

The caching and the use of compiled XSLT "translets" looks quite good. I 
notice that Cocoon 2.0 is now an official release. From what I have read, I 
think it should be possible to develop a "Generator" for Cocoon that 
extracts topic map data (as XTM format XML ?) and passes it on to what ever 
transformer or serializer modules you care to include. This would work 
really nicely for a "dynamic" site - where you are able to run a servlet 
container on the host machine. However, for our Sourceforge site, and for 
countless other "simple" sites, running servlets is not an option - there 
may be some PHP or Perl support and maybe an mSQL database (if you are 
lucky) but for the most part, you are limted to static HTML. For those 
sites, a Velocity based, scripted static transformation might be a better 
way to go.

If there are volunteers to take on the Cocoon 2.0 generator, I think that 
would be a really worthwhile application. Also if anyone cares to volunteer 
for developing a framework for static transformation (using XSLT or 
Velocity or a combination of the two), that would also be really worthwhile.

I think this discussion is rapidly becoming more of a technical / TM4J 
development issue than an issue of website content. I am therefore copying 
the message to tm4j-developers and would ask that all replies get sent to 
that list.

Cheers,

Kal