Well, cql is defined in "OGC Cataloge Service Specification v1.1.1 and v 2.0.0 " (OGC 02-087r3 y OGC 04-021r3)
There are a "mandatory query language" what can be extended (optional languages). In version 1.1.1 (OGC 02-087r3) present three types of query language: " .... - A common, mandatory query language using SQL style syntax, Z39.50 Type 1 operation style, and spatial operations derived from the simple features model in the OGC Simple Features Implementation Specification. - Any dialect of SQL conformant with the OGC Simple Features Implementation Specification. - Z.39.50 Type 1 query. ..." other reference in v1.1.1 section 7.2.7.3.6 CG_QueryLanguage is "... The list of query languages follows: OGC_Common, Z3950_TypeOne, SQL3_SimpleFeature, SQL2_SimpleFeature ..." We implement the first "mandatory query language", perhaps we need think about an interface what allows create instance of "dialects" different (we could use that keywords in the factory method). I don't know if is important this issue now, thinking that we only have one implementation. I only present the problem for your knowledge. Cheers Mauricio www.axios.es On Tuesday 20 March 2007 17:25, Jody Garnett wrote: > I did not know it was version 2.0. > > By using "SPECIFICATION" we would get cql2_0 (I think the goal was to > get gml2, gml3, filter1_0 into the package name where people could see it) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
