eXist-db

eXist has contributed and attended XML Prague in the past ... so I
have forwarded here.

---------------

XML Prague 2009 Call for Participation (CFP)
--------------------------------------------

XML Prague 2009 (http://www.xmlprague.cz) is now welcoming submissions for
presentations on the following topics:

   * XML Authoring
   * Data Modeling/Definition and Schema Languages
   * XML Vocabularies
   * Generating and Transforming XML
   * Markup Failures

All proposals will be submitted for review by a peer review panel made
up of the XML Prague Organizing Committee. Submissions will be chosen
based on interest, applicability, technical merit, and technical
correctness.

Accepted Papers will be included inside the published conference proceedings.

Authors should strive to contain original material and belong in the
topics previously listed. Submissions which can be construed as
product or service descriptions (adverts) will probably be deemed
inappropriate. Other approaches such as using case studies are welcome
but must be clearly related to conference topics.

Selected presenters must submit an full paper (on time) and give their
presentation and answer questions in English, as well as follow the
XML Prague 2009 conference guidelines.
Important Dates:

   * January 9 - End of CFP (extended abstract or full paper)
   * January 23 - Notification of acceptance/rejection of paper to authors
   * February 8 - Final paper

How to Submit:

All submissions must be done using the conference management system
available at the https://cmt.research.microsoft.com/XML2009/

If you have never used this system before for other conferences, you
will have to sign-up first and create new account for yourself.

After logging onto conference management system you will be able to
submit your paper and edit this submission before deadline. You can
also review the status of your paper as well as review comments from
review process.

You may submit an abstract or a full paper. We recommend to provide as
much information as possible to give the reviewers the best chance to
judge your submission.
Submission Guidelines:

All submissions must be in English and paper should not exceed 15
pages in length. Papers for review can be submitted in any common
format. However, we remind people that if your paper is accepted that
we will be asking for the final version to be submitted in DocBook XML
format.

If you have any question regarding submission process please contact
Jirka Kosek at jirka.kosek@....

---

cheers, Jim Fuller

-------------------------
XML Prague 2009
http://www.xmlprague.cz

Sometime in the past couple of weeks or so, did someone change anything that might affect the DOM and internal namespace 
handling with eXist?

We use Orbeon XForms....no changes to Orbeon in months!

But all of a sudden, when Orbeon tries to access a file from eXist using REST we get this error:

Fatal error: Attribute "xmlns" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "user".

Just wondering if there was a bug introduced in some recent changes that might have caused something like this?

Thx!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

I finally updated the old Apache XMLRPC library used by eXist from 
version 1.2 to 3.1.1. The 1.2 version did not support the whole unicode 
character range - that's why we shipped a patched version with eXist. 
This is no longer necessary, but just to be sure, please watch out for 
character encoding problems.

The main reason for the upgrade was a strange concurrency issue some 
users experienced with the XMLRPC interface. I hope the new 
implementation fixes this.

Concerning backwards compatibility, I tried not to change eXist's XMLRPC 
API. Existing client code should basically run as before. If you find 
any problems, please report them.

Wolfgang

Bug in REST interface. (Testing in XMLRPC fails not )

It's not possible to NAME a collection or file with following chars: 
 Parenthesis "()" and Comma ","

this IS allowed: 
http://localhost:8080/exist/rest/db/the testcoll æøå

NOT allowed:
http://localhost:8080/exist/rest/db/the testcoll (æøå
http://localhost:8080/exist/rest/db/the (testcoll) æøå
http://localhost:8080/exist/rest/db/the testcoll, æøå


(I have found old threads that mention this issue .. way back )

Q: Is there a bug-url , should there be one ?


-- 
View this message in context: http://www.nabble.com/REST-%3A-collection-file-names-cannot-include-%22%2C%28%29%22-%28eXist-1.2.4%29-tp20732654p20732654.html
Sent from the exist-open mailing list archive at Nabble.com.

Bugs item #2352324, was opened at 2008-11-26 16:33
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=117691&aid=2352324&group_id=17691

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hugh A. Cayless (hcayless)
Assigned to: Nobody/Anonymous (nobody)
Summary: attribute supplied in wrong namespace

Initial Comment:
In eXist 1.2.4, the attached, schema-valid document will be turned into an invalid document when loaded.  It contains an element for which the schema specifies an attribute in a different namespace with a fixed value.  Because the value is fixed, the instance document is valid even though the attribute isn't actually contained therein.  eXist adds the attribute, but does it in the element's namespace rather than the correct one.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=117691&aid=2352324&group_id=17691

Hi,

i have some problems querying our database.
To keep my querys simple i tried to use the text-search function 
"match-all" and "match-any"
but i'm getting wrong results with those functions :-(

My first statement was this one:
-------------------------------
for $doc in //text[@type='charter']
where ( .//supplier &= 'P*' )
and (.//idno != '')
order by xs:float($doc//idno)
return $doc
-------------------------------
Getting me a set of 80 results back - correct!

My second try was this one:
-------------------------------
xquery version "1.0";
import module namespace text="http://exist-db.org/xquery/text";
for $doc in //text[@type='charter'][.//idno != '']
[text:match-any((.//supplier) , ('P*'))]
order by xs:float($doc//idno)
return $doc
-------------------------------
I suppose that one should bring the same results, but i'm getting nearly 
all data back all 1956 datasets as result :-(

Does this function only work with reg-expr???
... text:match-any((.//supplier) , ('^P[a-z]*')) ...
This one gives me back the same 80 results as the first one, but it 
makes automatic querybuilding out of a form more difficult and tricky if 
i can't use just the text-field input, but have to reform the input to a 
reg-expr :-(


And of course, i wanted to use those functions, because i need a simple 
way to query different paths for the same term at ones, i.e.
text:match-any( ((.//path1), (.//path2), (.//path3)) , ('searchterm'))
And i need the possibility to use "?" and "*" in my Searchterms to 
substitute "1" or "0-n" letters.


Any advise or help is very appreciated.
Thanks a lot so far,
regards, Marcus

Hi list,

Recently I stumbled upon a surprising optimization which I wanted to share.

The application I am working on processes several types of XML documents.
These document types share a similar structure, but have different root
element names. They look a bit like this:

<XXXX> <!-- Type specific root element name -->
  <Header> <!-- Generic header -->
    <DocumentId>docid</DocumentId>
    ...
  </Header>
  <Body>     <!-- Type specific body -->
    ...
  </Body>
</XXXX>

Because not all root element names are known beforehand, sometimes the
following construct is used:

for $doc in collection("/db/data")
return $doc/element()/Header/DocumentId/string() (: Or something more
interesting than string() :)

This is pretty slow, even with an index on DocumentId and query rewriting
enabled, e.g., with 5000 documents it takes eXist (1.2.5dev-r8333) about 20
seconds to return a result. In this case, the element() path element can be
replaced by element()[1], since document nodes have at most one child
element. This improves performance dramatically: query time drops to 1 s.

I hope this helps someone who is trying to optimize his XQueries. Although
it would be nice if eXist performed this optimization automatically.

With kind regards,
Pieter Deelen

Hi Wolfgang,


>>  We are using eXist-db 1.2.0-rev:7236-20080115. Do you recommend updating
>>  to a newer version, and if yes, which one?
>
> I'm not aware of any bugs affecting document order in 1.2 or earlier 
> releases. However, 1.2.4 does contain some important bug fixes. Within the 
> 1.2 series, updates should be without risk.

Finally, we managed to reproduce & track down the odd & severe 
behaviour/bug of eXist-db, which changes the order of elements in XML 
documents and breaks the document in other ways, too.

Bad news: The problem exists (at least) in eXist-db 1.2.0 
rev7236-20080115.
Good news: The problem does not exists anymore in eXist-db 1.2.4 
rev8072-20080802 or at least I am not able to reproduce it with my 
example code. Maybe it has been fixed on purpose?!?

Anyway, I have enclosed a test database (XML document) and a test XQuery. 
Put the XML document to the database (/db/testdb.xml) and change the 
owger&group access rights of the document to "guest" & "guest". Finally, 
execute the XQuery in XQuery Sandbox and see what happens to the "id" 
attribute of the <researchareas> element. Yes, it's has disappeared and 
the value of that "id" attribute has shifted between the first and second 
<researcharea> element.

If I will move the <researchareas> element before the <projects> element 
and do the update, then everything works fine.

I was not able to figure out what is the reason for this odd behaviour, 
but I would sure like to know. Like I said, eXist-db 1.2.4 works fine with 
my test case.

Kind regards


-Markku Laine

Dear list-members,

Is it possible to purge an index of obsolete entries after an xml collection
has been substantially pruned?

I have a 10gb n-gram index file, which was created by indexing 4,000 xml
files.  I have since removed 2,000 files from the collection, and would like
to avoid re-indexing the remaining half.  Is there a way I can clear the old
index data without deleting the entire index and starting again?

If anyone has any suggestions, I would be very grateful to hear them.

Hi everybody,
	I was looking for an XQuery function which is able to save previously stored
binary resource to a local file. AFAIK it is possible to store from a file
(either binary or XML) to the database, using xmldb:store, and it is possible
serializing from an stored node to to a file using file:serialize, but I could
not find the right function for binary resources.

	Best Regards,
		José María

-- 
"There is no reason why anybody would want a computer in their home" -
	Ken Olson, founder of DEC 1977
"640K ought to be enough for anybody" - Bill Gates, 1981
"Nobody will ever outgrow a 20Mb hard drive." - ???

"Premature optimization is the root of all evil." - Donald Knuth

José María Fernández González
Tlfn: (+34) 91 732 80 00 / 91 224 69 00 (ext 3061)
e-mail: jmfernandez@...		Fax: (+34) 91 224 69 76
Unidad del Instituto Nacional de Bioinformática
Biología Estructural y Biocomputación	Structural Biology and Biocomputing
Centro Nacional de Investigaciones Oncológicas
C.P.: 28029				Zip Code: 28029
C/. Melchor Fernández Almagro, 3	Madrid (Spain)

**NOTA DE CONFIDENCIALIDAD** Este correo electrónico, y en su caso los ficheros adjuntos, pueden contener información protegida para el uso exclusivo de su destinatario. Se prohíbe la distribución, reproducción o cualquier otro tipo de transmisión por parte de otra persona que no sea el destinatario. Si usted recibe por error este correo, se ruega comunicarlo al remitente y borrar el mensaje recibido.
**CONFIDENTIALITY NOTICE** This email communication and any attachments may contain confidential and privileged information for the sole use of the designated recipient named above. Distribution, reproduction or any other use of this transmission by any party other than the intended recipient is prohibited. If you are not the intended recipient please contact the sender and delete all copies.

> This is Ramesh. I am implementing xforms and eXist xml database in my
> application. i have to implement transaction management in my application.
> while child node is successfully submitted. but parent node  inserting  is
> failure. I implemented these two actions in single transaction. how do i
> rollback the first action in xml eXist database.

I'm not sure I understand the question, but eXist only supports
transactions internally, i.e. transactions are not visible to users
and there's no explicit rollback mechanism.

You would need to implement this on the application layer.

Wolfgang

Hi Dan,

> I loved the pre-loaded Shakespeare demos.  They are a great way to 
> educate people on fulltext search.  They are not in the current on-line 
> demo Sandbox.

I'm sorry but we are still having difficulties to get the new demo 
server up and running. We had to shut down the old server due to 
problems at the hoster. I hope we'll get the new one running properly soon.

Wolfgang

Hi Joe

The main purpose of the Query Automation is to get an idea about the
performance of XQueries.

If you create a new XQuery it's always good to know about how it performs.
And sometimes it's good to know how long the XQueries take if the database
is under load. Those kinds of figures you can find out with the Query
Automation.

On the one hand you can define the quantity, which means how many times a
single query is executed. On the other hand you can define the concurrency,
which represents the number of connections and the number of threads the
plugin is working with.

The result that is displayed at the end of the automation doesn't contain
the single results. It contains a summary on compilation and execution times
of the single queries. So you'll probably know whether the XQuery is fast
enough or whether you need to optimize something.
The eqar-file is nothing but an XML-file. You can save it wherever you want
and compare the results after some optimization work was done.

Maybe the term 'automation' is a little bit misleading. But I hope things
are a bit more clear for you now?

Regards
Markus

Hey all,

can anyone tell me if it is possible to make xqueries ( that I used to  
store / search / edit files from a web-App ) lying in me eXist  
database accessable by the same users-groups stored in the web-app?

It uses REST to connect to eXist. Right now everything is readable and  
writeable to ``world''.

Is it possible to use XACML to make a resource lying in my database  
accessable to REST but only to it, so that they cannot be accessed  
from outside the app?

I enabled <xacml enable="yes"/> but don´t know if it´s possible what I  
want to do....