If you store an XML document with document element name CodesDocument in tamino without a schema then it goes into a collection called ino:etc in doctype CodesDocument which is created dynamically if it doesn’t exist already.
To find it you have to address the collection
http://yourhost/tamino/yourdb/ino:etc
with the query “CodesDocument” - then you should see it. You can do this with the interactive interface or just with IE5 like this
http://yourhost/tamino/yourdb/ino:etc?_xql=CodesDocument
A Tamino TSD2 schema specifies a collection name and a doctype, in this case “CodesDocument”.
My advice if you want to work with XML documents and don’t want to declare a schema for them, and there are a relatively small number of document types - declare a MINIMAL schema for each one using the same collection name. A minimal schema
declares the documentElement tag and the document can have any attributes or elements.
The easiest way to do this at the moment is to use the Tamino Dashboard that you can find to download in the JavaScript Discussion group.
You first create a new collection then add a minimal doctype.
Or create a document like this - which defines a collection “mycollection” and a doctype “CodesDocument” specifing any content and text indexes the entire document.
and use the TII to define the doctype.
<ino:collection xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” ino:name=“mycollection” ino:key=“id0000007383”>
- <ino:doctype ino:name=“CodesDocument” ino:key=“ID_CodesDocument” ino:options=“READ INSERT UPDATE DELETE” ino:structure-index=“CONDENSED”>
<ino:node ino:name=“CodesDocument” ino:key=“id0000007384” ino:obj-type=“ANY” ino:parent=“ID_CodesDocument” ino:search-type=“text” ino:map-type=“InfoField” ino:data-type=“WCHAR” />
</ino:doctype>
</ino:collection>
There is probably a way to do a minimal schema with the Tamino Schema Editor but I am not very familiar with it.
#Tamino#API-Management#webMethods