Suppose I have an XML document with Russian element and attribute names.
And I would like to access the document using Plain URL Addressing.
Doctype is Russian as well and that is why Tamino returns 404 error.
What encoding should I use for doctype or Tamino provides direct access only for documents which doctype has only ASCCI letters?
By the way it doesn’t work in Tamino API for Java either.
Thank you in advance
I tried in turkish characters. There are two subject.
One is encoding. You should use utf-8. Like in url
When you are loading data by interactive interface first you should save as utf-8.
Doctype in Turkish i can access vi interractive interface and i can load data.
No problem. But via URL based access you should use unicode representations.
for unicode in url ;
as you know unicode has two byte so in url you should use two characters for a unicode character. easy way to find out which characters,
in browser as url write www.yourunicode.com
then it will give you following error
Technical Information (for support personnel)
This error indicates that the gateway could not find the IP address of the Web site you are trying to access.
ISA Server: hititcsserver.hititcs.com
URL: <A HREF="http://www.
If you have a doctype that is uses characters from the Russian alphabet encoded say as utf-8 then I don’t think its going to be possible to directly address a document by using plain URL addressing (i.e. using HTTP GET).
I think the reason is that the HTTP GET request will have utf-8 characters and just thinking about it how would a HTTP server know what the encoding is?
Since the Russian characters when encoded using utf-8 are characters who’s decimal value is > 255 (i.e beyond the normal ASCII 8-bit limit), the web server cannot understand the request. I’ve tried this with IIS (which returns 404) and Apache returns 400 Bad Request.
I tried it , it works.
Hmmm, thats interesting. I couldn’t not get it to work: I tried from a browser, I tried with telnet! and I also tried with C++ using the MS XMLHTTP control and I simply got a very consistent answer: 404. This is even without Tamino: I created a file with a Russian filename and IIS cannot serve it up. Apache gives up with 400 error.
What web server are you using? And have you done any special configuration?
Dear Stuart ,
I am using iis,
for an unicode , because of two bytes ;
you should use two characters in url.
its my example in turkish character set .
my url is
Ok so what happens if you try and access the document directly with :
Without _xql it does not work. But other shemas don’t work either
Ok so this brings us back to the original question raised by Alexander, in that it is not possible to directly access an XML document when the doctype contains Unicode characters. This is not a problem with Tamino: its just the way the HTTP protocol is designed to work. I think the workaround if you know what the ino:id is to use _xql= and _encoding as you’ve suggested but it would need processing to remove the Tamino specific tags.
This one is url restriction.
My question is ;
in forum there are a lot of pepople trying to access tamino direct from url.
These are not xsl/xslt style they are trying to use url like interractive interface.
Why they don’t try to develope JSP based applications. Are they just testing the query environment or i missed something
… back to the original question …
> it is not possible to directly access an
> XML document when the doctype contains
> Unicode characters.
Not true for Tamino v3.
The Tamino server supports IRIs (URLs in URL-
This works o.k., if the used webserver is
Apache. Unfortunately it does not work yet
thru IIS. This will be fixed as soon as possible
(see SAGSIS P225005).
> This is not a problem with Tamino: its just
> the way the HTTP protocol is designed to work.
More precisely: the way URLs work. Fortunately
this is (slowly) getting fixed, see
By the way: IE 4 and above already supports IRIs.
All the best,
Thank you Paul, it actually sounds promising.
It is not just a whim, Iwama, to access documents directly by plain addressing. I must apologize that I didn’t explain the ploblem entirely. Almost all Tamino utilities use direct addressing to retrieve, change and delete particular documents. So X-Plorer, Webdav, Mass Loading, Migrate untilities and also some part of Java API, X-Application (your JSP) do not support Russian Schemas.
I would like to store CommerceML documents in Tamino. And it works fine. But Tamino Infrastructure makes it impossible to process those documents later. I was already going to replace CommerceML with Latin equivalent and transform a new documents before storing and restore it back after retrieving. Funny solution when using Native XML Database, isn’t it?
By the way the first question that is asked about a new product here is not if it’s fast or reliable, but if it supports Russian, because we have got too many shadows under the eyes with internationalization.
I’m glad the problem is close to be solved. I think a temporary walk around could be migration from IIS to Apache.
Thanks all for useful information!