Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ralph.goers@dslextreme.com
 designates 209.85.214.175 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: [PROPOSAL] Apache Parser
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: 
 <CAECjgKA3spqLtyLCeHrwD+2DUyQLecdusy+viWiueBu292iwtA@mail.gmail.com>
Date: Wed, 30 May 2012 23:37:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBA0228A-2677-4DA7-9449-F9EFF2A6CA0A@dslextreme.com>
References: 
 <CAECjgKA3spqLtyLCeHrwD+2DUyQLecdusy+viWiueBu292iwtA@mail.gmail.com>
To: general@incubator.apache.org

My initial reaction is that there may be some confusion between this =
project and Commons Configuration, at least from a naming standpoint.  =
However, I don't believe Commons Configuration currently supports this =
format of configuration.

Ralph

On May 30, 2012, at 11:18 PM, Seungyoung Kim wrote:

> Apache Parser
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> General Purpose Apache-style Configuration File Parser
>=20
> * Definition
>=20
>  - Apache-style Configuration:
>      A configuration file syntax and format originally introduced and =
used
>      in Apache HTTPd.
>=20
> * Abstract
>=20
>  Apache-style configuration syntax provides powerful, versatile and =
flexible
> representation of data which can be adopted by many other =
applications.
>=20
> * Proposal
>=20
>  We're proposing a developer library of General Purpose Configuration =
Parser
> based on and expanding Apache-style syntax.
>=20
> * Background
>=20
>  One of common file format is INI-style configuration which provides =
key-value
> pairs and 1-depth section. This format is simple but does not provide =
much
> flexibility.
>=20
>  XML and JSON format is another one which are used wided, but little =
bit
> too complecated and heavy from application's stand point of view.
>=20
>  Apache-style syntax can cover both simple and complex layerd =
configuration.
> The syntax is very versatile to represent almost data format and the =
callback
> mechanism adds flexibility.
>=20
>  Many cases, software engineers pay much of their time to define their
> configuration syntax. Apache-style configuration can be a good =
suggestion.
>=20
> * Rationale
>=20
>  Apache configuration has originally introduced by Apache HTTPd. When =
this
> project is provided as a one of Apache projects, we believe this =
project can
> grow up with strong community and use base.
>=20
>  It also helps future apache projects adopt this syntax for their new =
projects.
>=20
> * Initial Goals
>=20
>  Initial goal is providing core library logic in C implementation.
> Other language bindings will be provided after that.
>=20
>  Initially, configuration parser will provide two way access of parsed
> entries. One is callback model which is the model Apache HTTPd is =
using.
> The other way is key-value model, primary for simple use and for other
> language bindings.
>=20
> * Current Status
>=20
>  At this point, initial base codes has written.
>=20
> * Community
>=20
>  This project needs engineers for other language bindings. This is one =
of
> reasons we want this project to be a Apache project.
>=20
> * Inexperience with Open Source
>=20
>  The core developer, Seungyoung Kim, has been driven and involved in
> several open-source projects such as qDecoder, qLibc, qHttpd and =
RingFS.
>=20
> * Required Resources
>=20
>  - Mailing lists:
>      apacheparser-dev
>      apacheparser-commits
>=20
>  - Subversion Directory:
>      https://svn.apache.org/repos/asf/incubator/apacheparser
>=20
>  - Issue Tracking:
>      Bugzilla
>=20
>  - Other Resources:
>      WIKI page
>=20
> * Initial Committers
>=20
>  Seungyoung Kim (wolkykim at gmail dot com)
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org