Re: [Tm4j-developers] TM4J adds file: to resourceRef@href

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

Hi Stefan,

The issue here is that the /something/in/here.html gets absolutised when
it is imported against the base address of the topic map (presumably
something like file:/some/path/topicmap.xtm - you can check by using the
TM4J API to check what the value of that resourceRef is in the model -
it should be an absolute file: URL). Then when you export the path is
relativized (if possible) and so you end up with the path again, but it
looks like the scheme is not getting chopped off.

So the answer is that relativisation is done, using the base address of
the topic map and that the keeping of the scheme part of the URL should 
be treated as a bug.

Cheers,

Kal

PS - you are right, if/when we define serialisation we will need to
specify a way to handle this.

On Tue, 2004-05-18 at 15:20, Stefan Lischke wrote:
> Hi,
> 
> I just want to know why TM4J replaces any resourceRef@xlink:href element
> which has style "/something/in/here.html" with
> "file:/something/in/here.html".
> 
> I know i should provide a wellformed URI with
> "http://someserver.com/something/in/here.html" but someserver is not
> static, so im using it like in HTML where i can make
> 
> <a href="/something/in/here.html>this</a>
> 
> Does someone has any idea how to work with those "server relative" URI's ?
> 
> btw. we should define the behavior within TMAPI.
> 
> stefan
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Tm4j-developers mailing list
> Tm4...@li...
> https://lists.sourceforge.net/lists/listinfo/tm4j-developers
-- 
Kal Ahmed <ka...@te...>
techquila