A good way to learn about the structure of a document without trying to return all of it would be to use successive XPath queries that give you the names of elements. E. G name(/*) This will tell you the name of the outermost element.
Then name(/*/*1) name(/*/*2) /*/text()1 count(/*/*) name(/*/@*1) Instead, you may have to start your XPath expression with document('...') hopefully you know the name of a document? Also this screenshot shows some potentially useful queries. I think.
A good way to learn about the structure of a document without trying to return all of it would be to use successive XPath queries that give you the names of elements. E.g.Name(/*) This will tell you the name of the outermost element. Then, name(/*/*1) name(/*/*2) /*/text()1 count(/*/*) name(/*/@*1) etc. Since you can use XQuery, you could do a loop that prints out, say, all the above data for the first three elements at the top three levels of the document.
Alternatively, / may return nothing, because in XPath this means "the root node of the document containing the context node"; and in XQuerying a database of XML documents, there may not yet be a context node (caveat: I'm not real fluent in XQuery, so check your references). Instead, you may have to start your XPath expression with document('...')/; hopefully you know the name of a document? Also, this screenshot shows some potentially useful queries.
I think.
LarsH recommended a useful exploration strategy. An alternative is to get the whole XML document, for example applying the XSLT identity transformation: This transformation produces as result an XML document that in most cases is identical to the source XML document (any XML document) on which it is applied. Another way of seeing the exact XML document is to use a debugger and set a breakpoint at a place in the code where the XML document has already been received.
Then use the debugger visualization capabilitis to get the "outerxml" or "innerxml" property of the XMLDocument object. Of course, nothing prevents the server of returning different XML documents on different requests.
Since you are using CQ, you can click the "explore" link (towards the upper left of the query pane). This will give you a list of documents in the database you have selected. You can then use the URI of one of the documents and do an fn:doc of it: fn:doc("/myuri.
Xml") That will return that one document. Then you can add XPath steps to navigate down it.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.