Information Filled Under ‘Utility’ Category

XQuery and immortality WAS ACID transactions WAS Re: from Where 2.0

> Michael R is saying, I think, that > transaction facilities (and scripting) should only be added to the > standards > once they have been proven in products. Michael (K), thanks for the translation ! :-) Michael (R), I am sorry, despite the perfectly understandable English, I don’t understand the logic. I read, and reread the sentence above, and despite the rewriting, the content still doesn’t makes sense to me

Continue reading here:
XQuery and immortality WAS ACID transactions WAS Re:
from Where 2.0


Re: from Where 2.0

> > Any success stories in this community with storing and processing > > geolocation data ? > > eXist has a support for spatial data : > http://exist-db.org/devguide_indexes.html#N10E2D Perhaps an EXPath library similar in concept to eXist’s geospatial XQuery module would be a nice idea. We already provide some 44 generic geospatial specific functions.

See original here:
Re: from Where 2.0


Fwd: [ERR] from Where 2.0

Could the administrator of the mailing list please delete this address ? thanks ! Dana Begin forwarded message: > From: http://x-query.com/mailman/listinfo/talk > Date: March 30, 2010 7:15:36 PM PDT > To: http://x-query.com/mailman/listinfo/talk > Subject: [ERR] from Where 2.0 > > Transmit Report: > > To: http://x-query.com/mailman/listinfo/talk, 2010/03/31 11:15:33, 452, This mailbox is > temporarily disabled.

Continued here:
Fwd: [ERR] from Where 2.0


RE: XHTML with embedded XQuery: how to deal with the DOCTYPE declaration? How to deal with the default XHTML namespaces?

> > When using MarkLogic’s built-in HTTP server, I typically do > the following: > > xquery version “1.0-ml”; > > let $r := xdmp:set-response-content-type(“text/html; > charset= utf-8 “) return ( ‘ “http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”> ‘, > > > ) I’m surprised that should work; I would have expected the “

Excerpt from:
RE: XHTML with embedded XQuery: how to deal with
the DOCTYPE declaration? How to deal with the default XHTML
namespaces?


RE: XHTML with embedded XQuery: how to deal with the DOCTYPE declaration? How to deal with the default XHTML namespaces?

As with Kelly’s MarkLogic example, you would set the doctype in eXist using the following in your XQuery ‘s prolog: declare option exist:serialize “method=xhtml media -type=text/html omit-xml-declaration=no indent=yes doctype-public=-// W3C // DTD  XHTML 1.0 Transitional//EN doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”; This is documented on the XQuery wikibook at: http://en.wikibooks.org/ wiki /XQuery/eXist_Crib_sheet#output_XHTML_document Feel free to add other processors to the XQuery wikibook. Joe On Sat, Mar 27, 2010 at 6:19 PM, Kelly Stirman wrote: > When using MarkLogic’s built-in HTTP server, I typically do the following: > > xquery version “1.0-ml”; > > let $r := xdmp:set-response-content-type(“text/html; charset= utf-8 “) > return ( > ‘ ‘, > > > ) > > You can treat the doctype declaration as a string and return a sequence to the browser, including the doctype and the xhtml node. This seems like a valid approach for any XQuery processor, though it does seem like “ugly” XQuery.

Follow this link:
RE: XHTML with embedded XQuery: how to deal with
the DOCTYPE declaration? How to deal with the default XHTML namespaces?


XHTML with embedded XQuery: how to deal with the DOCTYPE declaration? How to deal with the default XHTML namespaces?

> > I am creating an XHTML document and embedding XQuery in it: > > QUESTION #1 > > When I execute the XHTML document (containing XQuery) I get > an error message regarding the DOCTYPE declaration: XQuery syntax is a bit like XML, but it isn’t real XML, don’t imagine that anything that’s OK in XML is OK in XQuery.

Read more:
XHTML with embedded XQuery: how to deal with the
DOCTYPE declaration? How to deal with the default XHTML namespaces?


XHTML with embedded XQuery: how to deal with the DOCTYPE declaration? How to deal with the default XHTML namespaces?

Hi Folks, I am creating an XHTML document and embedding XQuery in it: ——————————————————— … Our Solar System Planets { for $i in //planet return …

See the original post here:
XHTML with embedded XQuery: how to deal with the
DOCTYPE declaration? How to deal with the default XHTML namespaces?


Xquery, Saxon and special caracteres

> > How prepare the xquery to accept this characters? > > Escape the ampersand as you would with XML : I guess if this is actually user input, a better way is to use external variables: declare variable $searchstring as xs:string external; prod/DET[nD=$searchstring]/ad/number … and then pass in the value through the API or command line.

See the original post here:
Xquery, Saxon and special caracteres


[ANN] Sausalito 1.0 – XQuery in the Cloud

Ken, sorry for the late answer. You can find more information about Sausalito’s storage and the way transactions are implemented in our Sigmod 2008 paper “Building a Database on S3″. Best regards Matthias On 13.03.2010, at 22:07, Ken North wrote: > > > We are very excited to announce the first (non-beta) release of Sausalito 1.0.

See the original post here:
[ANN] Sausalito 1.0 – XQuery in the Cloud


Internet Explorer 9 Dev Preview Available

Microsoft has just released a preview release of IE 9; it is all for public to download and take a test run. It's a preview release in a “truest” sense because the preview version has lots of limitations: no toolbar, no address bar, no navigate…( read more )

Read more:
Internet Explorer 9 Dev Preview Available


Page 7 of 13« First...5678910...Last »


The news,articles,images etc. on XML Developer India  are selected automatically through a software process, please follow each article's attributed link to see the original content. This news site is powered by Wordpress. Incase of any objection or question please Contact Us...

Our Sevices

News