OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [search-ws] xQuery/XCQL


We’ve got plenty of them just around here, both applications and stylesheets.

 

Nothing we’ve done so far would break general XML parsing tools.  Removing an element and replacing it with another falls into the category of “breaking”.

 

Ralph

 

From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
Sent: Thursday, May 28, 2009 9:43 AM
To: search-ws@lists.oasis-open.org
Subject: Re: [search-ws] xQuery/XCQL

 

How many implementations of the echoed request do you think there are?   And we're talking about version 2.0, which already has quite a few application-breakers.

 

--Ray

 

----- Original Message -----

From: LeVan,Ralph

Sent: Thursday, May 28, 2009 9:39 AM

Subject: RE: [search-ws] xQuery/XCQL

 

Other than breaking all the applications that are expecting to find that element?

 

Let’s not do that.

 

Ralph

 

From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
Sent: Wednesday, May 27, 2009 5:51 PM
To: search-ws@lists.oasis-open.org
Subject: [search-ws] xQuery/XCQL

 

Would anyone  object to/see a problem with   changing the name of the <xQuery> element  of >echoedSearchRetrieveRequest> ......  to <xcql>.  

 

xQuery is confusing because of its similarity to W3C  XQuery.

 

 

--Ray



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]