Difference between revisions of "WTP/XQuery/Proposal"

From Eclipsepedia

< WTP
Jump to: navigation, search
(Extension Points)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= THIS IS A DRAFT PROPOSAL AND NOT AN OFFICAL WTP PROPOSAL YET.=
 
 
 
The XQuery Development Toolkit (XQDT) is a proposed project under the Web Tools Project.
 
The XQuery Development Toolkit (XQDT) is a proposed project under the Web Tools Project.
  
Line 40: Line 38:
 
* Validation
 
* Validation
 
** Validation of XQuery code.
 
** Validation of XQuery code.
** Validation for XQuery Engine specific functionality.  XQzilla, Exist, etc.
+
** Validation for XQuery Engine specific functionality.  [http://xqilla.sourceforge.net/HomePage XQilla], [http://exist.sourceforge.net/ exist-db], and [http://www.sqlsummit.com/XQueryProv.htm others].
 
** Project Level validation
 
** Project Level validation
 
** Error Level control for specific errors.
 
** Error Level control for specific errors.
Line 49: Line 47:
 
Possible future features
 
Possible future features
  
* XQuery Database Explorer - possible integratation into DTP for exploring a XML database
+
* XQuery Database Explorer - possible integration into DTP for exploring a XML database
 +
** This could leverage the [http://xmldb-org.sourceforge.net/index.html XML:DB API] to provide general support for XML:DB's that support the api.
 
* Debugging - allows step through debugging support of XQuery scripts and possible transition between XSLT, Java, and other languages and XQuery code.
 
* Debugging - allows step through debugging support of XQuery scripts and possible transition between XSLT, Java, and other languages and XQuery code.
  
Line 88: Line 87:
 
= Mentors =
 
= Mentors =
  
Need WTP Mentors.
+
* Nitin Dahyabhai (WTP Source Editing)
 +
* Chris Aniszczyk (Code 9)
  
 
== Committers ==
 
== Committers ==
Line 106: Line 106:
  
 
* [http://www.starstandard.org/ Standards for Technology in Automotive Retail]
 
* [http://www.starstandard.org/ Standards for Technology in Automotive Retail]
 +
* Benjamin Cabé (Anyware Technologies): XML Database Explorer
  
 
== User community ==
 
== User community ==
Line 113: Line 114:
 
== Tentative Development plan ==
 
== Tentative Development plan ==
  
 +
The tentative plan is the be incubating by the end of 2008.  Initial steps will be:
  
 +
* Submit code through IP review.
 +
* Start content assistance.
 +
* Finish syntax coloring
 +
* Start work on Validation support.
 +
 +
The project plans to try and follow the current WTP schedule for milestones and release candidates.  The project may deviate from this schedule of problems or issues arise.
  
 
= Relation to other Eclipse projects and other open source projects =
 
= Relation to other Eclipse projects and other open source projects =
 +
 +
* [http://www.w3.org/TR/xquery/ W3C XQuery 1.0]
 +
* [http://www.w3.org/TR/2008/CR-xquery-update-10-20080801/ W3C XQuery Update 1.0]
 +
* [http://jcp.org/en/jsr/detail?id=225 XQJ] - a java API standard for talking to XML Databases using XQuery.
 +
* [http://www.oracle.com/database/berkeley-db/xml/index.html Berkeley XML DB]
 +
* [http://exist.sourceforge.net exist-db]
 +
* [http://code.google.com/p/xqpretty/ XQPretty] - provides XPath 2.0 and XQuery parsing ability.
 +
* [http://antlr.org/ ANTLR V3] - used by XQPretty.
 +
* [http://www.eclipse.org/datatools/ Data Tools Platform]
 +
* [http://www.eclipse.org/webtools/ Web Tools Platform]
 +
* [http://xqdoc.org/ XQDoc]
 +
* [http://xmldb-org.sourceforge.net/index.html XML:DB API] - a general XML Database API framework.
 +
* [http://modis.ispras.ru/sedna/#about Sedena]
 +
 +
[[Category:XQuery Development Tools]]
 +
[[Category:XML Tools]]

Latest revision as of 12:40, 26 August 2009

The XQuery Development Toolkit (XQDT) is a proposed project under the Web Tools Project.

According to the Eclipse Development Process, this proposal is intended to declare the intent and scope of the XQuery Development Toolkit project as well as to gather input from the Eclipse community. You are invited to comment on and/or join the project.

Contents

[edit] Background

XQuery was designed by XML Query working group of the W3C in order to present a convenient way to query largely (but not limited to) XML data collections and became a W3C recommendation on January 23, 2007. Currently many commercial XML Databases support XQuery as a platform to query its data. Also with the upcoming new XQuery version which is 1.1, it is believed XQuery will be the main data query technique for XML documents as well as databases. As such, it is quite useful to have an editor for XQuery with rich functionality such as syntax validation and content assistance under WTP umbrella.

[edit] Introduction

XQuery Development Toolkit(XQDT) is mainly an editor built on Structured Source Editor(SSE) for easy XQuery handling. It will initially have basic text editor functions such as syntax colouring and content assistance to create and modify XQuery documents easily. Later it could be added more rich features such as content formatting, advance preferences, error tips and support to other commercial XML databases through extension points.

[edit] Project Description

XQuery Development Toolkit project will be based on the project done by Buddhika Laknath for Summer of Code 2008 named "New Eclipse Plugin for XQuery" mentored by David Carver who is a committer for XSL Tools. The initial idea of the project is to fill gaps in Eclipse in regards to new XML formats and persuade more web and XML users to choose Eclipse as their native platform.

[edit] Goal

Basic goal of the project is to provide a rich text editor for XQuery developments with Eclipse. Other than that, it's our hope that this will be an incentive to draw more attention from XML users into accepting Eclipse as their main development platform.

[edit] Scope

Currently Scope is limited to providing basic text editing features for XQuery language based on Structured Source Editing components. But at the end of first phase, providing that users requesting more features into the editor, it will be moving forward to bring more rich text editing experience to users.

As always, scope can change based on community and adopter feedback as well as changes in XQuery standards.

[edit] Features

The following features are planned or currently implemented:

  • Content Assistance (planned)
    • XPath 2.0
    • Xquery Templates
    • XQuery User Defined Functions
    • Namespaces
  • Syntax Coloring (partially implemented) - the editor is currently aware of XQuery/Xpath 2.0 specific syntax and will color keywords accordingly. It still needs to be made configurable.
    • XML syntax coloring is inherited from the XML editor
  • Validation
    • Validation of XQuery code.
    • Validation for XQuery Engine specific functionality. XQilla, exist-db, and others.
    • Project Level validation
    • Error Level control for specific errors.
  • Template support
  • New File Wizard


Possible future features

  • XQuery Database Explorer - possible integration into DTP for exploring a XML database
    • This could leverage the XML:DB API to provide general support for XML:DB's that support the api.
  • Debugging - allows step through debugging support of XQuery scripts and possible transition between XSLT, Java, and other languages and XQuery code.

[edit] Perspectives and Views

The initial views will leverage many of the views provided by the XSL Tools project. These are:

Perspectives:

  • XML Perspective - general editing perspective for XML related functionality.
  • Database Perspective - for XML Database browsing.

It will leverage the following existing views.

Views:

  • Project Explorer
  • Outline View
  • XPath View
  • Properties View
  • Problems View
  • Templates View

Possible new views:

  • XQDoc - XQDoc does for XQuery what JavaDoc does for java. It provides a platform neutral way of documenting XQuery.

[edit] Extension Points

Possible extension points include:

  • XQuery Engines - Allows for the selection and installation of various XQuery Engines used during Launch Configurations.
  • XQuery Engine specific Validation. Leveraging the existing WTP Validation framework, allow for projects to have specific XQuery Engines used for validation.
  • Debugging Support - If an engine supports Debugging allow it to contribute functionality.

[edit] Project Organization

We propose this project should be undertaken as an incubator project with the Web Tools project.

[edit] Mentors

  • Nitin Dahyabhai (WTP Source Editing)
  • Chris Aniszczyk (Code 9)

[edit] Committers

  • Budhikka Laknath - Contribution/Committer - Budhikka wrote the initial code during the Google Summer of Code Project.
  • David Carver (XSL Tooling Committer)

[edit] Initial Code Contribution

The initial code contribution comes from the Summer of Code 2008 project which is hosted at sourceforge, XQuery Plugin

[edit] Licensing and Intellectual property

All code is being relicensed under the terms of the Eclipse Public License. All committers have agreed to these relicensing terms.

[edit] Interested Parties

[edit] User community

XQuery already has a large user community that covers both the data side of xml as well as the document centric side of the XML. It is becoming the defacto standard for querying XML repositories and data bases, and is a good complement to other XML technologies like XSL. As more traditional database add support for XML databases having a good base set of XQuery tools to use and extend will become increasing important.


[edit] Tentative Development plan

The tentative plan is the be incubating by the end of 2008. Initial steps will be:

  • Submit code through IP review.
  • Start content assistance.
  • Finish syntax coloring
  • Start work on Validation support.

The project plans to try and follow the current WTP schedule for milestones and release candidates. The project may deviate from this schedule of problems or issues arise.

[edit] Relation to other Eclipse projects and other open source projects