You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Klevenz, Stephan" <st...@sap.com> on 2013/06/17 17:35:59 UTC

[PROPOSAL] OData Proposal for Incubator

Dear ASF members,

We would like to propose the OData project to the Incubator.

The OData Proposal is available at: https://wiki.apache.org/incubator/ODataProposal

We welcome your feedback and suggestions.

Thanks!

Stephan Klevenz



= Apache OData =

=== Abstract ===

Apache OData is a generic Java language implementation of the OData 2.0 specification which will serve as a code base for the upcoming OASIS OData specification.

=== Proposal ===

The Open Data Protocol (OData) [1] is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.

The Apache OData is a library which enables developers to implement OData producers and OData consumers. Basic principles of the library are to provide an OData 2.0 specification compliant OData Library, enhancements shall be possible in a compatible manner, have a clear separation between Core and API, to provide an option to build extensions on top. This library should be base for implementing future releases of the specification.

=== Background ===

OData was originally developed by Microsoft and is released in a version 2.0 under an Open Specification Promise [2]. A lot of companies did show interests in this protocol, used it in products and gave feedback back to Microsoft. This joined effort resulted in a new release OData 3.0 in 2012, this version became the basis for the OASIS technical committee [3] which is currently working on a new version of the specification. This OASIS standard release is expected this year.

The initial Java code of this project was developed by a development team that had already experience with other OData 2.0 and 3.0 implementations at SAP AG. The current code base implements OData 2.0 and because of this version is widely used it is a good starting point to build an open source community for the OData standard.

The current code also comes up with an implementation of an OData sample service. On the one side this is an example for users which want to use the library to expose their own data and on the other side it illustrates how implemented features work.

Additionally, the code base includes an extension which is called JPA processor. With this extension it is easy to expose any JPA persistence model via OData protocol without a lot of coding.

=== Rationale ===

More software vendors moving to OData means more choice for customers who will be able to use different implementations. For the standard to succeed, however, ensuring interoperability is paramount: in order to manage an ever growing context and leverage the enormous portability and interoperability issues that a globally adopted standard brings, it is necessary to think about how to make the related ecosystem healthy and sustainable. Successful modern standards are driven by:

 * Clear documentation, built iteratively with continuous feedback from stakeholders
 * A clearly defined compatibility process, enforced by tools that allow to gauge how implementations can be compatible and interoperable
 * Accurate compliance criteria, documented in writing as well as in actual testing code that measure how tools and libraries are able to interoperate
 * A sample implementation to clear up potential doubts and ensure that the standard can actually be implemented in real life scenarios

The above mentioned pieces are able to make the development activity, towards an OData implementation, easier and more successful. Having an healthy ecosystem will ensure a smoother implementation process, more compliant products, and ultimately, a wider adoption of the standard.

The OData ecosystem has been successful in creating and documenting early versions of the standard, yet it might potentially lack two very important aspects, that is a exhaustive implementation of the complete protocol that can be used productively and to ensure interoperability. As much as such artifacts can be developed independently by any OData proponent, the value of having a neutral party as a steward of actual code is to be considered. The Apache Software Foundation has been playing this kind of role for many years, and can provide the perfect environment to foster contributions on the OData theme with a great amount of expertise.

=== Initial Goals ===

 * Implement OData 2.0, make it final and mature
 * Start implementation of OASIS OData draft specification
 * Provide input and feedback for the draft specification to the OASIS OData TC based on implementation
 * Implement OData add-ons (library extensions and toolset)

== Current Status ==

=== Meritocracy ===

Most of the initial committers are open source developers with different experience levels and many of them have already worked in other open source or Apache projects. We will follow standard Apache procedures in accepting new contributors to the project team.

=== Community ===

Managed by an OASIS Technical Committee, the OData standard definition should be based on the idea of a community driven effort.

Apache OData aims to be a community driven initiative in developing a Java OData implementation. Such an approach is allowing more transparency and direct feedback even within the definition and improvement of OData specifications.

We encourage everyone interested in OData to join the Apache OData effort.

=== Core Developers ===

The development team is international and they have all strong skills in OData protocol. Jens Huesken who is member of the OASIS OData TC is providing specification feedback since OData 2.0. Stephan Klevenz, also a OASIS OData TC member, was a committer of the Apache Chemistry project. He has experience with the Incubator and Apache and was also a speaker on ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara Boehm did implement core parts of the library. Chandan V A, Anirban Roy, Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA processor add on.

=== Alignment ===

The project builds with Apache Maven, the core runtime requires Apache CXF for REST binding (JAX-RS) and the sample scenario can be deployed into any compliant Servlet or J2EE container like Apache Tomcat. Furthermore we see OData protocol as an option to be supported by other Apache projects that have to expose data via a standardized protocol based interface.

== Known Risks ==

=== Orphaned products ===

Apache OData is a fresh new codebase that targets the still moving OData standardization effort. Thus the future of this project depends heavily on the success of the standard. We hope and expect that our implementation efforts will strengthen and support the OData standard.

=== Inexperience with Open Source ===

Some of the initial committers are experienced open source developers. But there are also committers which are new to open source.

=== Homogenous Developers ===

The initial committers are from SAP working in different teams. One team is from Germany and has implemented the core parts of the library and the other team is from India and has implemented the JPA processor add-on.

=== Reliance of Salaried Developers ===

All of the initial committers are paid by SAP to work on this or related projects.

=== Relationships with Other Apache Products ===

Apache OData will directly use at least the following projects:

 * Apache CXF - for REST bindings
 * Apache Commons - for encoding/decoding

Other Apache projects may be interested in using Apache OData to add OData support once the standard is final.

=== An Excessive Fascination with the Apache Brand ===

We value Apache as a neutral place where diverse communities can work together on implementing shared standards. We hope that this part of the Apache brand helps attract contributions from many potential OData standard consumers. However, the brand value is not the main reason why we prefer to have this project at Apache.

== Documentation ==

This project is still at an early stage, so there is not much documentation available. See the OASIS OData page and odata.org web site for information about the OData standardization effort.

== Initial Source ==

 * [[https://github.com/SAP/cloud-odata-java]]
 * [[https://www.ohloh.net/p/cloud-odata-java]]

== Source and Intellectual Property Submission Plan ==

The complete code is under Apache Software License 2.

== External Dependencies ==

All the external dependencies of the initial codebases comply with Apache licensing policies.

== Cryptography ==

Apache OData is not expected to implement or use cryptographic code.

== Required Resources ==

=== Mailing lists ===

 * odata-dev'at'incubator.apache.org
 * odata-commits'at'incubator.apache.org
 * odata-private'at'incubator.apache.org

=== Subversion Directory ===

writeable Git Repository (preferred)

    [[git://git.apache.org/odata.git]]

or SVN Directory

    [[https://svn.apache.org/repos/asf/incubator/odata]]

=== Issue Tracking ===

    JIRA OData (OData)

=== Other Resources ===

    none

== Initial Committers ==

|| '''Name'''       || '''Email'''                 ||
|| Stephan Klevenz  || sklevenz'at'apache.org      ||
|| Jens Huesken     || jens.huesken'at'sap.com     ||
|| Christian Amend  || christian.amend'at'sap.com  ||
|| Michael Bolz     || michael.bolz'at'sap.com     ||
|| Tamara Boehm     || tamara.boehm'at'sap.com     ||
|| Chandan V A      || chandan.v.a'at'sap.com      ||
|| Anirban Roy      || anirban.roy'at'sap.com      ||
|| Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
|| Jobin John       || jobin.john'at'sap.com       ||
|| Joerg Singler    || joerg.singler'at'sap.com    ||

== Affiliations ==

|| '''Name'''          || '''Affilitation''' ||
|| Stephan Klevenz     || SAP AG       ||
|| Jens Huesken        || SAP AG       ||
|| Christian Amend     || SAP AG       ||
|| Michael Bolz        || SAP AG       ||
|| Tamara Boehm        || SAP AG       ||
|| Chandan V A         || SAP AG       ||
|| Anirban Roy         || SAP AG       ||
|| Chitresh Chauhan    || SAP AG       ||
|| Jobin John          || SAP AG       ||
|| Joerg Singler       || SAP AG       ||

== Sponsors ==

Champion

 * Florian Mueller

Nominated Mentors

 * Florian Mueller
 * tbd.

Sponsoring Entiy

 * Incubator PMC

==== Links ====

 * [1] [[http://www.odata.org]]
 * [2] [[http://www.microsoft.com/openspecifications/en/us/programs/osp/default.aspx]]
 * [3] [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
 * [4] [[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi Dave,

We would be happy to get you as an Mentor to this project. Can you please
add yourself as a mentor to the proposal?

https://wiki.apache.org/incubator/ODataProposal


I do share your concerns about the homogenous initial committer list. Have
a look to my recent reply to Henry about the same issue. we are open to
everyone to join the Apache OData proposal.

Regards,
Stephan 



On 18.06.13 02:19, "Dave Fisher" <da...@comcast.net> wrote:

>
>On Jun 17, 2013, at 12:30 PM, Henry Saputra wrote:
>
>> I love having the (reference) implementation for OData specs, should
>>help
>> the adoption of the specifications.
>> 
>> The immediate red flag is the homogeneous participation for initial
>> committers. Any plan to add more diverse members as the initial goals?
>> Does the project have contributions from external developers or
>>community?
>
>To me the question is if developers from outside of SAP are attracted to
>OData and also if the SAP team can properly be open to and inclusive of
>new volunteers on their dev list.
>
>I think that there are a surprising and wide number of possible consumers
>and producers of content in this form.
>
>Services can be defined based purely on the data they provide and
>consume. Putting OData services in the context of Tomcat and CXF aligns
>perfectly with my $dayjob. I could become a user of this software.
>
>I would be willing to add my name as a Mentor.
>
>Regards,
>Dave
>
>
>
>> 
>> - Henry
>> 
>> 
>> On Mon, Jun 17, 2013 at 8:35 AM, Klevenz, Stephan
>> <st...@sap.com>wrote:
>> 
>>> Dear ASF members,
>>> 
>>> We would like to propose the OData project to the Incubator.
>>> 
>>> The OData Proposal is available at:
>>> https://wiki.apache.org/incubator/ODataProposal
>>> 
>>> We welcome your feedback and suggestions.
>>> 
>>> Thanks!
>>> 
>>> Stephan Klevenz
>>> 
>>> 
>>> 
>>> = Apache OData =
>>> 
>>> === Abstract ===
>>> 
>>> Apache OData is a generic Java language implementation of the OData 2.0
>>> specification which will serve as a code base for the upcoming OASIS
>>>OData
>>> specification.
>>> 
>>> === Proposal ===
>>> 
>>> The Open Data Protocol (OData) [1] is a Web protocol for querying and
>>> updating data that provides a way to unlock your data and free it from
>>> silos that exist in applications today. OData does this by applying and
>>> building upon Web technologies such as HTTP, Atom Publishing Protocol
>>> (AtomPub) and JSON to provide access to information from a variety of
>>> applications, services, and stores.
>>> 
>>> The Apache OData is a library which enables developers to implement
>>>OData
>>> producers and OData consumers. Basic principles of the library are to
>>> provide an OData 2.0 specification compliant OData Library,
>>>enhancements
>>> shall be possible in a compatible manner, have a clear separation
>>>between
>>> Core and API, to provide an option to build extensions on top. This
>>>library
>>> should be base for implementing future releases of the specification.
>>> 
>>> === Background ===
>>> 
>>> OData was originally developed by Microsoft and is released in a
>>>version
>>> 2.0 under an Open Specification Promise [2]. A lot of companies did
>>>show
>>> interests in this protocol, used it in products and gave feedback back
>>>to
>>> Microsoft. This joined effort resulted in a new release OData 3.0 in
>>>2012,
>>> this version became the basis for the OASIS technical committee [3]
>>>which
>>> is currently working on a new version of the specification. This OASIS
>>> standard release is expected this year.
>>> 
>>> The initial Java code of this project was developed by a development
>>>team
>>> that had already experience with other OData 2.0 and 3.0
>>>implementations at
>>> SAP AG. The current code base implements OData 2.0 and because of this
>>> version is widely used it is a good starting point to build an open
>>>source
>>> community for the OData standard.
>>> 
>>> The current code also comes up with an implementation of an OData
>>>sample
>>> service. On the one side this is an example for users which want to
>>>use the
>>> library to expose their own data and on the other side it illustrates
>>>how
>>> implemented features work.
>>> 
>>> Additionally, the code base includes an extension which is called JPA
>>> processor. With this extension it is easy to expose any JPA persistence
>>> model via OData protocol without a lot of coding.
>>> 
>>> === Rationale ===
>>> 
>>> More software vendors moving to OData means more choice for customers
>>>who
>>> will be able to use different implementations. For the standard to
>>>succeed,
>>> however, ensuring interoperability is paramount: in order to manage an
>>>ever
>>> growing context and leverage the enormous portability and
>>>interoperability
>>> issues that a globally adopted standard brings, it is necessary to
>>>think
>>> about how to make the related ecosystem healthy and sustainable.
>>>Successful
>>> modern standards are driven by:
>>> 
>>> * Clear documentation, built iteratively with continuous feedback from
>>> stakeholders
>>> * A clearly defined compatibility process, enforced by tools that allow
>>> to gauge how implementations can be compatible and interoperable
>>> * Accurate compliance criteria, documented in writing as well as in
>>> actual testing code that measure how tools and libraries are able to
>>> interoperate
>>> * A sample implementation to clear up potential doubts and ensure that
>>> the standard can actually be implemented in real life scenarios
>>> 
>>> The above mentioned pieces are able to make the development activity,
>>> towards an OData implementation, easier and more successful. Having an
>>> healthy ecosystem will ensure a smoother implementation process, more
>>> compliant products, and ultimately, a wider adoption of the standard.
>>> 
>>> The OData ecosystem has been successful in creating and documenting
>>>early
>>> versions of the standard, yet it might potentially lack two very
>>>important
>>> aspects, that is a exhaustive implementation of the complete protocol
>>>that
>>> can be used productively and to ensure interoperability. As much as
>>>such
>>> artifacts can be developed independently by any OData proponent, the
>>>value
>>> of having a neutral party as a steward of actual code is to be
>>>considered.
>>> The Apache Software Foundation has been playing this kind of role for
>>>many
>>> years, and can provide the perfect environment to foster contributions
>>>on
>>> the OData theme with a great amount of expertise.
>>> 
>>> === Initial Goals ===
>>> 
>>> * Implement OData 2.0, make it final and mature
>>> * Start implementation of OASIS OData draft specification
>>> * Provide input and feedback for the draft specification to the OASIS
>>> OData TC based on implementation
>>> * Implement OData add-ons (library extensions and toolset)
>>> 
>>> == Current Status ==
>>> 
>>> === Meritocracy ===
>>> 
>>> Most of the initial committers are open source developers with
>>>different
>>> experience levels and many of them have already worked in other open
>>>source
>>> or Apache projects. We will follow standard Apache procedures in
>>>accepting
>>> new contributors to the project team.
>>> 
>>> === Community ===
>>> 
>>> Managed by an OASIS Technical Committee, the OData standard definition
>>> should be based on the idea of a community driven effort.
>>> 
>>> Apache OData aims to be a community driven initiative in developing a
>>>Java
>>> OData implementation. Such an approach is allowing more transparency
>>>and
>>> direct feedback even within the definition and improvement of OData
>>> specifications.
>>> 
>>> We encourage everyone interested in OData to join the Apache OData
>>>effort.
>>> 
>>> === Core Developers ===
>>> 
>>> The development team is international and they have all strong skills
>>>in
>>> OData protocol. Jens Huesken who is member of the OASIS OData TC is
>>> providing specification feedback since OData 2.0. Stephan Klevenz,
>>>also a
>>> OASIS OData TC member, was a committer of the Apache Chemistry
>>>project. He
>>> has experience with the Incubator and Apache and was also a speaker on
>>> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>>Boehm
>>> did implement core parts of the library. Chandan V A, Anirban Roy,
>>>Chitresh
>>> Chauhan, Jobin John and Joerg Singler are working on the JPA processor
>>>add
>>> on.
>>> 
>>> === Alignment ===
>>> 
>>> The project builds with Apache Maven, the core runtime requires Apache
>>>CXF
>>> for REST binding (JAX-RS) and the sample scenario can be deployed into
>>>any
>>> compliant Servlet or J2EE container like Apache Tomcat. Furthermore we
>>>see
>>> OData protocol as an option to be supported by other Apache projects
>>>that
>>> have to expose data via a standardized protocol based interface.
>>> 
>>> == Known Risks ==
>>> 
>>> === Orphaned products ===
>>> 
>>> Apache OData is a fresh new codebase that targets the still moving
>>>OData
>>> standardization effort. Thus the future of this project depends
>>>heavily on
>>> the success of the standard. We hope and expect that our implementation
>>> efforts will strengthen and support the OData standard.
>>> 
>>> === Inexperience with Open Source ===
>>> 
>>> Some of the initial committers are experienced open source developers.
>>>But
>>> there are also committers which are new to open source.
>>> 
>>> === Homogenous Developers ===
>>> 
>>> The initial committers are from SAP working in different teams. One
>>>team
>>> is from Germany and has implemented the core parts of the library and
>>>the
>>> other team is from India and has implemented the JPA processor add-on.
>>> 
>>> === Reliance of Salaried Developers ===
>>> 
>>> All of the initial committers are paid by SAP to work on this or
>>>related
>>> projects.
>>> 
>>> === Relationships with Other Apache Products ===
>>> 
>>> Apache OData will directly use at least the following projects:
>>> 
>>> * Apache CXF - for REST bindings
>>> * Apache Commons - for encoding/decoding
>>> 
>>> Other Apache projects may be interested in using Apache OData to add
>>>OData
>>> support once the standard is final.
>>> 
>>> === An Excessive Fascination with the Apache Brand ===
>>> 
>>> We value Apache as a neutral place where diverse communities can work
>>> together on implementing shared standards. We hope that this part of
>>>the
>>> Apache brand helps attract contributions from many potential OData
>>>standard
>>> consumers. However, the brand value is not the main reason why we
>>>prefer to
>>> have this project at Apache.
>>> 
>>> == Documentation ==
>>> 
>>> This project is still at an early stage, so there is not much
>>> documentation available. See the OASIS OData page and odata.org web
>>>site
>>> for information about the OData standardization effort.
>>> 
>>> == Initial Source ==
>>> 
>>> * [[https://github.com/SAP/cloud-odata-java]]
>>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>>> 
>>> == Source and Intellectual Property Submission Plan ==
>>> 
>>> The complete code is under Apache Software License 2.
>>> 
>>> == External Dependencies ==
>>> 
>>> All the external dependencies of the initial codebases comply with
>>>Apache
>>> licensing policies.
>>> 
>>> == Cryptography ==
>>> 
>>> Apache OData is not expected to implement or use cryptographic code.
>>> 
>>> == Required Resources ==
>>> 
>>> === Mailing lists ===
>>> 
>>> * odata-dev'at'incubator.apache.org
>>> * odata-commits'at'incubator.apache.org
>>> * odata-private'at'incubator.apache.org
>>> 
>>> === Subversion Directory ===
>>> 
>>> writeable Git Repository (preferred)
>>> 
>>>    [[git://git.apache.org/odata.git]]
>>> 
>>> or SVN Directory
>>> 
>>>    [[https://svn.apache.org/repos/asf/incubator/odata]]
>>> 
>>> === Issue Tracking ===
>>> 
>>>    JIRA OData (OData)
>>> 
>>> === Other Resources ===
>>> 
>>>    none
>>> 
>>> == Initial Committers ==
>>> 
>>> || '''Name'''       || '''Email'''                 ||
>>> || Stephan Klevenz  || sklevenz'at'apache.org      ||
>>> || Jens Huesken     || jens.huesken'at'sap.com     ||
>>> || Christian Amend  || christian.amend'at'sap.com  ||
>>> || Michael Bolz     || michael.bolz'at'sap.com     ||
>>> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
>>> || Chandan V A      || chandan.v.a'at'sap.com      ||
>>> || Anirban Roy      || anirban.roy'at'sap.com      ||
>>> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>>> || Jobin John       || jobin.john'at'sap.com       ||
>>> || Joerg Singler    || joerg.singler'at'sap.com    ||
>>> 
>>> == Affiliations ==
>>> 
>>> || '''Name'''          || '''Affilitation''' ||
>>> || Stephan Klevenz     || SAP AG       ||
>>> || Jens Huesken        || SAP AG       ||
>>> || Christian Amend     || SAP AG       ||
>>> || Michael Bolz        || SAP AG       ||
>>> || Tamara Boehm        || SAP AG       ||
>>> || Chandan V A         || SAP AG       ||
>>> || Anirban Roy         || SAP AG       ||
>>> || Chitresh Chauhan    || SAP AG       ||
>>> || Jobin John          || SAP AG       ||
>>> || Joerg Singler       || SAP AG       ||
>>> 
>>> == Sponsors ==
>>> 
>>> Champion
>>> 
>>> * Florian Mueller
>>> 
>>> Nominated Mentors
>>> 
>>> * Florian Mueller
>>> * tbd.
>>> 
>>> Sponsoring Entiy
>>> 
>>> * Incubator PMC
>>> 
>>> ==== Links ====
>>> 
>>> * [1] [[http://www.odata.org]]
>>> * [2] [[
>>> 
>>>http://www.microsoft.com/openspecifications/en/us/programs/osp/default.a
>>>spx
>>> ]]
>>> * [3] 
>>>[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata
>>> ]]
>>> * [4] [[
>>> https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>> 
>>> 
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Dave Fisher <da...@comcast.net>.
On Jun 17, 2013, at 12:30 PM, Henry Saputra wrote:

> I love having the (reference) implementation for OData specs, should help
> the adoption of the specifications.
> 
> The immediate red flag is the homogeneous participation for initial
> committers. Any plan to add more diverse members as the initial goals?
> Does the project have contributions from external developers or community?

To me the question is if developers from outside of SAP are attracted to OData and also if the SAP team can properly be open to and inclusive of new volunteers on their dev list.

I think that there are a surprising and wide number of possible consumers and producers of content in this form.

Services can be defined based purely on the data they provide and consume. Putting OData services in the context of Tomcat and CXF aligns perfectly with my $dayjob. I could become a user of this software.

I would be willing to add my name as a Mentor.

Regards,
Dave



> 
> - Henry
> 
> 
> On Mon, Jun 17, 2013 at 8:35 AM, Klevenz, Stephan
> <st...@sap.com>wrote:
> 
>> Dear ASF members,
>> 
>> We would like to propose the OData project to the Incubator.
>> 
>> The OData Proposal is available at:
>> https://wiki.apache.org/incubator/ODataProposal
>> 
>> We welcome your feedback and suggestions.
>> 
>> Thanks!
>> 
>> Stephan Klevenz
>> 
>> 
>> 
>> = Apache OData =
>> 
>> === Abstract ===
>> 
>> Apache OData is a generic Java language implementation of the OData 2.0
>> specification which will serve as a code base for the upcoming OASIS OData
>> specification.
>> 
>> === Proposal ===
>> 
>> The Open Data Protocol (OData) [1] is a Web protocol for querying and
>> updating data that provides a way to unlock your data and free it from
>> silos that exist in applications today. OData does this by applying and
>> building upon Web technologies such as HTTP, Atom Publishing Protocol
>> (AtomPub) and JSON to provide access to information from a variety of
>> applications, services, and stores.
>> 
>> The Apache OData is a library which enables developers to implement OData
>> producers and OData consumers. Basic principles of the library are to
>> provide an OData 2.0 specification compliant OData Library, enhancements
>> shall be possible in a compatible manner, have a clear separation between
>> Core and API, to provide an option to build extensions on top. This library
>> should be base for implementing future releases of the specification.
>> 
>> === Background ===
>> 
>> OData was originally developed by Microsoft and is released in a version
>> 2.0 under an Open Specification Promise [2]. A lot of companies did show
>> interests in this protocol, used it in products and gave feedback back to
>> Microsoft. This joined effort resulted in a new release OData 3.0 in 2012,
>> this version became the basis for the OASIS technical committee [3] which
>> is currently working on a new version of the specification. This OASIS
>> standard release is expected this year.
>> 
>> The initial Java code of this project was developed by a development team
>> that had already experience with other OData 2.0 and 3.0 implementations at
>> SAP AG. The current code base implements OData 2.0 and because of this
>> version is widely used it is a good starting point to build an open source
>> community for the OData standard.
>> 
>> The current code also comes up with an implementation of an OData sample
>> service. On the one side this is an example for users which want to use the
>> library to expose their own data and on the other side it illustrates how
>> implemented features work.
>> 
>> Additionally, the code base includes an extension which is called JPA
>> processor. With this extension it is easy to expose any JPA persistence
>> model via OData protocol without a lot of coding.
>> 
>> === Rationale ===
>> 
>> More software vendors moving to OData means more choice for customers who
>> will be able to use different implementations. For the standard to succeed,
>> however, ensuring interoperability is paramount: in order to manage an ever
>> growing context and leverage the enormous portability and interoperability
>> issues that a globally adopted standard brings, it is necessary to think
>> about how to make the related ecosystem healthy and sustainable. Successful
>> modern standards are driven by:
>> 
>> * Clear documentation, built iteratively with continuous feedback from
>> stakeholders
>> * A clearly defined compatibility process, enforced by tools that allow
>> to gauge how implementations can be compatible and interoperable
>> * Accurate compliance criteria, documented in writing as well as in
>> actual testing code that measure how tools and libraries are able to
>> interoperate
>> * A sample implementation to clear up potential doubts and ensure that
>> the standard can actually be implemented in real life scenarios
>> 
>> The above mentioned pieces are able to make the development activity,
>> towards an OData implementation, easier and more successful. Having an
>> healthy ecosystem will ensure a smoother implementation process, more
>> compliant products, and ultimately, a wider adoption of the standard.
>> 
>> The OData ecosystem has been successful in creating and documenting early
>> versions of the standard, yet it might potentially lack two very important
>> aspects, that is a exhaustive implementation of the complete protocol that
>> can be used productively and to ensure interoperability. As much as such
>> artifacts can be developed independently by any OData proponent, the value
>> of having a neutral party as a steward of actual code is to be considered.
>> The Apache Software Foundation has been playing this kind of role for many
>> years, and can provide the perfect environment to foster contributions on
>> the OData theme with a great amount of expertise.
>> 
>> === Initial Goals ===
>> 
>> * Implement OData 2.0, make it final and mature
>> * Start implementation of OASIS OData draft specification
>> * Provide input and feedback for the draft specification to the OASIS
>> OData TC based on implementation
>> * Implement OData add-ons (library extensions and toolset)
>> 
>> == Current Status ==
>> 
>> === Meritocracy ===
>> 
>> Most of the initial committers are open source developers with different
>> experience levels and many of them have already worked in other open source
>> or Apache projects. We will follow standard Apache procedures in accepting
>> new contributors to the project team.
>> 
>> === Community ===
>> 
>> Managed by an OASIS Technical Committee, the OData standard definition
>> should be based on the idea of a community driven effort.
>> 
>> Apache OData aims to be a community driven initiative in developing a Java
>> OData implementation. Such an approach is allowing more transparency and
>> direct feedback even within the definition and improvement of OData
>> specifications.
>> 
>> We encourage everyone interested in OData to join the Apache OData effort.
>> 
>> === Core Developers ===
>> 
>> The development team is international and they have all strong skills in
>> OData protocol. Jens Huesken who is member of the OASIS OData TC is
>> providing specification feedback since OData 2.0. Stephan Klevenz, also a
>> OASIS OData TC member, was a committer of the Apache Chemistry project. He
>> has experience with the Incubator and Apache and was also a speaker on
>> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara Boehm
>> did implement core parts of the library. Chandan V A, Anirban Roy, Chitresh
>> Chauhan, Jobin John and Joerg Singler are working on the JPA processor add
>> on.
>> 
>> === Alignment ===
>> 
>> The project builds with Apache Maven, the core runtime requires Apache CXF
>> for REST binding (JAX-RS) and the sample scenario can be deployed into any
>> compliant Servlet or J2EE container like Apache Tomcat. Furthermore we see
>> OData protocol as an option to be supported by other Apache projects that
>> have to expose data via a standardized protocol based interface.
>> 
>> == Known Risks ==
>> 
>> === Orphaned products ===
>> 
>> Apache OData is a fresh new codebase that targets the still moving OData
>> standardization effort. Thus the future of this project depends heavily on
>> the success of the standard. We hope and expect that our implementation
>> efforts will strengthen and support the OData standard.
>> 
>> === Inexperience with Open Source ===
>> 
>> Some of the initial committers are experienced open source developers. But
>> there are also committers which are new to open source.
>> 
>> === Homogenous Developers ===
>> 
>> The initial committers are from SAP working in different teams. One team
>> is from Germany and has implemented the core parts of the library and the
>> other team is from India and has implemented the JPA processor add-on.
>> 
>> === Reliance of Salaried Developers ===
>> 
>> All of the initial committers are paid by SAP to work on this or related
>> projects.
>> 
>> === Relationships with Other Apache Products ===
>> 
>> Apache OData will directly use at least the following projects:
>> 
>> * Apache CXF - for REST bindings
>> * Apache Commons - for encoding/decoding
>> 
>> Other Apache projects may be interested in using Apache OData to add OData
>> support once the standard is final.
>> 
>> === An Excessive Fascination with the Apache Brand ===
>> 
>> We value Apache as a neutral place where diverse communities can work
>> together on implementing shared standards. We hope that this part of the
>> Apache brand helps attract contributions from many potential OData standard
>> consumers. However, the brand value is not the main reason why we prefer to
>> have this project at Apache.
>> 
>> == Documentation ==
>> 
>> This project is still at an early stage, so there is not much
>> documentation available. See the OASIS OData page and odata.org web site
>> for information about the OData standardization effort.
>> 
>> == Initial Source ==
>> 
>> * [[https://github.com/SAP/cloud-odata-java]]
>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>> 
>> == Source and Intellectual Property Submission Plan ==
>> 
>> The complete code is under Apache Software License 2.
>> 
>> == External Dependencies ==
>> 
>> All the external dependencies of the initial codebases comply with Apache
>> licensing policies.
>> 
>> == Cryptography ==
>> 
>> Apache OData is not expected to implement or use cryptographic code.
>> 
>> == Required Resources ==
>> 
>> === Mailing lists ===
>> 
>> * odata-dev'at'incubator.apache.org
>> * odata-commits'at'incubator.apache.org
>> * odata-private'at'incubator.apache.org
>> 
>> === Subversion Directory ===
>> 
>> writeable Git Repository (preferred)
>> 
>>    [[git://git.apache.org/odata.git]]
>> 
>> or SVN Directory
>> 
>>    [[https://svn.apache.org/repos/asf/incubator/odata]]
>> 
>> === Issue Tracking ===
>> 
>>    JIRA OData (OData)
>> 
>> === Other Resources ===
>> 
>>    none
>> 
>> == Initial Committers ==
>> 
>> || '''Name'''       || '''Email'''                 ||
>> || Stephan Klevenz  || sklevenz'at'apache.org      ||
>> || Jens Huesken     || jens.huesken'at'sap.com     ||
>> || Christian Amend  || christian.amend'at'sap.com  ||
>> || Michael Bolz     || michael.bolz'at'sap.com     ||
>> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
>> || Chandan V A      || chandan.v.a'at'sap.com      ||
>> || Anirban Roy      || anirban.roy'at'sap.com      ||
>> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>> || Jobin John       || jobin.john'at'sap.com       ||
>> || Joerg Singler    || joerg.singler'at'sap.com    ||
>> 
>> == Affiliations ==
>> 
>> || '''Name'''          || '''Affilitation''' ||
>> || Stephan Klevenz     || SAP AG       ||
>> || Jens Huesken        || SAP AG       ||
>> || Christian Amend     || SAP AG       ||
>> || Michael Bolz        || SAP AG       ||
>> || Tamara Boehm        || SAP AG       ||
>> || Chandan V A         || SAP AG       ||
>> || Anirban Roy         || SAP AG       ||
>> || Chitresh Chauhan    || SAP AG       ||
>> || Jobin John          || SAP AG       ||
>> || Joerg Singler       || SAP AG       ||
>> 
>> == Sponsors ==
>> 
>> Champion
>> 
>> * Florian Mueller
>> 
>> Nominated Mentors
>> 
>> * Florian Mueller
>> * tbd.
>> 
>> Sponsoring Entiy
>> 
>> * Incubator PMC
>> 
>> ==== Links ====
>> 
>> * [1] [[http://www.odata.org]]
>> * [2] [[
>> http://www.microsoft.com/openspecifications/en/us/programs/osp/default.aspx
>> ]]
>> * [3] [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata
>> ]]
>> * [4] [[
>> https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>> 
>> 


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi Henry,

You are absolutely right and we are aware of that we are currently a
homogenous community. We don't want to stay this and encourage everyone to
join our effort and become a committer of the Apache OData project. OData
as an open OASIS standard will profit from a diversified OData project at
Apache. 

At GitHUB, where we released the original code a few weeks ago, we
received already some contributions from other developers. And we are in
contact with the technical committee at OASIS to create awareness about
this proposal. This could also create interest by other people.

Nethertheless this project is a young one and has to do effort to increase
its community.

Regards,
Stephan



On 17.06.13 21:30, "Henry Saputra" <he...@gmail.com> wrote:

>I love having the (reference) implementation for OData specs, should help
>the adoption of the specifications.
>
>The immediate red flag is the homogeneous participation for initial
>committers. Any plan to add more diverse members as the initial goals?
>Does the project have contributions from external developers or community?
>
>- Henry
>
>
>On Mon, Jun 17, 2013 at 8:35 AM, Klevenz, Stephan
><st...@sap.com>wrote:
>
>> Dear ASF members,
>>
>> We would like to propose the OData project to the Incubator.
>>
>> The OData Proposal is available at:
>> https://wiki.apache.org/incubator/ODataProposal
>>
>> We welcome your feedback and suggestions.
>>
>> Thanks!
>>
>> Stephan Klevenz
>>
>>
>>
>> = Apache OData =
>>
>> === Abstract ===
>>
>> Apache OData is a generic Java language implementation of the OData 2.0
>> specification which will serve as a code base for the upcoming OASIS
>>OData
>> specification.
>>
>> === Proposal ===
>>
>> The Open Data Protocol (OData) [1] is a Web protocol for querying and
>> updating data that provides a way to unlock your data and free it from
>> silos that exist in applications today. OData does this by applying and
>> building upon Web technologies such as HTTP, Atom Publishing Protocol
>> (AtomPub) and JSON to provide access to information from a variety of
>> applications, services, and stores.
>>
>> The Apache OData is a library which enables developers to implement
>>OData
>> producers and OData consumers. Basic principles of the library are to
>> provide an OData 2.0 specification compliant OData Library, enhancements
>> shall be possible in a compatible manner, have a clear separation
>>between
>> Core and API, to provide an option to build extensions on top. This
>>library
>> should be base for implementing future releases of the specification.
>>
>> === Background ===
>>
>> OData was originally developed by Microsoft and is released in a version
>> 2.0 under an Open Specification Promise [2]. A lot of companies did show
>> interests in this protocol, used it in products and gave feedback back
>>to
>> Microsoft. This joined effort resulted in a new release OData 3.0 in
>>2012,
>> this version became the basis for the OASIS technical committee [3]
>>which
>> is currently working on a new version of the specification. This OASIS
>> standard release is expected this year.
>>
>> The initial Java code of this project was developed by a development
>>team
>> that had already experience with other OData 2.0 and 3.0
>>implementations at
>> SAP AG. The current code base implements OData 2.0 and because of this
>> version is widely used it is a good starting point to build an open
>>source
>> community for the OData standard.
>>
>> The current code also comes up with an implementation of an OData sample
>> service. On the one side this is an example for users which want to use
>>the
>> library to expose their own data and on the other side it illustrates
>>how
>> implemented features work.
>>
>> Additionally, the code base includes an extension which is called JPA
>> processor. With this extension it is easy to expose any JPA persistence
>> model via OData protocol without a lot of coding.
>>
>> === Rationale ===
>>
>> More software vendors moving to OData means more choice for customers
>>who
>> will be able to use different implementations. For the standard to
>>succeed,
>> however, ensuring interoperability is paramount: in order to manage an
>>ever
>> growing context and leverage the enormous portability and
>>interoperability
>> issues that a globally adopted standard brings, it is necessary to think
>> about how to make the related ecosystem healthy and sustainable.
>>Successful
>> modern standards are driven by:
>>
>>  * Clear documentation, built iteratively with continuous feedback from
>> stakeholders
>>  * A clearly defined compatibility process, enforced by tools that allow
>> to gauge how implementations can be compatible and interoperable
>>  * Accurate compliance criteria, documented in writing as well as in
>> actual testing code that measure how tools and libraries are able to
>> interoperate
>>  * A sample implementation to clear up potential doubts and ensure that
>> the standard can actually be implemented in real life scenarios
>>
>> The above mentioned pieces are able to make the development activity,
>> towards an OData implementation, easier and more successful. Having an
>> healthy ecosystem will ensure a smoother implementation process, more
>> compliant products, and ultimately, a wider adoption of the standard.
>>
>> The OData ecosystem has been successful in creating and documenting
>>early
>> versions of the standard, yet it might potentially lack two very
>>important
>> aspects, that is a exhaustive implementation of the complete protocol
>>that
>> can be used productively and to ensure interoperability. As much as such
>> artifacts can be developed independently by any OData proponent, the
>>value
>> of having a neutral party as a steward of actual code is to be
>>considered.
>> The Apache Software Foundation has been playing this kind of role for
>>many
>> years, and can provide the perfect environment to foster contributions
>>on
>> the OData theme with a great amount of expertise.
>>
>> === Initial Goals ===
>>
>>  * Implement OData 2.0, make it final and mature
>>  * Start implementation of OASIS OData draft specification
>>  * Provide input and feedback for the draft specification to the OASIS
>> OData TC based on implementation
>>  * Implement OData add-ons (library extensions and toolset)
>>
>> == Current Status ==
>>
>> === Meritocracy ===
>>
>> Most of the initial committers are open source developers with different
>> experience levels and many of them have already worked in other open
>>source
>> or Apache projects. We will follow standard Apache procedures in
>>accepting
>> new contributors to the project team.
>>
>> === Community ===
>>
>> Managed by an OASIS Technical Committee, the OData standard definition
>> should be based on the idea of a community driven effort.
>>
>> Apache OData aims to be a community driven initiative in developing a
>>Java
>> OData implementation. Such an approach is allowing more transparency and
>> direct feedback even within the definition and improvement of OData
>> specifications.
>>
>> We encourage everyone interested in OData to join the Apache OData
>>effort.
>>
>> === Core Developers ===
>>
>> The development team is international and they have all strong skills in
>> OData protocol. Jens Huesken who is member of the OASIS OData TC is
>> providing specification feedback since OData 2.0. Stephan Klevenz, also
>>a
>> OASIS OData TC member, was a committer of the Apache Chemistry project.
>>He
>> has experience with the Incubator and Apache and was also a speaker on
>> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>Boehm
>> did implement core parts of the library. Chandan V A, Anirban Roy,
>>Chitresh
>> Chauhan, Jobin John and Joerg Singler are working on the JPA processor
>>add
>> on.
>>
>> === Alignment ===
>>
>> The project builds with Apache Maven, the core runtime requires Apache
>>CXF
>> for REST binding (JAX-RS) and the sample scenario can be deployed into
>>any
>> compliant Servlet or J2EE container like Apache Tomcat. Furthermore we
>>see
>> OData protocol as an option to be supported by other Apache projects
>>that
>> have to expose data via a standardized protocol based interface.
>>
>> == Known Risks ==
>>
>> === Orphaned products ===
>>
>> Apache OData is a fresh new codebase that targets the still moving OData
>> standardization effort. Thus the future of this project depends heavily
>>on
>> the success of the standard. We hope and expect that our implementation
>> efforts will strengthen and support the OData standard.
>>
>> === Inexperience with Open Source ===
>>
>> Some of the initial committers are experienced open source developers.
>>But
>> there are also committers which are new to open source.
>>
>> === Homogenous Developers ===
>>
>> The initial committers are from SAP working in different teams. One team
>> is from Germany and has implemented the core parts of the library and
>>the
>> other team is from India and has implemented the JPA processor add-on.
>>
>> === Reliance of Salaried Developers ===
>>
>> All of the initial committers are paid by SAP to work on this or related
>> projects.
>>
>> === Relationships with Other Apache Products ===
>>
>> Apache OData will directly use at least the following projects:
>>
>>  * Apache CXF - for REST bindings
>>  * Apache Commons - for encoding/decoding
>>
>> Other Apache projects may be interested in using Apache OData to add
>>OData
>> support once the standard is final.
>>
>> === An Excessive Fascination with the Apache Brand ===
>>
>> We value Apache as a neutral place where diverse communities can work
>> together on implementing shared standards. We hope that this part of the
>> Apache brand helps attract contributions from many potential OData
>>standard
>> consumers. However, the brand value is not the main reason why we
>>prefer to
>> have this project at Apache.
>>
>> == Documentation ==
>>
>> This project is still at an early stage, so there is not much
>> documentation available. See the OASIS OData page and odata.org web site
>> for information about the OData standardization effort.
>>
>> == Initial Source ==
>>
>>  * [[https://github.com/SAP/cloud-odata-java]]
>>  * [[https://www.ohloh.net/p/cloud-odata-java]]
>>
>> == Source and Intellectual Property Submission Plan ==
>>
>> The complete code is under Apache Software License 2.
>>
>> == External Dependencies ==
>>
>> All the external dependencies of the initial codebases comply with
>>Apache
>> licensing policies.
>>
>> == Cryptography ==
>>
>> Apache OData is not expected to implement or use cryptographic code.
>>
>> == Required Resources ==
>>
>> === Mailing lists ===
>>
>>  * odata-dev'at'incubator.apache.org
>>  * odata-commits'at'incubator.apache.org
>>  * odata-private'at'incubator.apache.org
>>
>> === Subversion Directory ===
>>
>> writeable Git Repository (preferred)
>>
>>     [[git://git.apache.org/odata.git]]
>>
>> or SVN Directory
>>
>>     [[https://svn.apache.org/repos/asf/incubator/odata]]
>>
>> === Issue Tracking ===
>>
>>     JIRA OData (OData)
>>
>> === Other Resources ===
>>
>>     none
>>
>> == Initial Committers ==
>>
>> || '''Name'''       || '''Email'''                 ||
>> || Stephan Klevenz  || sklevenz'at'apache.org      ||
>> || Jens Huesken     || jens.huesken'at'sap.com     ||
>> || Christian Amend  || christian.amend'at'sap.com  ||
>> || Michael Bolz     || michael.bolz'at'sap.com     ||
>> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
>> || Chandan V A      || chandan.v.a'at'sap.com      ||
>> || Anirban Roy      || anirban.roy'at'sap.com      ||
>> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>> || Jobin John       || jobin.john'at'sap.com       ||
>> || Joerg Singler    || joerg.singler'at'sap.com    ||
>>
>> == Affiliations ==
>>
>> || '''Name'''          || '''Affilitation''' ||
>> || Stephan Klevenz     || SAP AG       ||
>> || Jens Huesken        || SAP AG       ||
>> || Christian Amend     || SAP AG       ||
>> || Michael Bolz        || SAP AG       ||
>> || Tamara Boehm        || SAP AG       ||
>> || Chandan V A         || SAP AG       ||
>> || Anirban Roy         || SAP AG       ||
>> || Chitresh Chauhan    || SAP AG       ||
>> || Jobin John          || SAP AG       ||
>> || Joerg Singler       || SAP AG       ||
>>
>> == Sponsors ==
>>
>> Champion
>>
>>  * Florian Mueller
>>
>> Nominated Mentors
>>
>>  * Florian Mueller
>>  * tbd.
>>
>> Sponsoring Entiy
>>
>>  * Incubator PMC
>>
>> ==== Links ====
>>
>>  * [1] [[http://www.odata.org]]
>>  * [2] [[
>> 
>>http://www.microsoft.com/openspecifications/en/us/programs/osp/default.as
>>px
>> ]]
>>  * [3] 
>>[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata
>> ]]
>>  * [4] [[
>> https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>
>>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Henry Saputra <he...@gmail.com>.
I love having the (reference) implementation for OData specs, should help
the adoption of the specifications.

The immediate red flag is the homogeneous participation for initial
committers. Any plan to add more diverse members as the initial goals?
Does the project have contributions from external developers or community?

- Henry


On Mon, Jun 17, 2013 at 8:35 AM, Klevenz, Stephan
<st...@sap.com>wrote:

> Dear ASF members,
>
> We would like to propose the OData project to the Incubator.
>
> The OData Proposal is available at:
> https://wiki.apache.org/incubator/ODataProposal
>
> We welcome your feedback and suggestions.
>
> Thanks!
>
> Stephan Klevenz
>
>
>
> = Apache OData =
>
> === Abstract ===
>
> Apache OData is a generic Java language implementation of the OData 2.0
> specification which will serve as a code base for the upcoming OASIS OData
> specification.
>
> === Proposal ===
>
> The Open Data Protocol (OData) [1] is a Web protocol for querying and
> updating data that provides a way to unlock your data and free it from
> silos that exist in applications today. OData does this by applying and
> building upon Web technologies such as HTTP, Atom Publishing Protocol
> (AtomPub) and JSON to provide access to information from a variety of
> applications, services, and stores.
>
> The Apache OData is a library which enables developers to implement OData
> producers and OData consumers. Basic principles of the library are to
> provide an OData 2.0 specification compliant OData Library, enhancements
> shall be possible in a compatible manner, have a clear separation between
> Core and API, to provide an option to build extensions on top. This library
> should be base for implementing future releases of the specification.
>
> === Background ===
>
> OData was originally developed by Microsoft and is released in a version
> 2.0 under an Open Specification Promise [2]. A lot of companies did show
> interests in this protocol, used it in products and gave feedback back to
> Microsoft. This joined effort resulted in a new release OData 3.0 in 2012,
> this version became the basis for the OASIS technical committee [3] which
> is currently working on a new version of the specification. This OASIS
> standard release is expected this year.
>
> The initial Java code of this project was developed by a development team
> that had already experience with other OData 2.0 and 3.0 implementations at
> SAP AG. The current code base implements OData 2.0 and because of this
> version is widely used it is a good starting point to build an open source
> community for the OData standard.
>
> The current code also comes up with an implementation of an OData sample
> service. On the one side this is an example for users which want to use the
> library to expose their own data and on the other side it illustrates how
> implemented features work.
>
> Additionally, the code base includes an extension which is called JPA
> processor. With this extension it is easy to expose any JPA persistence
> model via OData protocol without a lot of coding.
>
> === Rationale ===
>
> More software vendors moving to OData means more choice for customers who
> will be able to use different implementations. For the standard to succeed,
> however, ensuring interoperability is paramount: in order to manage an ever
> growing context and leverage the enormous portability and interoperability
> issues that a globally adopted standard brings, it is necessary to think
> about how to make the related ecosystem healthy and sustainable. Successful
> modern standards are driven by:
>
>  * Clear documentation, built iteratively with continuous feedback from
> stakeholders
>  * A clearly defined compatibility process, enforced by tools that allow
> to gauge how implementations can be compatible and interoperable
>  * Accurate compliance criteria, documented in writing as well as in
> actual testing code that measure how tools and libraries are able to
> interoperate
>  * A sample implementation to clear up potential doubts and ensure that
> the standard can actually be implemented in real life scenarios
>
> The above mentioned pieces are able to make the development activity,
> towards an OData implementation, easier and more successful. Having an
> healthy ecosystem will ensure a smoother implementation process, more
> compliant products, and ultimately, a wider adoption of the standard.
>
> The OData ecosystem has been successful in creating and documenting early
> versions of the standard, yet it might potentially lack two very important
> aspects, that is a exhaustive implementation of the complete protocol that
> can be used productively and to ensure interoperability. As much as such
> artifacts can be developed independently by any OData proponent, the value
> of having a neutral party as a steward of actual code is to be considered.
> The Apache Software Foundation has been playing this kind of role for many
> years, and can provide the perfect environment to foster contributions on
> the OData theme with a great amount of expertise.
>
> === Initial Goals ===
>
>  * Implement OData 2.0, make it final and mature
>  * Start implementation of OASIS OData draft specification
>  * Provide input and feedback for the draft specification to the OASIS
> OData TC based on implementation
>  * Implement OData add-ons (library extensions and toolset)
>
> == Current Status ==
>
> === Meritocracy ===
>
> Most of the initial committers are open source developers with different
> experience levels and many of them have already worked in other open source
> or Apache projects. We will follow standard Apache procedures in accepting
> new contributors to the project team.
>
> === Community ===
>
> Managed by an OASIS Technical Committee, the OData standard definition
> should be based on the idea of a community driven effort.
>
> Apache OData aims to be a community driven initiative in developing a Java
> OData implementation. Such an approach is allowing more transparency and
> direct feedback even within the definition and improvement of OData
> specifications.
>
> We encourage everyone interested in OData to join the Apache OData effort.
>
> === Core Developers ===
>
> The development team is international and they have all strong skills in
> OData protocol. Jens Huesken who is member of the OASIS OData TC is
> providing specification feedback since OData 2.0. Stephan Klevenz, also a
> OASIS OData TC member, was a committer of the Apache Chemistry project. He
> has experience with the Incubator and Apache and was also a speaker on
> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara Boehm
> did implement core parts of the library. Chandan V A, Anirban Roy, Chitresh
> Chauhan, Jobin John and Joerg Singler are working on the JPA processor add
> on.
>
> === Alignment ===
>
> The project builds with Apache Maven, the core runtime requires Apache CXF
> for REST binding (JAX-RS) and the sample scenario can be deployed into any
> compliant Servlet or J2EE container like Apache Tomcat. Furthermore we see
> OData protocol as an option to be supported by other Apache projects that
> have to expose data via a standardized protocol based interface.
>
> == Known Risks ==
>
> === Orphaned products ===
>
> Apache OData is a fresh new codebase that targets the still moving OData
> standardization effort. Thus the future of this project depends heavily on
> the success of the standard. We hope and expect that our implementation
> efforts will strengthen and support the OData standard.
>
> === Inexperience with Open Source ===
>
> Some of the initial committers are experienced open source developers. But
> there are also committers which are new to open source.
>
> === Homogenous Developers ===
>
> The initial committers are from SAP working in different teams. One team
> is from Germany and has implemented the core parts of the library and the
> other team is from India and has implemented the JPA processor add-on.
>
> === Reliance of Salaried Developers ===
>
> All of the initial committers are paid by SAP to work on this or related
> projects.
>
> === Relationships with Other Apache Products ===
>
> Apache OData will directly use at least the following projects:
>
>  * Apache CXF - for REST bindings
>  * Apache Commons - for encoding/decoding
>
> Other Apache projects may be interested in using Apache OData to add OData
> support once the standard is final.
>
> === An Excessive Fascination with the Apache Brand ===
>
> We value Apache as a neutral place where diverse communities can work
> together on implementing shared standards. We hope that this part of the
> Apache brand helps attract contributions from many potential OData standard
> consumers. However, the brand value is not the main reason why we prefer to
> have this project at Apache.
>
> == Documentation ==
>
> This project is still at an early stage, so there is not much
> documentation available. See the OASIS OData page and odata.org web site
> for information about the OData standardization effort.
>
> == Initial Source ==
>
>  * [[https://github.com/SAP/cloud-odata-java]]
>  * [[https://www.ohloh.net/p/cloud-odata-java]]
>
> == Source and Intellectual Property Submission Plan ==
>
> The complete code is under Apache Software License 2.
>
> == External Dependencies ==
>
> All the external dependencies of the initial codebases comply with Apache
> licensing policies.
>
> == Cryptography ==
>
> Apache OData is not expected to implement or use cryptographic code.
>
> == Required Resources ==
>
> === Mailing lists ===
>
>  * odata-dev'at'incubator.apache.org
>  * odata-commits'at'incubator.apache.org
>  * odata-private'at'incubator.apache.org
>
> === Subversion Directory ===
>
> writeable Git Repository (preferred)
>
>     [[git://git.apache.org/odata.git]]
>
> or SVN Directory
>
>     [[https://svn.apache.org/repos/asf/incubator/odata]]
>
> === Issue Tracking ===
>
>     JIRA OData (OData)
>
> === Other Resources ===
>
>     none
>
> == Initial Committers ==
>
> || '''Name'''       || '''Email'''                 ||
> || Stephan Klevenz  || sklevenz'at'apache.org      ||
> || Jens Huesken     || jens.huesken'at'sap.com     ||
> || Christian Amend  || christian.amend'at'sap.com  ||
> || Michael Bolz     || michael.bolz'at'sap.com     ||
> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
> || Chandan V A      || chandan.v.a'at'sap.com      ||
> || Anirban Roy      || anirban.roy'at'sap.com      ||
> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
> || Jobin John       || jobin.john'at'sap.com       ||
> || Joerg Singler    || joerg.singler'at'sap.com    ||
>
> == Affiliations ==
>
> || '''Name'''          || '''Affilitation''' ||
> || Stephan Klevenz     || SAP AG       ||
> || Jens Huesken        || SAP AG       ||
> || Christian Amend     || SAP AG       ||
> || Michael Bolz        || SAP AG       ||
> || Tamara Boehm        || SAP AG       ||
> || Chandan V A         || SAP AG       ||
> || Anirban Roy         || SAP AG       ||
> || Chitresh Chauhan    || SAP AG       ||
> || Jobin John          || SAP AG       ||
> || Joerg Singler       || SAP AG       ||
>
> == Sponsors ==
>
> Champion
>
>  * Florian Mueller
>
> Nominated Mentors
>
>  * Florian Mueller
>  * tbd.
>
> Sponsoring Entiy
>
>  * Incubator PMC
>
> ==== Links ====
>
>  * [1] [[http://www.odata.org]]
>  * [2] [[
> http://www.microsoft.com/openspecifications/en/us/programs/osp/default.aspx
> ]]
>  * [3] [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata
> ]]
>  * [4] [[
> https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>
>

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Olemis,


Thanks for interest. I have added Apache Bloodhound to the list of
potential integrators in the proposal document
(https://wiki.apache.org/incubator/ODataProposal).

About your question to OData Phyton binding. This is very interesting
because of OData as a web protocol is not just bound to a single
implementation technology. We don't have concrete plans but an Apache
OData community could potentially benefit from a Phyton contribution.

Regards,
Stephan 

On 17.06.13 19:33, "Olemis Lang" <ol...@gmail.com> wrote:

>On 6/17/13, Klevenz, Stephan <st...@sap.com> wrote:
>> Dear ASF members,
>>
>> We would like to propose the OData project to the Incubator.
>>
>> The OData Proposal is available at:
>> https://wiki.apache.org/incubator/ODataProposal
>>
>> We welcome your feedback and suggestions.
>>
>
>JFTR , at present there is an ongoing effort to start working on an
>integration of the oData standards with Apache Bloodhound (similar to
>TracGVizPlugin [1]_ for Google Charts API ; I'll follow up with
>further details in a few days if this turns out to be useful /
>required ;) . This might also be added to the list of potential
>integrations in section «Relationships with Other Apache Products» .
>
>Therefore I'm curious and would like to know if some effort will be
>spent in building official Python bindings for oData .
>
>FWIW , the way I see it this project will be a very beneficial
>addition to the Apache ecosystem
>
>.. [1] trachacks:TracGvizPlugin
>        (http://trac-hacks.org/wiki/TracGvizPlugin)
>
>-- 
>Regards,
>
>Olemis.
>
>Apache Bloodhound contributor
>http://issues.apache.org/bloodhound
>
>Blog ES: http://simelo-es.blogspot.com/
>Blog EN: http://simelo-en.blogspot.com/
>
>Featured article:


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Olemis Lang <ol...@gmail.com>.
On 6/17/13, Klevenz, Stephan <st...@sap.com> wrote:
> Dear ASF members,
>
> We would like to propose the OData project to the Incubator.
>
> The OData Proposal is available at:
> https://wiki.apache.org/incubator/ODataProposal
>
> We welcome your feedback and suggestions.
>

JFTR , at present there is an ongoing effort to start working on an
integration of the oData standards with Apache™ Bloodhound (similar to
TracGVizPlugin [1]_ for Google Charts API ; I'll follow up with
further details in a few days if this turns out to be useful /
required ;) . This might also be added to the list of potential
integrations in section «Relationships with Other Apache Products» .

Therefore I'm curious and would like to know if some effort will be
spent in building official Python bindings for oData .

FWIW , the way I see it this project will be a very beneficial
addition to the Apache ecosystem

.. [1] trachacks:TracGvizPlugin
        (http://trac-hacks.org/wiki/TracGvizPlugin)

-- 
Regards,

Olemis.

Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Anny,

Thanks for your feedback. Maybe you have recognized that Apache Olingo has
passed the vote (Thanks all!!!) and starts now incubation. As soon as we
have a mailing list I would like to encourage you to have this interesting
discussion on our incubator mailing list.

Regards,
Stephan



On 05.07.13 15:17, "Anny G" <gv...@gmail.com> wrote:

>Dear all,
>
>This is a very good initiative. We use OData in our integration projects
>as
>the standard protocol. Based on our experiences with OData as a standard
>and
>its exiting ecosystem, I have a few suggestions,
>
>1. Please start by supporting OData v3 (not v2). v2 is relatively old,
>lacks
>some key features that are present in v3. Also, the ACCEPT header
>semantics
>for JSON format is compatible between v3 and v4 (the current in progress
>version) but not v2. This is critical from a consumer point of view.
>Another
>reason to start with v3 is that it is the version that was submitted to
>OASIS for standardizing which will come out very soon as v4.
>
>2. Please evaluate odata4j which is designed very well despite some bugs
>and
>deficiencies. This allows this apache project to take the best of ideas
>from
>2 of the available implementations of odata on java.
>
>Thanks & Regards,
>Anny G
>
>
>
>
>--
>View this message in context:
>http://apache-incubator-general.996316.n3.nabble.com/PROPOSAL-OData-Propos
>al-for-Incubator-tp35801p36019.html
>Sent from the Apache Incubator - General mailing list archive at
>Nabble.com.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Anny G <gv...@gmail.com>.
Dear all,

This is a very good initiative. We use OData in our integration projects as
the standard protocol. Based on our experiences with OData as a standard and
its exiting ecosystem, I have a few suggestions,

1. Please start by supporting OData v3 (not v2). v2 is relatively old, lacks
some key features that are present in v3. Also, the ACCEPT header semantics
for JSON format is compatible between v3 and v4 (the current in progress
version) but not v2. This is critical from a consumer point of view. Another
reason to start with v3 is that it is the version that was submitted to
OASIS for standardizing which will come out very soon as v4.

2. Please evaluate odata4j which is designed very well despite some bugs and
deficiencies. This allows this apache project to take the best of ideas from
2 of the available implementations of odata on java.

Thanks & Regards,
Anny G




--
View this message in context: http://apache-incubator-general.996316.n3.nabble.com/PROPOSAL-OData-Proposal-for-Incubator-tp35801p36019.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.

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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Dear Apache Members,

After this discussion we have renamed the proposal to Apache Olingo.

https://wiki.apache.org/incubator/OlingoProposal

@Dennis: Thanks again to your feedback here.

Regards,
Stephan

On 21.06.13 17:42, "Dennis E. Hamilton" <de...@acm.org> wrote:

>Stephen,
>
>I support your choice to have a different name.
>
> - Dennis
>
>I'm not sure how "Olingo" is pronounced in Spanish but I'm certain there
>will be much fun creating artwork of the little critter.  It looks like
>an animal that must be on the cover of an O'Reilly book somewhere.  (I
>find raccoons, their cousins, more appealing, except when they are
>pillaging the cherry tree at my house.)
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Friday, June 21, 2013 06:34 AM
>To: dennis.hamilton@acm.org; general@incubator.apache.org
>Subject: Re: [PROPOSAL] OData Proposal for Incubator
>Importance: High
>
>Hi Dennis,
>
>Sorry for coming back so late to your valuable feedback. After re-thinking
>about the trademark issue and your thoughts about confusion we come to
>conclusion to use a different name for the project. I would like to change
>our project name to
>
>Apache Olingo
>
>Olingo is a little bear [1] and that name should avoid any confusion with
>the OASIS standard or any other potential trademark holder. If there are
>no concerns then I will go and change our proposal to Apache Olingo.
>
>WDYT?
>
>Regards,
>stephan
>
>[1] http://en.wikipedia.org/wiki/Olingo
>
>On 18.06.13 15:58, "Dennis E. Hamilton" <de...@acm.org> wrote:
>
>>I think there will be an issue with regard to trademarks and you will
>>have to deal with folks seeing the trademark of "Apache OData" as a
>>land-grab at "OData" itself.  The simplicity you think is avoiding
>>confusion is, in that respect, causing confusion.
>>
>>In any case, it is always wise to avoid confusion of a (standard)
>>specification, even OASIS Standard OData v3.0 or whatever, with the name
>>of an implementation.  OASIS is going to make their own claims about some
>>of those terms as well, if the past practice is any guide.
>>
>> - Dennis
>>
>>The ODF Toolkit snuck by, much to my dismay, even capturing odf as their
>>incubator repository name, but they may have to deal with that to
>>graduate to a TLP.
>>
>>-----Original Message-----
>>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>>Sent: Tuesday, June 18, 2013 06:27 AM
>>To: general@incubator.apache.org
>>Cc: dennis.hamilton@acm.org
>>Subject: Re: [PROPOSAL] OData Proposal for Incubator
>>
>>Hello Dennis,
>>
>>Good point! The project naming was a challenge for us and maybe I just
>>can
>>explain why we prefer Apache OData as project name. The main reason is
>>search. 
>>
>>Someone who is interested in OData will use this term and the result page
>>will today list odata.org as the protocols homepage, Wikipedia which is
>>fine and the OASIS TC. In future we would like to see that Apache OData
>>is
>>highly ranked and completes the search result list.
>>
>>If we use a different name someone has to know this name and has to
>>search
>>for it explicitly. We would like to keep it simple and avoid confusion.
>>
>>We had also a look into the ASF project naming guidelines and I think
>>most
>>of the points there are considered by the name Apache OData.
>>
>>
>>Regards,
>>Stephan
>>
>>On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:
>>
>>>I think one concern here is appropriation of a generic, specified-tied
>>>name to an implementation, even a reference implementation.
>>>
>>>"Apache OData" seems over-reaching in that respect, especially since
>>>there are other projects, at ASF and elsewhere, that may employ OData
>>>bindings and services of one sort or another.
>>[ ... ]
>>
>


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

RE: [PROPOSAL] OData Proposal for Incubator

Posted by "Dennis E. Hamilton" <de...@acm.org>.
Stephen,

I support your choice to have a different name.  

 - Dennis

I'm not sure how "Olingo" is pronounced in Spanish but I'm certain there will be much fun creating artwork of the little critter.  It looks like an animal that must be on the cover of an O'Reilly book somewhere.  (I find raccoons, their cousins, more appealing, except when they are pillaging the cherry tree at my house.)

-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com] 
Sent: Friday, June 21, 2013 06:34 AM
To: dennis.hamilton@acm.org; general@incubator.apache.org
Subject: Re: [PROPOSAL] OData Proposal for Incubator
Importance: High

Hi Dennis,

Sorry for coming back so late to your valuable feedback. After re-thinking
about the trademark issue and your thoughts about confusion we come to
conclusion to use a different name for the project. I would like to change
our project name to

Apache Olingo

Olingo is a little bear [1] and that name should avoid any confusion with
the OASIS standard or any other potential trademark holder. If there are
no concerns then I will go and change our proposal to Apache Olingo.

WDYT?

Regards,
stephan

[1] http://en.wikipedia.org/wiki/Olingo

On 18.06.13 15:58, "Dennis E. Hamilton" <de...@acm.org> wrote:

>I think there will be an issue with regard to trademarks and you will
>have to deal with folks seeing the trademark of "Apache OData" as a
>land-grab at "OData" itself.  The simplicity you think is avoiding
>confusion is, in that respect, causing confusion.
>
>In any case, it is always wise to avoid confusion of a (standard)
>specification, even OASIS Standard OData v3.0 or whatever, with the name
>of an implementation.  OASIS is going to make their own claims about some
>of those terms as well, if the past practice is any guide.
>
> - Dennis
>
>The ODF Toolkit snuck by, much to my dismay, even capturing odf as their
>incubator repository name, but they may have to deal with that to
>graduate to a TLP.
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Tuesday, June 18, 2013 06:27 AM
>To: general@incubator.apache.org
>Cc: dennis.hamilton@acm.org
>Subject: Re: [PROPOSAL] OData Proposal for Incubator
>
>Hello Dennis,
>
>Good point! The project naming was a challenge for us and maybe I just can
>explain why we prefer Apache OData as project name. The main reason is
>search. 
>
>Someone who is interested in OData will use this term and the result page
>will today list odata.org as the protocols homepage, Wikipedia which is
>fine and the OASIS TC. In future we would like to see that Apache OData is
>highly ranked and completes the search result list.
>
>If we use a different name someone has to know this name and has to search
>for it explicitly. We would like to keep it simple and avoid confusion.
>
>We had also a look into the ASF project naming guidelines and I think most
>of the points there are considered by the name Apache OData.
>
>
>Regards,
>Stephan
>
>On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:
>
>>I think one concern here is appropriation of a generic, specified-tied
>>name to an implementation, even a reference implementation.
>>
>>"Apache OData" seems over-reaching in that respect, especially since
>>there are other projects, at ASF and elsewhere, that may employ OData
>>bindings and services of one sort or another.
>[ ... ]
>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Sam Ruby <ru...@intertwingly.net>.
On Tue, Jun 18, 2013 at 9:58 AM, Dennis E. Hamilton
<de...@acm.org> wrote:
> I think there will be an issue with regard to trademarks and you will have to deal with folks seeing the trademark of "Apache OData" as a land-grab at "OData" itself.  The simplicity you think is avoiding confusion is, in that respect, causing confusion.
>
> In any case, it is always wise to avoid confusion of a (standard) specification, even OASIS Standard OData v3.0 or whatever, with the name of an implementation.  OASIS is going to make their own claims about some of those terms as well, if the past practice is any guide.

Existing counter examples here at the ASF: c++ standard library,
commons, directory, logging, traffic server, uima, web services, xml;
with uima being particularly relevant.

>  - Dennis
>
> The ODF Toolkit snuck by, much to my dismay, even capturing odf as their incubator repository name, but they may have to deal with that to graduate to a TLP.

- Sam Ruby

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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi Dennis,

Sorry for coming back so late to your valuable feedback. After re-thinking
about the trademark issue and your thoughts about confusion we come to
conclusion to use a different name for the project. I would like to change
our project name to

Apache Olingo

Olingo is a little bear [1] and that name should avoid any confusion with
the OASIS standard or any other potential trademark holder. If there are
no concerns then I will go and change our proposal to Apache Olingo.

WDYT?

Regards,
stephan

[1] http://en.wikipedia.org/wiki/Olingo

On 18.06.13 15:58, "Dennis E. Hamilton" <de...@acm.org> wrote:

>I think there will be an issue with regard to trademarks and you will
>have to deal with folks seeing the trademark of "Apache OData" as a
>land-grab at "OData" itself.  The simplicity you think is avoiding
>confusion is, in that respect, causing confusion.
>
>In any case, it is always wise to avoid confusion of a (standard)
>specification, even OASIS Standard OData v3.0 or whatever, with the name
>of an implementation.  OASIS is going to make their own claims about some
>of those terms as well, if the past practice is any guide.
>
> - Dennis
>
>The ODF Toolkit snuck by, much to my dismay, even capturing odf as their
>incubator repository name, but they may have to deal with that to
>graduate to a TLP.
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Tuesday, June 18, 2013 06:27 AM
>To: general@incubator.apache.org
>Cc: dennis.hamilton@acm.org
>Subject: Re: [PROPOSAL] OData Proposal for Incubator
>
>Hello Dennis,
>
>Good point! The project naming was a challenge for us and maybe I just can
>explain why we prefer Apache OData as project name. The main reason is
>search. 
>
>Someone who is interested in OData will use this term and the result page
>will today list odata.org as the protocols homepage, Wikipedia which is
>fine and the OASIS TC. In future we would like to see that Apache OData is
>highly ranked and completes the search result list.
>
>If we use a different name someone has to know this name and has to search
>for it explicitly. We would like to keep it simple and avoid confusion.
>
>We had also a look into the ASF project naming guidelines and I think most
>of the points there are considered by the name Apache OData.
>
>
>Regards,
>Stephan
>
>On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:
>
>>I think one concern here is appropriation of a generic, specified-tied
>>name to an implementation, even a reference implementation.
>>
>>"Apache OData" seems over-reaching in that respect, especially since
>>there are other projects, at ASF and elsewhere, that may employ OData
>>bindings and services of one sort or another.
>[ ... ]
>


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

RE: [PROPOSAL] OData Proposal for Incubator

Posted by "Dennis E. Hamilton" <de...@acm.org>.
I think there will be an issue with regard to trademarks and you will have to deal with folks seeing the trademark of "Apache OData" as a land-grab at "OData" itself.  The simplicity you think is avoiding confusion is, in that respect, causing confusion.

In any case, it is always wise to avoid confusion of a (standard) specification, even OASIS Standard OData v3.0 or whatever, with the name of an implementation.  OASIS is going to make their own claims about some of those terms as well, if the past practice is any guide.

 - Dennis

The ODF Toolkit snuck by, much to my dismay, even capturing odf as their incubator repository name, but they may have to deal with that to graduate to a TLP.

-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com] 
Sent: Tuesday, June 18, 2013 06:27 AM
To: general@incubator.apache.org
Cc: dennis.hamilton@acm.org
Subject: Re: [PROPOSAL] OData Proposal for Incubator

Hello Dennis,

Good point! The project naming was a challenge for us and maybe I just can
explain why we prefer Apache OData as project name. The main reason is
search. 

Someone who is interested in OData will use this term and the result page
will today list odata.org as the protocols homepage, Wikipedia which is
fine and the OASIS TC. In future we would like to see that Apache OData is
highly ranked and completes the search result list.

If we use a different name someone has to know this name and has to search
for it explicitly. We would like to keep it simple and avoid confusion.

We had also a look into the ASF project naming guidelines and I think most
of the points there are considered by the name Apache OData.


Regards,
Stephan

On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:

>I think one concern here is appropriation of a generic, specified-tied
>name to an implementation, even a reference implementation.
>
>"Apache OData" seems over-reaching in that respect, especially since
>there are other projects, at ASF and elsewhere, that may employ OData
>bindings and services of one sort or another.
[ ... ]


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by David Nalley <da...@gnsa.us>.
Who owns the rights to the OData trademark? I am not sure that you or
the ASF has standing to use OData as a project name. That said we have
podling namesearch for a reason, to make sure that these types of
issues can be addressed by people qualified to make such judgements
(e.g. not me)

--David

On Tue, Jun 18, 2013 at 9:27 AM, Klevenz, Stephan
<st...@sap.com> wrote:
> Hello Dennis,
>
> Good point! The project naming was a challenge for us and maybe I just can
> explain why we prefer Apache OData as project name. The main reason is
> search.
>
> Someone who is interested in OData will use this term and the result page
> will today list odata.org as the protocols homepage, Wikipedia which is
> fine and the OASIS TC. In future we would like to see that Apache OData is
> highly ranked and completes the search result list.
>
> If we use a different name someone has to know this name and has to search
> for it explicitly. We would like to keep it simple and avoid confusion.
>
> We had also a look into the ASF project naming guidelines and I think most
> of the points there are considered by the name Apache OData.
>
>
> Regards,
> Stephan
>
> On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:
>
>>I think one concern here is appropriation of a generic, specified-tied
>>name to an implementation, even a reference implementation.
>>
>>"Apache OData" seems over-reaching in that respect, especially since
>>there are other projects, at ASF and elsewhere, that may employ OData
>>bindings and services of one sort or another.
>>
>>-----Original Message-----
>>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>>Sent: Monday, June 17, 2013 08:36 AM
>>To: general@incubator.apache.org
>>Subject: [PROPOSAL] OData Proposal for Incubator
>>
>>Dear ASF members,
>>
>>We would like to propose the OData project to the Incubator.
>>
>>The OData Proposal is available at:
>>https://wiki.apache.org/incubator/ODataProposal
>>
>>We welcome your feedback and suggestions.
>>
>>Thanks!
>>
>>Stephan Klevenz
>>
>>
>>[ ... ]
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Hello Dennis,

Good point! The project naming was a challenge for us and maybe I just can
explain why we prefer Apache OData as project name. The main reason is
search. 

Someone who is interested in OData will use this term and the result page
will today list odata.org as the protocols homepage, Wikipedia which is
fine and the OASIS TC. In future we would like to see that Apache OData is
highly ranked and completes the search result list.

If we use a different name someone has to know this name and has to search
for it explicitly. We would like to keep it simple and avoid confusion.

We had also a look into the ASF project naming guidelines and I think most
of the points there are considered by the name Apache OData.


Regards,
Stephan

On 18.06.13 03:28, "Dennis E. Hamilton" <de...@acm.org> wrote:

>I think one concern here is appropriation of a generic, specified-tied
>name to an implementation, even a reference implementation.
>
>"Apache OData" seems over-reaching in that respect, especially since
>there are other projects, at ASF and elsewhere, that may employ OData
>bindings and services of one sort or another.
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Monday, June 17, 2013 08:36 AM
>To: general@incubator.apache.org
>Subject: [PROPOSAL] OData Proposal for Incubator
>
>Dear ASF members,
>
>We would like to propose the OData project to the Incubator.
>
>The OData Proposal is available at:
>https://wiki.apache.org/incubator/ODataProposal
>
>We welcome your feedback and suggestions.
>
>Thanks!
>
>Stephan Klevenz
>
>
>[ ... ]
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


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

RE: [PROPOSAL] OData Proposal for Incubator

Posted by "Dennis E. Hamilton" <de...@acm.org>.
I think one concern here is appropriation of a generic, specified-tied name to an implementation, even a reference implementation.

"Apache OData" seems over-reaching in that respect, especially since there are other projects, at ASF and elsewhere, that may employ OData bindings and services of one sort or another.

-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com] 
Sent: Monday, June 17, 2013 08:36 AM
To: general@incubator.apache.org
Subject: [PROPOSAL] OData Proposal for Incubator

Dear ASF members,

We would like to propose the OData project to the Incubator.

The OData Proposal is available at: https://wiki.apache.org/incubator/ODataProposal

We welcome your feedback and suggestions.

Thanks!

Stephan Klevenz


[ ... ]



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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Francesco Chicchiriccò <il...@apache.org>.
On 19/06/2013 14:00, Klevenz, Stephan wrote:
> Francesco,
>
>
> We are welcome you to be a initial committer. Can you please add yourself
> to the initial committer list in our proposal?
>
> https://wiki.apache.org/incubator/ODataProposal

Done.
Regards.

> Francesco did already some contributions to the project which is currently
> on GitHub.
>
> Regards,
> Stephan
>
> On 19.06.13 10:01, "Francesco Chicchiriccò" <il...@apache.org> wrote:
>
>> Klevenz, Stephan wrote:
>>> Dear ASF members,
>>>
>>> We would like to propose the OData project to the Incubator.
>>>
>>> The OData Proposal is available at:
>>> https://wiki.apache.org/incubator/ODataProposal
>>>
>>> We welcome your feedback and suggestions.
>>>
>> Hi Stephan,
>> this proposal looks very interesting to me: if you need people, I would
>> like
>> to join the project.
>>
>> Regards.

-- 
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/


-- 
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Francesco,


We are welcome you to be a initial committer. Can you please add yourself
to the initial committer list in our proposal?

https://wiki.apache.org/incubator/ODataProposal


Francesco did already some contributions to the project which is currently
on GitHub.

Regards,
Stephan

On 19.06.13 10:01, "Francesco Chicchiriccò" <il...@apache.org> wrote:

>
>
>Klevenz, Stephan wrote:
>> 
>> Dear ASF members,
>> 
>> We would like to propose the OData project to the Incubator.
>> 
>> The OData Proposal is available at:
>> https://wiki.apache.org/incubator/ODataProposal
>> 
>> We welcome your feedback and suggestions.
>> 
>
>Hi Stephan,
>this proposal looks very interesting to me: if you need people, I would
>like
>to join the project.
>
>Regards.
>-- 
>View this message in context:
>http://old.nabble.com/-PROPOSAL--OData-Proposal-for-Incubator-tp35634730p3
>5642221.html
>Sent from the Apache Incubator - General mailing list archive at
>Nabble.com.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Francesco Chicchiriccò <il...@apache.org>.

Klevenz, Stephan wrote:
> 
> Dear ASF members,
> 
> We would like to propose the OData project to the Incubator.
> 
> The OData Proposal is available at:
> https://wiki.apache.org/incubator/ODataProposal
> 
> We welcome your feedback and suggestions.
> 

Hi Stephan,
this proposal looks very interesting to me: if you need people, I would like
to join the project.

Regards.
-- 
View this message in context: http://old.nabble.com/-PROPOSAL--OData-Proposal-for-Incubator-tp35634730p35642221.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Sergio Fernández <se...@salzburgresearch.at>.
Hi,

as part of the marmotta PPMC, I think I could put my two cents in this 
discussion :-)

On 18/06/13 13:17, Klevenz, Stephan wrote:
> Thanks for your hint. I do understand Marmotta as an implementation of the
> Linked Data Platform (LDP). Linked Data is a concept for building a
> semantic web where things are identified by URIs. Links can be used to
> explore things.

URIs identify things in the Web of Data, and links are the relationships 
between those things, right, that's Linked Data basically. And LDP just 
comes to build something on top of such «basic» infrastructure.

> OData is a data centric protocol which describes metadata and allows data
> queries. It can be seen as the SQL for the web.

A query language for the Web among the other proposals out there. But, 
yes, the definitions helps.

I was following a bit OData when started at Oasis, but I should admit I 
don't know what's actually going there in the last few years.

> Although LDP and OData make use of REST principles both do address
> different uses cases. I don't see overlap here.

As I said in dev@marmotta: http://markmail.org/message/v7qcapwtrmte6el4
even if both project share paradigms (REST) and partially some goals 
(publish Open Data), I don't see such overlap. Even I'd say, having more 
data-oriented projects in the ASF is good in many aspects.

Cheers,


> On 17.06.13 18:59, "Rob Vesse" <rv...@yarcdata.com> wrote:
>
>> Stephan
>>
>> What overlap (if any) do you see with the existing Marmotta podling?
>>
>> They are building out an implementation of the Linked Data Platform which
>> is a ongoing W3C standardization effort
>> (http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a
>> more RDF/Semantic Web centric alternative to the MS/Oasis OData standard.
>>
>> Rob
>>
>>
>> On 6/17/13 8:35 AM, "Klevenz, Stephan" <st...@sap.com> wrote:
>>
>>> Dear ASF members,
>>>
>>> We would like to propose the OData project to the Incubator.
>>>
>>> The OData Proposal is available at:
>>> https://wiki.apache.org/incubator/ODataProposal
>>>
>>> We welcome your feedback and suggestions.
>>>
>>> Thanks!
>>>
>>> Stephan Klevenz
>>>
>>>
>>>
>>> = Apache OData =
>>>
>>> === Abstract ===
>>>
>>> Apache OData is a generic Java language implementation of the OData 2.0
>>> specification which will serve as a code base for the upcoming OASIS
>>> OData specification.
>>>
>>> === Proposal ===
>>>
>>> The Open Data Protocol (OData) [1] is a Web protocol for querying and
>>> updating data that provides a way to unlock your data and free it from
>>> silos that exist in applications today. OData does this by applying and
>>> building upon Web technologies such as HTTP, Atom Publishing Protocol
>>> (AtomPub) and JSON to provide access to information from a variety of
>>> applications, services, and stores.
>>>
>>> The Apache OData is a library which enables developers to implement OData
>>> producers and OData consumers. Basic principles of the library are to
>>> provide an OData 2.0 specification compliant OData Library, enhancements
>>> shall be possible in a compatible manner, have a clear separation between
>>> Core and API, to provide an option to build extensions on top. This
>>> library should be base for implementing future releases of the
>>> specification.
>>>
>>> === Background ===
>>>
>>> OData was originally developed by Microsoft and is released in a version
>>> 2.0 under an Open Specification Promise [2]. A lot of companies did show
>>> interests in this protocol, used it in products and gave feedback back to
>>> Microsoft. This joined effort resulted in a new release OData 3.0 in
>>> 2012, this version became the basis for the OASIS technical committee [3]
>>> which is currently working on a new version of the specification. This
>>> OASIS standard release is expected this year.
>>>
>>> The initial Java code of this project was developed by a development team
>>> that had already experience with other OData 2.0 and 3.0 implementations
>>> at SAP AG. The current code base implements OData 2.0 and because of this
>>> version is widely used it is a good starting point to build an open
>>> source community for the OData standard.
>>>
>>> The current code also comes up with an implementation of an OData sample
>>> service. On the one side this is an example for users which want to use
>>> the library to expose their own data and on the other side it illustrates
>>> how implemented features work.
>>>
>>> Additionally, the code base includes an extension which is called JPA
>>> processor. With this extension it is easy to expose any JPA persistence
>>> model via OData protocol without a lot of coding.
>>>
>>> === Rationale ===
>>>
>>> More software vendors moving to OData means more choice for customers who
>>> will be able to use different implementations. For the standard to
>>> succeed, however, ensuring interoperability is paramount: in order to
>>> manage an ever growing context and leverage the enormous portability and
>>> interoperability issues that a globally adopted standard brings, it is
>>> necessary to think about how to make the related ecosystem healthy and
>>> sustainable. Successful modern standards are driven by:
>>>
>>> * Clear documentation, built iteratively with continuous feedback from
>>> stakeholders
>>> * A clearly defined compatibility process, enforced by tools that allow
>>> to gauge how implementations can be compatible and interoperable
>>> * Accurate compliance criteria, documented in writing as well as in
>>> actual testing code that measure how tools and libraries are able to
>>> interoperate
>>> * A sample implementation to clear up potential doubts and ensure that
>>> the standard can actually be implemented in real life scenarios
>>>
>>> The above mentioned pieces are able to make the development activity,
>>> towards an OData implementation, easier and more successful. Having an
>>> healthy ecosystem will ensure a smoother implementation process, more
>>> compliant products, and ultimately, a wider adoption of the standard.
>>>
>>> The OData ecosystem has been successful in creating and documenting early
>>> versions of the standard, yet it might potentially lack two very
>>> important aspects, that is a exhaustive implementation of the complete
>>> protocol that can be used productively and to ensure interoperability. As
>>> much as such artifacts can be developed independently by any OData
>>> proponent, the value of having a neutral party as a steward of actual
>>> code is to be considered. The Apache Software Foundation has been playing
>>> this kind of role for many years, and can provide the perfect environment
>>> to foster contributions on the OData theme with a great amount of
>>> expertise.
>>>
>>> === Initial Goals ===
>>>
>>> * Implement OData 2.0, make it final and mature
>>> * Start implementation of OASIS OData draft specification
>>> * Provide input and feedback for the draft specification to the OASIS
>>> OData TC based on implementation
>>> * Implement OData add-ons (library extensions and toolset)
>>>
>>> == Current Status ==
>>>
>>> === Meritocracy ===
>>>
>>> Most of the initial committers are open source developers with different
>>> experience levels and many of them have already worked in other open
>>> source or Apache projects. We will follow standard Apache procedures in
>>> accepting new contributors to the project team.
>>>
>>> === Community ===
>>>
>>> Managed by an OASIS Technical Committee, the OData standard definition
>>> should be based on the idea of a community driven effort.
>>>
>>> Apache OData aims to be a community driven initiative in developing a
>>> Java OData implementation. Such an approach is allowing more transparency
>>> and direct feedback even within the definition and improvement of OData
>>> specifications.
>>>
>>> We encourage everyone interested in OData to join the Apache OData
>>> effort.
>>>
>>> === Core Developers ===
>>>
>>> The development team is international and they have all strong skills in
>>> OData protocol. Jens Huesken who is member of the OASIS OData TC is
>>> providing specification feedback since OData 2.0. Stephan Klevenz, also a
>>> OASIS OData TC member, was a committer of the Apache Chemistry project.
>>> He has experience with the Incubator and Apache and was also a speaker on
>>> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>> Boehm did implement core parts of the library. Chandan V A, Anirban Roy,
>>> Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA
>>> processor add on.
>>>
>>> === Alignment ===
>>>
>>> The project builds with Apache Maven, the core runtime requires Apache
>>> CXF for REST binding (JAX-RS) and the sample scenario can be deployed
>>> into any compliant Servlet or J2EE container like Apache Tomcat.
>>> Furthermore we see OData protocol as an option to be supported by other
>>> Apache projects that have to expose data via a standardized protocol
>>> based interface.
>>>
>>> == Known Risks ==
>>>
>>> === Orphaned products ===
>>>
>>> Apache OData is a fresh new codebase that targets the still moving OData
>>> standardization effort. Thus the future of this project depends heavily
>>> on the success of the standard. We hope and expect that our
>>> implementation efforts will strengthen and support the OData standard.
>>>
>>> === Inexperience with Open Source ===
>>>
>>> Some of the initial committers are experienced open source developers.
>>> But there are also committers which are new to open source.
>>>
>>> === Homogenous Developers ===
>>>
>>> The initial committers are from SAP working in different teams. One team
>>> is from Germany and has implemented the core parts of the library and the
>>> other team is from India and has implemented the JPA processor add-on.
>>>
>>> === Reliance of Salaried Developers ===
>>>
>>> All of the initial committers are paid by SAP to work on this or related
>>> projects.
>>>
>>> === Relationships with Other Apache Products ===
>>>
>>> Apache OData will directly use at least the following projects:
>>>
>>> * Apache CXF - for REST bindings
>>> * Apache Commons - for encoding/decoding
>>>
>>> Other Apache projects may be interested in using Apache OData to add
>>> OData support once the standard is final.
>>>
>>> === An Excessive Fascination with the Apache Brand ===
>>>
>>> We value Apache as a neutral place where diverse communities can work
>>> together on implementing shared standards. We hope that this part of the
>>> Apache brand helps attract contributions from many potential OData
>>> standard consumers. However, the brand value is not the main reason why
>>> we prefer to have this project at Apache.
>>>
>>> == Documentation ==
>>>
>>> This project is still at an early stage, so there is not much
>>> documentation available. See the OASIS OData page and odata.org web site
>>> for information about the OData standardization effort.
>>>
>>> == Initial Source ==
>>>
>>> * [[https://github.com/SAP/cloud-odata-java]]
>>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>>>
>>> == Source and Intellectual Property Submission Plan ==
>>>
>>> The complete code is under Apache Software License 2.
>>>
>>> == External Dependencies ==
>>>
>>> All the external dependencies of the initial codebases comply with Apache
>>> licensing policies.
>>>
>>> == Cryptography ==
>>>
>>> Apache OData is not expected to implement or use cryptographic code.
>>>
>>> == Required Resources ==
>>>
>>> === Mailing lists ===
>>>
>>> * odata-dev'at'incubator.apache.org
>>> * odata-commits'at'incubator.apache.org
>>> * odata-private'at'incubator.apache.org
>>>
>>> === Subversion Directory ===
>>>
>>> writeable Git Repository (preferred)
>>>
>>>     [[git://git.apache.org/odata.git]]
>>>
>>> or SVN Directory
>>>
>>>     [[https://svn.apache.org/repos/asf/incubator/odata]]
>>>
>>> === Issue Tracking ===
>>>
>>>     JIRA OData (OData)
>>>
>>> === Other Resources ===
>>>
>>>     none
>>>
>>> == Initial Committers ==
>>>
>>> || '''Name'''       || '''Email'''                 ||
>>> || Stephan Klevenz  || sklevenz'at'apache.org      ||
>>> || Jens Huesken     || jens.huesken'at'sap.com     ||
>>> || Christian Amend  || christian.amend'at'sap.com  ||
>>> || Michael Bolz     || michael.bolz'at'sap.com     ||
>>> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
>>> || Chandan V A      || chandan.v.a'at'sap.com      ||
>>> || Anirban Roy      || anirban.roy'at'sap.com      ||
>>> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>>> || Jobin John       || jobin.john'at'sap.com       ||
>>> || Joerg Singler    || joerg.singler'at'sap.com    ||
>>>
>>> == Affiliations ==
>>>
>>> || '''Name'''          || '''Affilitation''' ||
>>> || Stephan Klevenz     || SAP AG       ||
>>> || Jens Huesken        || SAP AG       ||
>>> || Christian Amend     || SAP AG       ||
>>> || Michael Bolz        || SAP AG       ||
>>> || Tamara Boehm        || SAP AG       ||
>>> || Chandan V A         || SAP AG       ||
>>> || Anirban Roy         || SAP AG       ||
>>> || Chitresh Chauhan    || SAP AG       ||
>>> || Jobin John          || SAP AG       ||
>>> || Joerg Singler       || SAP AG       ||
>>>
>>> == Sponsors ==
>>>
>>> Champion
>>>
>>> * Florian Mueller
>>>
>>> Nominated Mentors
>>>
>>> * Florian Mueller
>>> * tbd.
>>>
>>> Sponsoring Entiy
>>>
>>> * Incubator PMC
>>>
>>> ==== Links ====
>>>
>>> * [1] [[http://www.odata.org]]
>>> * [2]
>>> [[http://www.microsoft.com/openspecifications/en/us/programs/osp/default.
>>> a
>>> spx]]
>>> * [3]
>>> [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
>>> * [4]
>>> [[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

-- 
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at

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

Re: FW: [PROPOSAL] OData Proposal for Incubator

Posted by Sergio Fernández <wi...@apache.org>.
Hi Rob,

I saw the thread at general@incubator.a.o, but I was not able to find 
time for properly go into it.

AFAIK about OData from OASIS, definitely there is not such overlap. Even 
if both technologies are based on the base paradigm (REST) and they 
could be used to address the same goal (publish Open Data), the 
fundamentals are very different.

Even though, from both projects could try to find synergies within ASF, 
in events or whatever, which would be really cool.

Thanks for triggering the discussion here. I'd try to join the main 
thread to asset these arguments there too.

Cheers,


On 18/06/13 18:43, Rob Vesse wrote:
> Hi All
>
> Not sure if anyone here subscribes to general@i.a.o so thought you might
> like to be aware that the following has recently been proposed.
>
> I already raised the question of possible overlap with Marmotta though
> their devs don't necessarily see any, just making you guys aware in case
> anyone wants to weigh in on this.
>
> Rob
>
>
> On 6/18/13 4:17 AM, "Klevenz, Stephan" <st...@sap.com> wrote:
>
>> Rob,
>>
>> Thanks for your hint. I do understand Marmotta as an implementation of the
>> Linked Data Platform (LDP). Linked Data is a concept for building a
>> semantic web where things are identified by URIs. Links can be used to
>> explore things.
>>
>> OData is a data centric protocol which describes metadata and allows data
>> queries. It can be seen as the SQL for the web. One main use case is to
>> open data silos to be accessible over the web. Apache OData is a
>> implementation of the OData protocol.
>>
>> Although LDP and OData make use of REST principles both do address
>> different uses cases. I don't see overlap here.
>>
>>
>> Regards,
>> Stephan
>>
>>
>>
>>
>>
>> On 17.06.13 18:59, "Rob Vesse" <rv...@yarcdata.com> wrote:
>>
>>> Stephan
>>>
>>> What overlap (if any) do you see with the existing Marmotta podling?
>>>
>>> They are building out an implementation of the Linked Data Platform which
>>> is a ongoing W3C standardization effort
>>> (http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a
>>> more RDF/Semantic Web centric alternative to the MS/Oasis OData standard.
>>>
>>> Rob
>>>
>>>
>>> On 6/17/13 8:35 AM, "Klevenz, Stephan" <st...@sap.com> wrote:
>>>
>>>> Dear ASF members,
>>>>
>>>> We would like to propose the OData project to the Incubator.
>>>>
>>>> The OData Proposal is available at:
>>>> https://wiki.apache.org/incubator/ODataProposal
>>>>
>>>> We welcome your feedback and suggestions.
>>>>
>>>> Thanks!
>>>>
>>>> Stephan Klevenz
>>>>
>>>>
>>>>
>>>> = Apache OData =
>>>>
>>>> === Abstract ===
>>>>
>>>> Apache OData is a generic Java language implementation of the OData 2.0
>>>> specification which will serve as a code base for the upcoming OASIS
>>>> OData specification.
>>>>
>>>> === Proposal ===
>>>>
>>>> The Open Data Protocol (OData) [1] is a Web protocol for querying and
>>>> updating data that provides a way to unlock your data and free it from
>>>> silos that exist in applications today. OData does this by applying and
>>>> building upon Web technologies such as HTTP, Atom Publishing Protocol
>>>> (AtomPub) and JSON to provide access to information from a variety of
>>>> applications, services, and stores.
>>>>
>>>> The Apache OData is a library which enables developers to implement
>>>> OData
>>>> producers and OData consumers. Basic principles of the library are to
>>>> provide an OData 2.0 specification compliant OData Library, enhancements
>>>> shall be possible in a compatible manner, have a clear separation
>>>> between
>>>> Core and API, to provide an option to build extensions on top. This
>>>> library should be base for implementing future releases of the
>>>> specification.
>>>>
>>>> === Background ===
>>>>
>>>> OData was originally developed by Microsoft and is released in a version
>>>> 2.0 under an Open Specification Promise [2]. A lot of companies did show
>>>> interests in this protocol, used it in products and gave feedback back
>>>> to
>>>> Microsoft. This joined effort resulted in a new release OData 3.0 in
>>>> 2012, this version became the basis for the OASIS technical committee
>>>> [3]
>>>> which is currently working on a new version of the specification. This
>>>> OASIS standard release is expected this year.
>>>>
>>>> The initial Java code of this project was developed by a development
>>>> team
>>>> that had already experience with other OData 2.0 and 3.0 implementations
>>>> at SAP AG. The current code base implements OData 2.0 and because of
>>>> this
>>>> version is widely used it is a good starting point to build an open
>>>> source community for the OData standard.
>>>>
>>>> The current code also comes up with an implementation of an OData sample
>>>> service. On the one side this is an example for users which want to use
>>>> the library to expose their own data and on the other side it
>>>> illustrates
>>>> how implemented features work.
>>>>
>>>> Additionally, the code base includes an extension which is called JPA
>>>> processor. With this extension it is easy to expose any JPA persistence
>>>> model via OData protocol without a lot of coding.
>>>>
>>>> === Rationale ===
>>>>
>>>> More software vendors moving to OData means more choice for customers
>>>> who
>>>> will be able to use different implementations. For the standard to
>>>> succeed, however, ensuring interoperability is paramount: in order to
>>>> manage an ever growing context and leverage the enormous portability and
>>>> interoperability issues that a globally adopted standard brings, it is
>>>> necessary to think about how to make the related ecosystem healthy and
>>>> sustainable. Successful modern standards are driven by:
>>>>
>>>> * Clear documentation, built iteratively with continuous feedback from
>>>> stakeholders
>>>> * A clearly defined compatibility process, enforced by tools that allow
>>>> to gauge how implementations can be compatible and interoperable
>>>> * Accurate compliance criteria, documented in writing as well as in
>>>> actual testing code that measure how tools and libraries are able to
>>>> interoperate
>>>> * A sample implementation to clear up potential doubts and ensure that
>>>> the standard can actually be implemented in real life scenarios
>>>>
>>>> The above mentioned pieces are able to make the development activity,
>>>> towards an OData implementation, easier and more successful. Having an
>>>> healthy ecosystem will ensure a smoother implementation process, more
>>>> compliant products, and ultimately, a wider adoption of the standard.
>>>>
>>>> The OData ecosystem has been successful in creating and documenting
>>>> early
>>>> versions of the standard, yet it might potentially lack two very
>>>> important aspects, that is a exhaustive implementation of the complete
>>>> protocol that can be used productively and to ensure interoperability.
>>>> As
>>>> much as such artifacts can be developed independently by any OData
>>>> proponent, the value of having a neutral party as a steward of actual
>>>> code is to be considered. The Apache Software Foundation has been
>>>> playing
>>>> this kind of role for many years, and can provide the perfect
>>>> environment
>>>> to foster contributions on the OData theme with a great amount of
>>>> expertise.
>>>>
>>>> === Initial Goals ===
>>>>
>>>> * Implement OData 2.0, make it final and mature
>>>> * Start implementation of OASIS OData draft specification
>>>> * Provide input and feedback for the draft specification to the OASIS
>>>> OData TC based on implementation
>>>> * Implement OData add-ons (library extensions and toolset)
>>>>
>>>> == Current Status ==
>>>>
>>>> === Meritocracy ===
>>>>
>>>> Most of the initial committers are open source developers with different
>>>> experience levels and many of them have already worked in other open
>>>> source or Apache projects. We will follow standard Apache procedures in
>>>> accepting new contributors to the project team.
>>>>
>>>> === Community ===
>>>>
>>>> Managed by an OASIS Technical Committee, the OData standard definition
>>>> should be based on the idea of a community driven effort.
>>>>
>>>> Apache OData aims to be a community driven initiative in developing a
>>>> Java OData implementation. Such an approach is allowing more
>>>> transparency
>>>> and direct feedback even within the definition and improvement of OData
>>>> specifications.
>>>>
>>>> We encourage everyone interested in OData to join the Apache OData
>>>> effort.
>>>>
>>>> === Core Developers ===
>>>>
>>>> The development team is international and they have all strong skills in
>>>> OData protocol. Jens Huesken who is member of the OASIS OData TC is
>>>> providing specification feedback since OData 2.0. Stephan Klevenz, also
>>>> a
>>>> OASIS OData TC member, was a committer of the Apache Chemistry project.
>>>> He has experience with the Incubator and Apache and was also a speaker
>>>> on
>>>> ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>>> Boehm did implement core parts of the library. Chandan V A, Anirban Roy,
>>>> Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA
>>>> processor add on.
>>>>
>>>> === Alignment ===
>>>>
>>>> The project builds with Apache Maven, the core runtime requires Apache
>>>> CXF for REST binding (JAX-RS) and the sample scenario can be deployed
>>>> into any compliant Servlet or J2EE container like Apache Tomcat.
>>>> Furthermore we see OData protocol as an option to be supported by other
>>>> Apache projects that have to expose data via a standardized protocol
>>>> based interface.
>>>>
>>>> == Known Risks ==
>>>>
>>>> === Orphaned products ===
>>>>
>>>> Apache OData is a fresh new codebase that targets the still moving OData
>>>> standardization effort. Thus the future of this project depends heavily
>>>> on the success of the standard. We hope and expect that our
>>>> implementation efforts will strengthen and support the OData standard.
>>>>
>>>> === Inexperience with Open Source ===
>>>>
>>>> Some of the initial committers are experienced open source developers.
>>>> But there are also committers which are new to open source.
>>>>
>>>> === Homogenous Developers ===
>>>>
>>>> The initial committers are from SAP working in different teams. One team
>>>> is from Germany and has implemented the core parts of the library and
>>>> the
>>>> other team is from India and has implemented the JPA processor add-on.
>>>>
>>>> === Reliance of Salaried Developers ===
>>>>
>>>> All of the initial committers are paid by SAP to work on this or related
>>>> projects.
>>>>
>>>> === Relationships with Other Apache Products ===
>>>>
>>>> Apache OData will directly use at least the following projects:
>>>>
>>>> * Apache CXF - for REST bindings
>>>> * Apache Commons - for encoding/decoding
>>>>
>>>> Other Apache projects may be interested in using Apache OData to add
>>>> OData support once the standard is final.
>>>>
>>>> === An Excessive Fascination with the Apache Brand ===
>>>>
>>>> We value Apache as a neutral place where diverse communities can work
>>>> together on implementing shared standards. We hope that this part of the
>>>> Apache brand helps attract contributions from many potential OData
>>>> standard consumers. However, the brand value is not the main reason why
>>>> we prefer to have this project at Apache.
>>>>
>>>> == Documentation ==
>>>>
>>>> This project is still at an early stage, so there is not much
>>>> documentation available. See the OASIS OData page and odata.org web site
>>>> for information about the OData standardization effort.
>>>>
>>>> == Initial Source ==
>>>>
>>>> * [[https://github.com/SAP/cloud-odata-java]]
>>>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>>>>
>>>> == Source and Intellectual Property Submission Plan ==
>>>>
>>>> The complete code is under Apache Software License 2.
>>>>
>>>> == External Dependencies ==
>>>>
>>>> All the external dependencies of the initial codebases comply with
>>>> Apache
>>>> licensing policies.
>>>>
>>>> == Cryptography ==
>>>>
>>>> Apache OData is not expected to implement or use cryptographic code.
>>>>
>>>> == Required Resources ==
>>>>
>>>> === Mailing lists ===
>>>>
>>>> * odata-dev'at'incubator.apache.org
>>>> * odata-commits'at'incubator.apache.org
>>>> * odata-private'at'incubator.apache.org
>>>>
>>>> === Subversion Directory ===
>>>>
>>>> writeable Git Repository (preferred)
>>>>
>>>>     [[git://git.apache.org/odata.git]]
>>>>
>>>> or SVN Directory
>>>>
>>>>     [[https://svn.apache.org/repos/asf/incubator/odata]]
>>>>
>>>> === Issue Tracking ===
>>>>
>>>>     JIRA OData (OData)
>>>>
>>>> === Other Resources ===
>>>>
>>>>     none
>>>>
>>>> == Initial Committers ==
>>>>
>>>> || '''Name'''       || '''Email'''                 ||
>>>> || Stephan Klevenz  || sklevenz'at'apache.org      ||
>>>> || Jens Huesken     || jens.huesken'at'sap.com     ||
>>>> || Christian Amend  || christian.amend'at'sap.com  ||
>>>> || Michael Bolz     || michael.bolz'at'sap.com     ||
>>>> || Tamara Boehm     || tamara.boehm'at'sap.com     ||
>>>> || Chandan V A      || chandan.v.a'at'sap.com      ||
>>>> || Anirban Roy      || anirban.roy'at'sap.com      ||
>>>> || Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>>>> || Jobin John       || jobin.john'at'sap.com       ||
>>>> || Joerg Singler    || joerg.singler'at'sap.com    ||
>>>>
>>>> == Affiliations ==
>>>>
>>>> || '''Name'''          || '''Affilitation''' ||
>>>> || Stephan Klevenz     || SAP AG       ||
>>>> || Jens Huesken        || SAP AG       ||
>>>> || Christian Amend     || SAP AG       ||
>>>> || Michael Bolz        || SAP AG       ||
>>>> || Tamara Boehm        || SAP AG       ||
>>>> || Chandan V A         || SAP AG       ||
>>>> || Anirban Roy         || SAP AG       ||
>>>> || Chitresh Chauhan    || SAP AG       ||
>>>> || Jobin John          || SAP AG       ||
>>>> || Joerg Singler       || SAP AG       ||
>>>>
>>>> == Sponsors ==
>>>>
>>>> Champion
>>>>
>>>> * Florian Mueller
>>>>
>>>> Nominated Mentors
>>>>
>>>> * Florian Mueller
>>>> * tbd.
>>>>
>>>> Sponsoring Entiy
>>>>
>>>> * Incubator PMC
>>>>
>>>> ==== Links ====
>>>>
>>>> * [1] [[http://www.odata.org]]
>>>> * [2]
>>>> [[http://www.microsoft.com/openspecifications/en/us/programs/osp/default
>>>> .
>>>> a
>>>> spx]]
>>>> * [3]
>>>> [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
>>>> * [4]
>>>> [[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>

-- 
Sergio Fernández

FW: [PROPOSAL] OData Proposal for Incubator

Posted by Rob Vesse <rv...@yarcdata.com>.
Hi All

Not sure if anyone here subscribes to general@i.a.o so thought you might
like to be aware that the following has recently been proposed.

I already raised the question of possible overlap with Marmotta though
their devs don't necessarily see any, just making you guys aware in case
anyone wants to weigh in on this.

Rob


On 6/18/13 4:17 AM, "Klevenz, Stephan" <st...@sap.com> wrote:

>Rob,
>
>Thanks for your hint. I do understand Marmotta as an implementation of the
>Linked Data Platform (LDP). Linked Data is a concept for building a
>semantic web where things are identified by URIs. Links can be used to
>explore things.
>
>OData is a data centric protocol which describes metadata and allows data
>queries. It can be seen as the SQL for the web. One main use case is to
>open data silos to be accessible over the web. Apache OData is a
>implementation of the OData protocol.
>
>Although LDP and OData make use of REST principles both do address
>different uses cases. I don't see overlap here.
>
>
>Regards,
>Stephan
>
>
>
>
>
>On 17.06.13 18:59, "Rob Vesse" <rv...@yarcdata.com> wrote:
>
>>Stephan
>>
>>What overlap (if any) do you see with the existing Marmotta podling?
>>
>>They are building out an implementation of the Linked Data Platform which
>>is a ongoing W3C standardization effort
>>(http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a
>>more RDF/Semantic Web centric alternative to the MS/Oasis OData standard.
>>
>>Rob
>>
>>
>>On 6/17/13 8:35 AM, "Klevenz, Stephan" <st...@sap.com> wrote:
>>
>>>Dear ASF members,
>>>
>>>We would like to propose the OData project to the Incubator.
>>>
>>>The OData Proposal is available at:
>>>https://wiki.apache.org/incubator/ODataProposal
>>>
>>>We welcome your feedback and suggestions.
>>>
>>>Thanks!
>>>
>>>Stephan Klevenz
>>>
>>>
>>>
>>>= Apache OData =
>>>
>>>=== Abstract ===
>>>
>>>Apache OData is a generic Java language implementation of the OData 2.0
>>>specification which will serve as a code base for the upcoming OASIS
>>>OData specification.
>>>
>>>=== Proposal ===
>>>
>>>The Open Data Protocol (OData) [1] is a Web protocol for querying and
>>>updating data that provides a way to unlock your data and free it from
>>>silos that exist in applications today. OData does this by applying and
>>>building upon Web technologies such as HTTP, Atom Publishing Protocol
>>>(AtomPub) and JSON to provide access to information from a variety of
>>>applications, services, and stores.
>>>
>>>The Apache OData is a library which enables developers to implement
>>>OData
>>>producers and OData consumers. Basic principles of the library are to
>>>provide an OData 2.0 specification compliant OData Library, enhancements
>>>shall be possible in a compatible manner, have a clear separation
>>>between
>>>Core and API, to provide an option to build extensions on top. This
>>>library should be base for implementing future releases of the
>>>specification.
>>>
>>>=== Background ===
>>>
>>>OData was originally developed by Microsoft and is released in a version
>>>2.0 under an Open Specification Promise [2]. A lot of companies did show
>>>interests in this protocol, used it in products and gave feedback back
>>>to
>>>Microsoft. This joined effort resulted in a new release OData 3.0 in
>>>2012, this version became the basis for the OASIS technical committee
>>>[3]
>>>which is currently working on a new version of the specification. This
>>>OASIS standard release is expected this year.
>>>
>>>The initial Java code of this project was developed by a development
>>>team
>>>that had already experience with other OData 2.0 and 3.0 implementations
>>>at SAP AG. The current code base implements OData 2.0 and because of
>>>this
>>>version is widely used it is a good starting point to build an open
>>>source community for the OData standard.
>>>
>>>The current code also comes up with an implementation of an OData sample
>>>service. On the one side this is an example for users which want to use
>>>the library to expose their own data and on the other side it
>>>illustrates
>>>how implemented features work.
>>>
>>>Additionally, the code base includes an extension which is called JPA
>>>processor. With this extension it is easy to expose any JPA persistence
>>>model via OData protocol without a lot of coding.
>>>
>>>=== Rationale ===
>>>
>>>More software vendors moving to OData means more choice for customers
>>>who
>>>will be able to use different implementations. For the standard to
>>>succeed, however, ensuring interoperability is paramount: in order to
>>>manage an ever growing context and leverage the enormous portability and
>>>interoperability issues that a globally adopted standard brings, it is
>>>necessary to think about how to make the related ecosystem healthy and
>>>sustainable. Successful modern standards are driven by:
>>>
>>> * Clear documentation, built iteratively with continuous feedback from
>>>stakeholders
>>> * A clearly defined compatibility process, enforced by tools that allow
>>>to gauge how implementations can be compatible and interoperable
>>> * Accurate compliance criteria, documented in writing as well as in
>>>actual testing code that measure how tools and libraries are able to
>>>interoperate
>>> * A sample implementation to clear up potential doubts and ensure that
>>>the standard can actually be implemented in real life scenarios
>>>
>>>The above mentioned pieces are able to make the development activity,
>>>towards an OData implementation, easier and more successful. Having an
>>>healthy ecosystem will ensure a smoother implementation process, more
>>>compliant products, and ultimately, a wider adoption of the standard.
>>>
>>>The OData ecosystem has been successful in creating and documenting
>>>early
>>>versions of the standard, yet it might potentially lack two very
>>>important aspects, that is a exhaustive implementation of the complete
>>>protocol that can be used productively and to ensure interoperability.
>>>As
>>>much as such artifacts can be developed independently by any OData
>>>proponent, the value of having a neutral party as a steward of actual
>>>code is to be considered. The Apache Software Foundation has been
>>>playing
>>>this kind of role for many years, and can provide the perfect
>>>environment
>>>to foster contributions on the OData theme with a great amount of
>>>expertise.
>>>
>>>=== Initial Goals ===
>>>
>>> * Implement OData 2.0, make it final and mature
>>> * Start implementation of OASIS OData draft specification
>>> * Provide input and feedback for the draft specification to the OASIS
>>>OData TC based on implementation
>>> * Implement OData add-ons (library extensions and toolset)
>>>
>>>== Current Status ==
>>>
>>>=== Meritocracy ===
>>>
>>>Most of the initial committers are open source developers with different
>>>experience levels and many of them have already worked in other open
>>>source or Apache projects. We will follow standard Apache procedures in
>>>accepting new contributors to the project team.
>>>
>>>=== Community ===
>>>
>>>Managed by an OASIS Technical Committee, the OData standard definition
>>>should be based on the idea of a community driven effort.
>>>
>>>Apache OData aims to be a community driven initiative in developing a
>>>Java OData implementation. Such an approach is allowing more
>>>transparency
>>>and direct feedback even within the definition and improvement of OData
>>>specifications.
>>>
>>>We encourage everyone interested in OData to join the Apache OData
>>>effort.
>>>
>>>=== Core Developers ===
>>>
>>>The development team is international and they have all strong skills in
>>>OData protocol. Jens Huesken who is member of the OASIS OData TC is
>>>providing specification feedback since OData 2.0. Stephan Klevenz, also
>>>a
>>>OASIS OData TC member, was a committer of the Apache Chemistry project.
>>>He has experience with the Incubator and Apache and was also a speaker
>>>on
>>>ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>>Boehm did implement core parts of the library. Chandan V A, Anirban Roy,
>>>Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA
>>>processor add on.
>>>
>>>=== Alignment ===
>>>
>>>The project builds with Apache Maven, the core runtime requires Apache
>>>CXF for REST binding (JAX-RS) and the sample scenario can be deployed
>>>into any compliant Servlet or J2EE container like Apache Tomcat.
>>>Furthermore we see OData protocol as an option to be supported by other
>>>Apache projects that have to expose data via a standardized protocol
>>>based interface.
>>>
>>>== Known Risks ==
>>>
>>>=== Orphaned products ===
>>>
>>>Apache OData is a fresh new codebase that targets the still moving OData
>>>standardization effort. Thus the future of this project depends heavily
>>>on the success of the standard. We hope and expect that our
>>>implementation efforts will strengthen and support the OData standard.
>>>
>>>=== Inexperience with Open Source ===
>>>
>>>Some of the initial committers are experienced open source developers.
>>>But there are also committers which are new to open source.
>>>
>>>=== Homogenous Developers ===
>>>
>>>The initial committers are from SAP working in different teams. One team
>>>is from Germany and has implemented the core parts of the library and
>>>the
>>>other team is from India and has implemented the JPA processor add-on.
>>>
>>>=== Reliance of Salaried Developers ===
>>>
>>>All of the initial committers are paid by SAP to work on this or related
>>>projects.
>>>
>>>=== Relationships with Other Apache Products ===
>>>
>>>Apache OData will directly use at least the following projects:
>>>
>>> * Apache CXF - for REST bindings
>>> * Apache Commons - for encoding/decoding
>>>
>>>Other Apache projects may be interested in using Apache OData to add
>>>OData support once the standard is final.
>>>
>>>=== An Excessive Fascination with the Apache Brand ===
>>>
>>>We value Apache as a neutral place where diverse communities can work
>>>together on implementing shared standards. We hope that this part of the
>>>Apache brand helps attract contributions from many potential OData
>>>standard consumers. However, the brand value is not the main reason why
>>>we prefer to have this project at Apache.
>>>
>>>== Documentation ==
>>>
>>>This project is still at an early stage, so there is not much
>>>documentation available. See the OASIS OData page and odata.org web site
>>>for information about the OData standardization effort.
>>>
>>>== Initial Source ==
>>>
>>> * [[https://github.com/SAP/cloud-odata-java]]
>>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>>>
>>>== Source and Intellectual Property Submission Plan ==
>>>
>>>The complete code is under Apache Software License 2.
>>>
>>>== External Dependencies ==
>>>
>>>All the external dependencies of the initial codebases comply with
>>>Apache
>>>licensing policies.
>>>
>>>== Cryptography ==
>>>
>>>Apache OData is not expected to implement or use cryptographic code.
>>>
>>>== Required Resources ==
>>>
>>>=== Mailing lists ===
>>>
>>> * odata-dev'at'incubator.apache.org
>>> * odata-commits'at'incubator.apache.org
>>> * odata-private'at'incubator.apache.org
>>>
>>>=== Subversion Directory ===
>>>
>>>writeable Git Repository (preferred)
>>>
>>>    [[git://git.apache.org/odata.git]]
>>>
>>>or SVN Directory
>>>
>>>    [[https://svn.apache.org/repos/asf/incubator/odata]]
>>>
>>>=== Issue Tracking ===
>>>
>>>    JIRA OData (OData)
>>>
>>>=== Other Resources ===
>>>
>>>    none
>>>
>>>== Initial Committers ==
>>>
>>>|| '''Name'''       || '''Email'''                 ||
>>>|| Stephan Klevenz  || sklevenz'at'apache.org      ||
>>>|| Jens Huesken     || jens.huesken'at'sap.com     ||
>>>|| Christian Amend  || christian.amend'at'sap.com  ||
>>>|| Michael Bolz     || michael.bolz'at'sap.com     ||
>>>|| Tamara Boehm     || tamara.boehm'at'sap.com     ||
>>>|| Chandan V A      || chandan.v.a'at'sap.com      ||
>>>|| Anirban Roy      || anirban.roy'at'sap.com      ||
>>>|| Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>>>|| Jobin John       || jobin.john'at'sap.com       ||
>>>|| Joerg Singler    || joerg.singler'at'sap.com    ||
>>>
>>>== Affiliations ==
>>>
>>>|| '''Name'''          || '''Affilitation''' ||
>>>|| Stephan Klevenz     || SAP AG       ||
>>>|| Jens Huesken        || SAP AG       ||
>>>|| Christian Amend     || SAP AG       ||
>>>|| Michael Bolz        || SAP AG       ||
>>>|| Tamara Boehm        || SAP AG       ||
>>>|| Chandan V A         || SAP AG       ||
>>>|| Anirban Roy         || SAP AG       ||
>>>|| Chitresh Chauhan    || SAP AG       ||
>>>|| Jobin John          || SAP AG       ||
>>>|| Joerg Singler       || SAP AG       ||
>>>
>>>== Sponsors ==
>>>
>>>Champion
>>>
>>> * Florian Mueller
>>>
>>>Nominated Mentors
>>>
>>> * Florian Mueller
>>> * tbd.
>>>
>>>Sponsoring Entiy
>>>
>>> * Incubator PMC
>>>
>>>==== Links ====
>>>
>>> * [1] [[http://www.odata.org]]
>>> * [2] 
>>>[[http://www.microsoft.com/openspecifications/en/us/programs/osp/default
>>>.
>>>a
>>>spx]]
>>> * [3] 
>>>[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
>>> * [4] 
>>>[[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>

Re: [PROPOSAL] OData Proposal for Incubator

Posted by "Klevenz, Stephan" <st...@sap.com>.
Rob,

Thanks for your hint. I do understand Marmotta as an implementation of the
Linked Data Platform (LDP). Linked Data is a concept for building a
semantic web where things are identified by URIs. Links can be used to
explore things.

OData is a data centric protocol which describes metadata and allows data
queries. It can be seen as the SQL for the web. One main use case is to
open data silos to be accessible over the web. Apache OData is a
implementation of the OData protocol.

Although LDP and OData make use of REST principles both do address
different uses cases. I don't see overlap here.


Regards,
Stephan





On 17.06.13 18:59, "Rob Vesse" <rv...@yarcdata.com> wrote:

>Stephan
>
>What overlap (if any) do you see with the existing Marmotta podling?
>
>They are building out an implementation of the Linked Data Platform which
>is a ongoing W3C standardization effort
>(http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a
>more RDF/Semantic Web centric alternative to the MS/Oasis OData standard.
>
>Rob
>
>
>On 6/17/13 8:35 AM, "Klevenz, Stephan" <st...@sap.com> wrote:
>
>>Dear ASF members,
>>
>>We would like to propose the OData project to the Incubator.
>>
>>The OData Proposal is available at:
>>https://wiki.apache.org/incubator/ODataProposal
>>
>>We welcome your feedback and suggestions.
>>
>>Thanks!
>>
>>Stephan Klevenz
>>
>>
>>
>>= Apache OData =
>>
>>=== Abstract ===
>>
>>Apache OData is a generic Java language implementation of the OData 2.0
>>specification which will serve as a code base for the upcoming OASIS
>>OData specification.
>>
>>=== Proposal ===
>>
>>The Open Data Protocol (OData) [1] is a Web protocol for querying and
>>updating data that provides a way to unlock your data and free it from
>>silos that exist in applications today. OData does this by applying and
>>building upon Web technologies such as HTTP, Atom Publishing Protocol
>>(AtomPub) and JSON to provide access to information from a variety of
>>applications, services, and stores.
>>
>>The Apache OData is a library which enables developers to implement OData
>>producers and OData consumers. Basic principles of the library are to
>>provide an OData 2.0 specification compliant OData Library, enhancements
>>shall be possible in a compatible manner, have a clear separation between
>>Core and API, to provide an option to build extensions on top. This
>>library should be base for implementing future releases of the
>>specification.
>>
>>=== Background ===
>>
>>OData was originally developed by Microsoft and is released in a version
>>2.0 under an Open Specification Promise [2]. A lot of companies did show
>>interests in this protocol, used it in products and gave feedback back to
>>Microsoft. This joined effort resulted in a new release OData 3.0 in
>>2012, this version became the basis for the OASIS technical committee [3]
>>which is currently working on a new version of the specification. This
>>OASIS standard release is expected this year.
>>
>>The initial Java code of this project was developed by a development team
>>that had already experience with other OData 2.0 and 3.0 implementations
>>at SAP AG. The current code base implements OData 2.0 and because of this
>>version is widely used it is a good starting point to build an open
>>source community for the OData standard.
>>
>>The current code also comes up with an implementation of an OData sample
>>service. On the one side this is an example for users which want to use
>>the library to expose their own data and on the other side it illustrates
>>how implemented features work.
>>
>>Additionally, the code base includes an extension which is called JPA
>>processor. With this extension it is easy to expose any JPA persistence
>>model via OData protocol without a lot of coding.
>>
>>=== Rationale ===
>>
>>More software vendors moving to OData means more choice for customers who
>>will be able to use different implementations. For the standard to
>>succeed, however, ensuring interoperability is paramount: in order to
>>manage an ever growing context and leverage the enormous portability and
>>interoperability issues that a globally adopted standard brings, it is
>>necessary to think about how to make the related ecosystem healthy and
>>sustainable. Successful modern standards are driven by:
>>
>> * Clear documentation, built iteratively with continuous feedback from
>>stakeholders
>> * A clearly defined compatibility process, enforced by tools that allow
>>to gauge how implementations can be compatible and interoperable
>> * Accurate compliance criteria, documented in writing as well as in
>>actual testing code that measure how tools and libraries are able to
>>interoperate
>> * A sample implementation to clear up potential doubts and ensure that
>>the standard can actually be implemented in real life scenarios
>>
>>The above mentioned pieces are able to make the development activity,
>>towards an OData implementation, easier and more successful. Having an
>>healthy ecosystem will ensure a smoother implementation process, more
>>compliant products, and ultimately, a wider adoption of the standard.
>>
>>The OData ecosystem has been successful in creating and documenting early
>>versions of the standard, yet it might potentially lack two very
>>important aspects, that is a exhaustive implementation of the complete
>>protocol that can be used productively and to ensure interoperability. As
>>much as such artifacts can be developed independently by any OData
>>proponent, the value of having a neutral party as a steward of actual
>>code is to be considered. The Apache Software Foundation has been playing
>>this kind of role for many years, and can provide the perfect environment
>>to foster contributions on the OData theme with a great amount of
>>expertise.
>>
>>=== Initial Goals ===
>>
>> * Implement OData 2.0, make it final and mature
>> * Start implementation of OASIS OData draft specification
>> * Provide input and feedback for the draft specification to the OASIS
>>OData TC based on implementation
>> * Implement OData add-ons (library extensions and toolset)
>>
>>== Current Status ==
>>
>>=== Meritocracy ===
>>
>>Most of the initial committers are open source developers with different
>>experience levels and many of them have already worked in other open
>>source or Apache projects. We will follow standard Apache procedures in
>>accepting new contributors to the project team.
>>
>>=== Community ===
>>
>>Managed by an OASIS Technical Committee, the OData standard definition
>>should be based on the idea of a community driven effort.
>>
>>Apache OData aims to be a community driven initiative in developing a
>>Java OData implementation. Such an approach is allowing more transparency
>>and direct feedback even within the definition and improvement of OData
>>specifications.
>>
>>We encourage everyone interested in OData to join the Apache OData
>>effort.
>>
>>=== Core Developers ===
>>
>>The development team is international and they have all strong skills in
>>OData protocol. Jens Huesken who is member of the OASIS OData TC is
>>providing specification feedback since OData 2.0. Stephan Klevenz, also a
>>OASIS OData TC member, was a committer of the Apache Chemistry project.
>>He has experience with the Incubator and Apache and was also a speaker on
>>ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>>Boehm did implement core parts of the library. Chandan V A, Anirban Roy,
>>Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA
>>processor add on.
>>
>>=== Alignment ===
>>
>>The project builds with Apache Maven, the core runtime requires Apache
>>CXF for REST binding (JAX-RS) and the sample scenario can be deployed
>>into any compliant Servlet or J2EE container like Apache Tomcat.
>>Furthermore we see OData protocol as an option to be supported by other
>>Apache projects that have to expose data via a standardized protocol
>>based interface.
>>
>>== Known Risks ==
>>
>>=== Orphaned products ===
>>
>>Apache OData is a fresh new codebase that targets the still moving OData
>>standardization effort. Thus the future of this project depends heavily
>>on the success of the standard. We hope and expect that our
>>implementation efforts will strengthen and support the OData standard.
>>
>>=== Inexperience with Open Source ===
>>
>>Some of the initial committers are experienced open source developers.
>>But there are also committers which are new to open source.
>>
>>=== Homogenous Developers ===
>>
>>The initial committers are from SAP working in different teams. One team
>>is from Germany and has implemented the core parts of the library and the
>>other team is from India and has implemented the JPA processor add-on.
>>
>>=== Reliance of Salaried Developers ===
>>
>>All of the initial committers are paid by SAP to work on this or related
>>projects.
>>
>>=== Relationships with Other Apache Products ===
>>
>>Apache OData will directly use at least the following projects:
>>
>> * Apache CXF - for REST bindings
>> * Apache Commons - for encoding/decoding
>>
>>Other Apache projects may be interested in using Apache OData to add
>>OData support once the standard is final.
>>
>>=== An Excessive Fascination with the Apache Brand ===
>>
>>We value Apache as a neutral place where diverse communities can work
>>together on implementing shared standards. We hope that this part of the
>>Apache brand helps attract contributions from many potential OData
>>standard consumers. However, the brand value is not the main reason why
>>we prefer to have this project at Apache.
>>
>>== Documentation ==
>>
>>This project is still at an early stage, so there is not much
>>documentation available. See the OASIS OData page and odata.org web site
>>for information about the OData standardization effort.
>>
>>== Initial Source ==
>>
>> * [[https://github.com/SAP/cloud-odata-java]]
>> * [[https://www.ohloh.net/p/cloud-odata-java]]
>>
>>== Source and Intellectual Property Submission Plan ==
>>
>>The complete code is under Apache Software License 2.
>>
>>== External Dependencies ==
>>
>>All the external dependencies of the initial codebases comply with Apache
>>licensing policies.
>>
>>== Cryptography ==
>>
>>Apache OData is not expected to implement or use cryptographic code.
>>
>>== Required Resources ==
>>
>>=== Mailing lists ===
>>
>> * odata-dev'at'incubator.apache.org
>> * odata-commits'at'incubator.apache.org
>> * odata-private'at'incubator.apache.org
>>
>>=== Subversion Directory ===
>>
>>writeable Git Repository (preferred)
>>
>>    [[git://git.apache.org/odata.git]]
>>
>>or SVN Directory
>>
>>    [[https://svn.apache.org/repos/asf/incubator/odata]]
>>
>>=== Issue Tracking ===
>>
>>    JIRA OData (OData)
>>
>>=== Other Resources ===
>>
>>    none
>>
>>== Initial Committers ==
>>
>>|| '''Name'''       || '''Email'''                 ||
>>|| Stephan Klevenz  || sklevenz'at'apache.org      ||
>>|| Jens Huesken     || jens.huesken'at'sap.com     ||
>>|| Christian Amend  || christian.amend'at'sap.com  ||
>>|| Michael Bolz     || michael.bolz'at'sap.com     ||
>>|| Tamara Boehm     || tamara.boehm'at'sap.com     ||
>>|| Chandan V A      || chandan.v.a'at'sap.com      ||
>>|| Anirban Roy      || anirban.roy'at'sap.com      ||
>>|| Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>>|| Jobin John       || jobin.john'at'sap.com       ||
>>|| Joerg Singler    || joerg.singler'at'sap.com    ||
>>
>>== Affiliations ==
>>
>>|| '''Name'''          || '''Affilitation''' ||
>>|| Stephan Klevenz     || SAP AG       ||
>>|| Jens Huesken        || SAP AG       ||
>>|| Christian Amend     || SAP AG       ||
>>|| Michael Bolz        || SAP AG       ||
>>|| Tamara Boehm        || SAP AG       ||
>>|| Chandan V A         || SAP AG       ||
>>|| Anirban Roy         || SAP AG       ||
>>|| Chitresh Chauhan    || SAP AG       ||
>>|| Jobin John          || SAP AG       ||
>>|| Joerg Singler       || SAP AG       ||
>>
>>== Sponsors ==
>>
>>Champion
>>
>> * Florian Mueller
>>
>>Nominated Mentors
>>
>> * Florian Mueller
>> * tbd.
>>
>>Sponsoring Entiy
>>
>> * Incubator PMC
>>
>>==== Links ====
>>
>> * [1] [[http://www.odata.org]]
>> * [2] 
>>[[http://www.microsoft.com/openspecifications/en/us/programs/osp/default.
>>a
>>spx]]
>> * [3] 
>>[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
>> * [4] 
>>[[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>


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

Re: [PROPOSAL] OData Proposal for Incubator

Posted by Rob Vesse <rv...@yarcdata.com>.
Stephan

What overlap (if any) do you see with the existing Marmotta podling?

They are building out an implementation of the Linked Data Platform which
is a ongoing W3C standardization effort
(http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a
more RDF/Semantic Web centric alternative to the MS/Oasis OData standard.

Rob


On 6/17/13 8:35 AM, "Klevenz, Stephan" <st...@sap.com> wrote:

>Dear ASF members,
>
>We would like to propose the OData project to the Incubator.
>
>The OData Proposal is available at:
>https://wiki.apache.org/incubator/ODataProposal
>
>We welcome your feedback and suggestions.
>
>Thanks!
>
>Stephan Klevenz
>
>
>
>= Apache OData =
>
>=== Abstract ===
>
>Apache OData is a generic Java language implementation of the OData 2.0
>specification which will serve as a code base for the upcoming OASIS
>OData specification.
>
>=== Proposal ===
>
>The Open Data Protocol (OData) [1] is a Web protocol for querying and
>updating data that provides a way to unlock your data and free it from
>silos that exist in applications today. OData does this by applying and
>building upon Web technologies such as HTTP, Atom Publishing Protocol
>(AtomPub) and JSON to provide access to information from a variety of
>applications, services, and stores.
>
>The Apache OData is a library which enables developers to implement OData
>producers and OData consumers. Basic principles of the library are to
>provide an OData 2.0 specification compliant OData Library, enhancements
>shall be possible in a compatible manner, have a clear separation between
>Core and API, to provide an option to build extensions on top. This
>library should be base for implementing future releases of the
>specification.
>
>=== Background ===
>
>OData was originally developed by Microsoft and is released in a version
>2.0 under an Open Specification Promise [2]. A lot of companies did show
>interests in this protocol, used it in products and gave feedback back to
>Microsoft. This joined effort resulted in a new release OData 3.0 in
>2012, this version became the basis for the OASIS technical committee [3]
>which is currently working on a new version of the specification. This
>OASIS standard release is expected this year.
>
>The initial Java code of this project was developed by a development team
>that had already experience with other OData 2.0 and 3.0 implementations
>at SAP AG. The current code base implements OData 2.0 and because of this
>version is widely used it is a good starting point to build an open
>source community for the OData standard.
>
>The current code also comes up with an implementation of an OData sample
>service. On the one side this is an example for users which want to use
>the library to expose their own data and on the other side it illustrates
>how implemented features work.
>
>Additionally, the code base includes an extension which is called JPA
>processor. With this extension it is easy to expose any JPA persistence
>model via OData protocol without a lot of coding.
>
>=== Rationale ===
>
>More software vendors moving to OData means more choice for customers who
>will be able to use different implementations. For the standard to
>succeed, however, ensuring interoperability is paramount: in order to
>manage an ever growing context and leverage the enormous portability and
>interoperability issues that a globally adopted standard brings, it is
>necessary to think about how to make the related ecosystem healthy and
>sustainable. Successful modern standards are driven by:
>
> * Clear documentation, built iteratively with continuous feedback from
>stakeholders
> * A clearly defined compatibility process, enforced by tools that allow
>to gauge how implementations can be compatible and interoperable
> * Accurate compliance criteria, documented in writing as well as in
>actual testing code that measure how tools and libraries are able to
>interoperate
> * A sample implementation to clear up potential doubts and ensure that
>the standard can actually be implemented in real life scenarios
>
>The above mentioned pieces are able to make the development activity,
>towards an OData implementation, easier and more successful. Having an
>healthy ecosystem will ensure a smoother implementation process, more
>compliant products, and ultimately, a wider adoption of the standard.
>
>The OData ecosystem has been successful in creating and documenting early
>versions of the standard, yet it might potentially lack two very
>important aspects, that is a exhaustive implementation of the complete
>protocol that can be used productively and to ensure interoperability. As
>much as such artifacts can be developed independently by any OData
>proponent, the value of having a neutral party as a steward of actual
>code is to be considered. The Apache Software Foundation has been playing
>this kind of role for many years, and can provide the perfect environment
>to foster contributions on the OData theme with a great amount of
>expertise.
>
>=== Initial Goals ===
>
> * Implement OData 2.0, make it final and mature
> * Start implementation of OASIS OData draft specification
> * Provide input and feedback for the draft specification to the OASIS
>OData TC based on implementation
> * Implement OData add-ons (library extensions and toolset)
>
>== Current Status ==
>
>=== Meritocracy ===
>
>Most of the initial committers are open source developers with different
>experience levels and many of them have already worked in other open
>source or Apache projects. We will follow standard Apache procedures in
>accepting new contributors to the project team.
>
>=== Community ===
>
>Managed by an OASIS Technical Committee, the OData standard definition
>should be based on the idea of a community driven effort.
>
>Apache OData aims to be a community driven initiative in developing a
>Java OData implementation. Such an approach is allowing more transparency
>and direct feedback even within the definition and improvement of OData
>specifications.
>
>We encourage everyone interested in OData to join the Apache OData effort.
>
>=== Core Developers ===
>
>The development team is international and they have all strong skills in
>OData protocol. Jens Huesken who is member of the OASIS OData TC is
>providing specification feedback since OData 2.0. Stephan Klevenz, also a
>OASIS OData TC member, was a committer of the Apache Chemistry project.
>He has experience with the Incubator and Apache and was also a speaker on
>ApacheCon 2012 in Vancouver. Christian Amend, Michael Bolz and Tamara
>Boehm did implement core parts of the library. Chandan V A, Anirban Roy,
>Chitresh Chauhan, Jobin John and Joerg Singler are working on the JPA
>processor add on.
>
>=== Alignment ===
>
>The project builds with Apache Maven, the core runtime requires Apache
>CXF for REST binding (JAX-RS) and the sample scenario can be deployed
>into any compliant Servlet or J2EE container like Apache Tomcat.
>Furthermore we see OData protocol as an option to be supported by other
>Apache projects that have to expose data via a standardized protocol
>based interface.
>
>== Known Risks ==
>
>=== Orphaned products ===
>
>Apache OData is a fresh new codebase that targets the still moving OData
>standardization effort. Thus the future of this project depends heavily
>on the success of the standard. We hope and expect that our
>implementation efforts will strengthen and support the OData standard.
>
>=== Inexperience with Open Source ===
>
>Some of the initial committers are experienced open source developers.
>But there are also committers which are new to open source.
>
>=== Homogenous Developers ===
>
>The initial committers are from SAP working in different teams. One team
>is from Germany and has implemented the core parts of the library and the
>other team is from India and has implemented the JPA processor add-on.
>
>=== Reliance of Salaried Developers ===
>
>All of the initial committers are paid by SAP to work on this or related
>projects.
>
>=== Relationships with Other Apache Products ===
>
>Apache OData will directly use at least the following projects:
>
> * Apache CXF - for REST bindings
> * Apache Commons - for encoding/decoding
>
>Other Apache projects may be interested in using Apache OData to add
>OData support once the standard is final.
>
>=== An Excessive Fascination with the Apache Brand ===
>
>We value Apache as a neutral place where diverse communities can work
>together on implementing shared standards. We hope that this part of the
>Apache brand helps attract contributions from many potential OData
>standard consumers. However, the brand value is not the main reason why
>we prefer to have this project at Apache.
>
>== Documentation ==
>
>This project is still at an early stage, so there is not much
>documentation available. See the OASIS OData page and odata.org web site
>for information about the OData standardization effort.
>
>== Initial Source ==
>
> * [[https://github.com/SAP/cloud-odata-java]]
> * [[https://www.ohloh.net/p/cloud-odata-java]]
>
>== Source and Intellectual Property Submission Plan ==
>
>The complete code is under Apache Software License 2.
>
>== External Dependencies ==
>
>All the external dependencies of the initial codebases comply with Apache
>licensing policies.
>
>== Cryptography ==
>
>Apache OData is not expected to implement or use cryptographic code.
>
>== Required Resources ==
>
>=== Mailing lists ===
>
> * odata-dev'at'incubator.apache.org
> * odata-commits'at'incubator.apache.org
> * odata-private'at'incubator.apache.org
>
>=== Subversion Directory ===
>
>writeable Git Repository (preferred)
>
>    [[git://git.apache.org/odata.git]]
>
>or SVN Directory
>
>    [[https://svn.apache.org/repos/asf/incubator/odata]]
>
>=== Issue Tracking ===
>
>    JIRA OData (OData)
>
>=== Other Resources ===
>
>    none
>
>== Initial Committers ==
>
>|| '''Name'''       || '''Email'''                 ||
>|| Stephan Klevenz  || sklevenz'at'apache.org      ||
>|| Jens Huesken     || jens.huesken'at'sap.com     ||
>|| Christian Amend  || christian.amend'at'sap.com  ||
>|| Michael Bolz     || michael.bolz'at'sap.com     ||
>|| Tamara Boehm     || tamara.boehm'at'sap.com     ||
>|| Chandan V A      || chandan.v.a'at'sap.com      ||
>|| Anirban Roy      || anirban.roy'at'sap.com      ||
>|| Chitresh Chauhan || chitresh.chauhan'at'sap.com ||
>|| Jobin John       || jobin.john'at'sap.com       ||
>|| Joerg Singler    || joerg.singler'at'sap.com    ||
>
>== Affiliations ==
>
>|| '''Name'''          || '''Affilitation''' ||
>|| Stephan Klevenz     || SAP AG       ||
>|| Jens Huesken        || SAP AG       ||
>|| Christian Amend     || SAP AG       ||
>|| Michael Bolz        || SAP AG       ||
>|| Tamara Boehm        || SAP AG       ||
>|| Chandan V A         || SAP AG       ||
>|| Anirban Roy         || SAP AG       ||
>|| Chitresh Chauhan    || SAP AG       ||
>|| Jobin John          || SAP AG       ||
>|| Joerg Singler       || SAP AG       ||
>
>== Sponsors ==
>
>Champion
>
> * Florian Mueller
>
>Nominated Mentors
>
> * Florian Mueller
> * tbd.
>
>Sponsoring Entiy
>
> * Incubator PMC
>
>==== Links ====
>
> * [1] [[http://www.odata.org]]
> * [2] 
>[[http://www.microsoft.com/openspecifications/en/us/programs/osp/default.a
>spx]]
> * [3] 
>[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata]]
> * [4] 
>[[https://www.oasis-open.org/committees/membership.php?wg_abbrev=odata]]
>


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