Re: BATH PROFILE - XML RECORDS

Hi Sebastian,

Thanks for the diagnostic info!  I will attempt to follow it up on the sever
side.  I have observed (probably) the same issue in my client, in the form
of two or four extra bytes appearing at the beginning of the xml content
after decoding by the OCLC BER utilities.  Not knowing whether it was a
client- or server- issue, but not having the source code for the server,
I set my client to ignore the extra bytes.  However, I see now that a
more definite solution is called for.

FYI, this is an ISITE server running on an NT.


thanks,
-Steve Gregory



----- Original Message -----
From: "Sebastian Hammer" <quinn@indexdata.dk>
To: "Stephen P. Gregory" <gregory@aclin.org>; <www-zig@w3.org>; "Mark Crane"
<mcrane@iii.com>
Cc: "_Steve Gregory" <gregory@aclin.org>
Sent: Wednesday, October 02, 2002 3:00 AM
Subject: Re: BATH PROFILE - XML RECORDS


>
> At 15:59 01-10-2002 -0600, Stephen P. Gregory wrote:
>
> >This is convenient, as we would like to test our latest server:
> >
> >site = Future Home of the Colorado FGDC Node
> >hostname = fryingpan.aclin.org
> >port = 210
> >dbname = colorado
> >recordSyntax = XML or SUTRS
>
> This target appears to use an invalid encoding for XML records -- they
come
> back as a BER-encoded datatype, whereas I am pretty sure that the proper
> way to represent XML is as an "Octet-aligned" type in the EXTERNAL.
>
> Ray, we looked around a bit but had a hard time finding a hard statement
to
> this effect on the Maintenance agency site, or indeed in the record syntax
> list.
>
> --Sebastian
> --
> Sebastian Hammer, Index Data <http://www.indexdata.dk/>
> Ph: +45 3341 0100, Fax: +45 3341 0101

Received on Wednesday, 2 October 2002 09:11:59 UTC