Motivation:

CQL is limitied to its specification; we need a text format for filter and expression

Contact:

Jody Garnett Mauricio Pazos

Tracker:

http://jira.codehaus.org/browse/GEOT-1666

Tagline:

We need a text format for filter and expression

This page represents the current plan; for discussion please check the tracker link above.

Contents:

{TOC}

Description

The CQL format has a couple of limitations we need to break free of:

This proposal will create a new query language (called TXT) that looks like CQL but offers support for the above two ideas. We would call it WKT but since we are making up is is not yet known.

Status

Voting in progress:

Tasks

This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success

 

no progress

(tick)

done

(error)

impeded

(warning)

lack mandate/funds/time

(question)

volunteer needed

status

description

Release

(tick)

Define the BNF for TXT based on the CQL origional (see TXT Language Analysis)

2.6.0

(tick)

Code refactoring in CQLCopiler class to separate the generated parser from filter builder logic

2.6.0

(tick)

Create a TXT facade class that is method compatible with CQL

2.6.0

(tick)

Develop ID predicate

2.6.0

(tick)

Develop Comparison predicate

2.6.0

(tick)

Develop Between predicate

2.6.0

(tick)

Develop Null predicate

2.6.0

(tick)

Develop IN predicate

2.6.0

(tick)

Develop LIKE Text Pattern predicate

2.6.0

(tick)

Develop Spatial Predicate Functions

2.6.0

(tick)

Update the user guide to present TXT as a non standard option.

2.6.0

(tick)

Replace TXT by ECQL (src and docs).

2.6.0

 

Develop Spatial Relation Predicates

2.6.1

Debate

We are looking for a better name for the new language

Now: TXT

Options:

Name

(plus)

(minus)

TXT

the user can easily see the context

TXT is a file format with a big history

ECQL

All OGC CQL statements are valid in the new language; It is clear for the users that they only need to learn the new language features; maintains the reference to CQL the original language

could be prone to error: only a letter ("E") of difference to distinguish the context

CQL+

idem ECQL

need to be url-escaped in a GET request

TXTQL

the user can easily see the context

hard to pronounce

Conclusion: it will be ECQL (thanks everybody)

API Changes

Facade Class

class ECQL {
    Expression toExpression( String );
    Expression toExpression( String, FilterFactory );
    Filter toFilter( String );
    Filter toFilter( String, FilterFactory );
    List<Filter> toFilterList(String);
    List<Filter> toFilterList(String,FilterFactory);
}

Documentation Changes

list the pages affected by this proposal

Resources

Children: