You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by Kevin Ratnasekera <dj...@gmail.com> on 2015/02/17 18:50:06 UTC
GSoC 2015 Introduction
Hi all,
I am Kevin Ratnasekera, final year Computer Science Engineering
Undergraduate from University of Moratuwa, Sri Lanka. I successfully
completed and participated in GSoC 2014. I also have open source industrial
experience with WSO2 ( an open source middleware company ) where I acquired
knowledge in the areas of SOA and Web services, technologies such as REST,
SOAP, XML, JSON etc. I am interested in participating GSoC this year with
Apache Olingo. I went through the Apache gsoc ideas list, found this
"Implement OData Json Metadocument Serializer/Parser" project really
interesting. Even though I got some background knowledge, I am new to OData
and Olingo. I really appreciate, if a mentor could provide me some guidance
to get things started and areas which I need to gather knowledge and
improve.
Regards
Kevin
.
RE: GSoC 2015 Introduction
Posted by "Amend, Christian" <ch...@sap.com>.
Hi Kevin,
sorry for my late reply. You did a lot of research ☺ As you correctly understood the main topic is to transform the EDM into a json document. You do not have to define the format on your own. There is already a specification draft here: https://www.oasis-open.org/committees/document.php?document_id=54598&wg_abbrev=odata
This draft outlines how the json document should look like. Unfortunately this draft is not part of the latest released specification and thus is subject to change during the next months.
When I said there is lots to be done for the json fomat I meant our serialization in general. For example there are 3 different ways in Json to expose an entity as a json document(see here http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata02/os/odata-json-format-v4.0-errata02-os-complete.html#_Toc403940604). All 3 versions differ in the amount of additional metadata information within the payload. These 3 are:
- odata.metadata=none (no metadata mixed with entity data)
- odata.metadata=minimal(a subset of metadata information with the entity data)
- odata.metadata=full(full metadata information with the entity data)
We have currently implemented the odata.metadata=minimal. So the other 2 formats are still missing. This is something you could work on as well if you like.
So for tasks I would suggest this:
1. Understand the current draft of the json metadata document
2. Take a draft version once the GSoC officially begins and start implementing based on that draft version
Stretch goals could be:
1. Support odata.metadata=none for entities
2. Support odata.metadata=full for entities
Anyway you should not invest too much time for now until Apache is accepted and the Olingo project gets granted a seat. For now it is enough if you get the concept of this and understand the tasks.
Best Regards,
Christian
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
Sent: Sonntag, 22. Februar 2015 10:01
To: Amend, Christian
Cc: dev@olingo.apache.org
Subject: Re: GSoC 2015 Introduction
Hi Christian,
I hope ASF will get accepted as a mentoring organization this year too :) I made some background study the links you mentioned and some posts related to Oasis Odata specifications .I need some clarifications in order to understand the problem clearly. If I understood problem correctly, currently the metadata document describes it s data using Entity Data Model (EDM) using format based on XML which is Conceptual Schema Definition Language (CSDL). So as you mentioned our project first task is to come up with a JSON format similar to CSDL so that we can describe metadata document in JSON. As JSON Schema [1] format is used for describe the data in JSON, we can use a similar approach to describe EDM. Inside JSON schema format there many different ways of describing the EDM. Is this what you meant by the previous mail statement "There are also many other possibilities when it comes to the json serialization."? If I got this thing correctly, I need come with a kind of specification to this format from my own before the official specification get published. While considering the all aspects of EDM and CSDL specification I need some time to come up with proper JSON format while considering all aspects. Please do comment on this, I need some feedback in order to move forward and I can come up with a documentation of this format too.
I also went through some samples and tutorials mentioned Apache Olingo, was able to setup the development environment too.
[1]http://json-schema.org/
Regards
Kevin
On Thu, Feb 19, 2015 at 4:46 PM, Amend, Christian <ch...@sap.com>> wrote:
Hi Kevin,
also please keep in mind that the Apache Software Foundation has yet to be accepted as a mentoring organization. I don`t see any reason why this should not happen but the final decision will be made public on March 2nd 2015.
Best Regards,
Christian
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com<ma...@gmail.com>]
Sent: Donnerstag, 19. Februar 2015 11:43
To: Amend, Christian
Cc: dev@olingo.apache.org<ma...@olingo.apache.org>
Subject: Re: GSoC 2015 Introduction
Hi Christian,
Thank you very much for your points. I will go through each and come up with more detail.
Regards
Kevin
On Wed, Feb 18, 2015 at 9:58 PM, Amend, Christian <ch...@sap.com>> wrote:
Hi Kevin,
it is awesome that you are interested in our Olingo project. Basically all the information you need can be found on our website here: http://olingo.apache.org/ and the oasis OData website here: http://www.odata.org/ have a look at the V4 specification.
About the json metadata topic: The issue you found is an initial draft of how the task could look like. Depending on how far the official specification is on publishing the final json metadata format the project goes forward. There are also many other possibilities when it comes to the json serialization. So the first and primary goal for this GSoC is to provide the json metadata document but if you are fast we can extend the scope for this project.
If you have any questions about this don`t hesitate to write to the mailing list or comment on the Jira issue. You can also subscribe to our dev and users list by writing a mail to user-subscribe@olingo.apache.org<ma...@olingo.apache.org> and dev-subscribe@olingo.apache.org<ma...@olingo.apache.org>
You should also know that this is the first time I mentor an GSoC project :-)
Best Regards,
Christian
-----Original Message-----
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com<ma...@gmail.com>]
Sent: Dienstag, 17. Februar 2015 18:50
To: dev@olingo.apache.org<ma...@olingo.apache.org>
Subject: GSoC 2015 Introduction
Hi all,
I am Kevin Ratnasekera, final year Computer Science Engineering
Undergraduate from University of Moratuwa, Sri Lanka. I successfully
completed and participated in GSoC 2014. I also have open source industrial
experience with WSO2 ( an open source middleware company ) where I acquired
knowledge in the areas of SOA and Web services, technologies such as REST,
SOAP, XML, JSON etc. I am interested in participating GSoC this year with
Apache Olingo. I went through the Apache gsoc ideas list, found this
"Implement OData Json Metadocument Serializer/Parser" project really
interesting. Even though I got some background knowledge, I am new to OData
and Olingo. I really appreciate, if a mentor could provide me some guidance
to get things started and areas which I need to gather knowledge and
improve.
Regards
Kevin
.
Re: GSoC 2015 Introduction
Posted by Kevin Ratnasekera <dj...@gmail.com>.
Hi Christian,
I hope ASF will get accepted as a mentoring organization this year too :) I
made some background study the links you mentioned and some posts related
to Oasis Odata specifications .I need some clarifications in order to
understand the problem clearly. If I understood problem correctly,
currently the metadata document describes it s data using Entity Data Model
(EDM) using format based on XML which is Conceptual Schema Definition
Language (CSDL). So as you mentioned our project first task is to come up
with a JSON format similar to CSDL so that we can describe metadata
document in JSON. As JSON Schema [1] format is used for describe the data
in JSON, we can use a similar approach to describe EDM. Inside JSON schema
format there many different ways of describing the EDM. Is this what you
meant by the previous mail statement "There are also many other
possibilities when it comes to the json serialization."? If I got this
thing correctly, I need come with a kind of specification to this format
from my own before the official specification get published. While
considering the all aspects of EDM and CSDL specification I need some time
to come up with proper JSON format while considering all aspects. Please do
comment on this, I need some feedback in order to move forward and I can
come up with a documentation of this format too.
I also went through some samples and tutorials mentioned Apache Olingo, was
able to setup the development environment too.
[1]http://json-schema.org/
Regards
Kevin
On Thu, Feb 19, 2015 at 4:46 PM, Amend, Christian <ch...@sap.com>
wrote:
> Hi Kevin,
>
>
>
> also please keep in mind that the Apache Software Foundation has yet to be
> accepted as a mentoring organization. I don`t see any reason why this
> should not happen but the final decision will be made public on March 2nd
> 2015.
>
>
>
> Best Regards,
>
> Christian
>
>
>
> *From:* Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
> *Sent:* Donnerstag, 19. Februar 2015 11:43
> *To:* Amend, Christian
> *Cc:* dev@olingo.apache.org
> *Subject:* Re: GSoC 2015 Introduction
>
>
>
> Hi Christian,
>
> Thank you very much for your points. I will go through each and come up
> with more detail.
>
> Regards
>
> Kevin
>
>
>
> On Wed, Feb 18, 2015 at 9:58 PM, Amend, Christian <ch...@sap.com>
> wrote:
>
> Hi Kevin,
>
> it is awesome that you are interested in our Olingo project. Basically all
> the information you need can be found on our website here:
> http://olingo.apache.org/ and the oasis OData website here:
> http://www.odata.org/ have a look at the V4 specification.
>
> About the json metadata topic: The issue you found is an initial draft of
> how the task could look like. Depending on how far the official
> specification is on publishing the final json metadata format the project
> goes forward. There are also many other possibilities when it comes to the
> json serialization. So the first and primary goal for this GSoC is to
> provide the json metadata document but if you are fast we can extend the
> scope for this project.
>
> If you have any questions about this don`t hesitate to write to the
> mailing list or comment on the Jira issue. You can also subscribe to our
> dev and users list by writing a mail to user-subscribe@olingo.apache.org
> and dev-subscribe@olingo.apache.org
>
> You should also know that this is the first time I mentor an GSoC project
> :-)
>
> Best Regards,
> Christian
>
>
> -----Original Message-----
> From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
> Sent: Dienstag, 17. Februar 2015 18:50
> To: dev@olingo.apache.org
> Subject: GSoC 2015 Introduction
>
> Hi all,
> I am Kevin Ratnasekera, final year Computer Science Engineering
> Undergraduate from University of Moratuwa, Sri Lanka. I successfully
> completed and participated in GSoC 2014. I also have open source industrial
> experience with WSO2 ( an open source middleware company ) where I acquired
> knowledge in the areas of SOA and Web services, technologies such as REST,
> SOAP, XML, JSON etc. I am interested in participating GSoC this year with
> Apache Olingo. I went through the Apache gsoc ideas list, found this
> "Implement OData Json Metadocument Serializer/Parser" project really
> interesting. Even though I got some background knowledge, I am new to OData
> and Olingo. I really appreciate, if a mentor could provide me some guidance
> to get things started and areas which I need to gather knowledge and
> improve.
> Regards
> Kevin
>
>
>
>
>
>
>
>
>
>
>
>
>
> .
>
>
>
RE: GSoC 2015 Introduction
Posted by "Amend, Christian" <ch...@sap.com>.
Hi Kevin,
also please keep in mind that the Apache Software Foundation has yet to be accepted as a mentoring organization. I don`t see any reason why this should not happen but the final decision will be made public on March 2nd 2015.
Best Regards,
Christian
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
Sent: Donnerstag, 19. Februar 2015 11:43
To: Amend, Christian
Cc: dev@olingo.apache.org
Subject: Re: GSoC 2015 Introduction
Hi Christian,
Thank you very much for your points. I will go through each and come up with more detail.
Regards
Kevin
On Wed, Feb 18, 2015 at 9:58 PM, Amend, Christian <ch...@sap.com>> wrote:
Hi Kevin,
it is awesome that you are interested in our Olingo project. Basically all the information you need can be found on our website here: http://olingo.apache.org/ and the oasis OData website here: http://www.odata.org/ have a look at the V4 specification.
About the json metadata topic: The issue you found is an initial draft of how the task could look like. Depending on how far the official specification is on publishing the final json metadata format the project goes forward. There are also many other possibilities when it comes to the json serialization. So the first and primary goal for this GSoC is to provide the json metadata document but if you are fast we can extend the scope for this project.
If you have any questions about this don`t hesitate to write to the mailing list or comment on the Jira issue. You can also subscribe to our dev and users list by writing a mail to user-subscribe@olingo.apache.org<ma...@olingo.apache.org> and dev-subscribe@olingo.apache.org<ma...@olingo.apache.org>
You should also know that this is the first time I mentor an GSoC project :-)
Best Regards,
Christian
-----Original Message-----
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com<ma...@gmail.com>]
Sent: Dienstag, 17. Februar 2015 18:50
To: dev@olingo.apache.org<ma...@olingo.apache.org>
Subject: GSoC 2015 Introduction
Hi all,
I am Kevin Ratnasekera, final year Computer Science Engineering
Undergraduate from University of Moratuwa, Sri Lanka. I successfully
completed and participated in GSoC 2014. I also have open source industrial
experience with WSO2 ( an open source middleware company ) where I acquired
knowledge in the areas of SOA and Web services, technologies such as REST,
SOAP, XML, JSON etc. I am interested in participating GSoC this year with
Apache Olingo. I went through the Apache gsoc ideas list, found this
"Implement OData Json Metadocument Serializer/Parser" project really
interesting. Even though I got some background knowledge, I am new to OData
and Olingo. I really appreciate, if a mentor could provide me some guidance
to get things started and areas which I need to gather knowledge and
improve.
Regards
Kevin
.
Re: GSoC 2015 Introduction
Posted by Kevin Ratnasekera <dj...@gmail.com>.
Hi Christian,
Thank you very much for your points. I will go through each and come up
with more detail.
Regards
Kevin
On Wed, Feb 18, 2015 at 9:58 PM, Amend, Christian <ch...@sap.com>
wrote:
> Hi Kevin,
>
> it is awesome that you are interested in our Olingo project. Basically all
> the information you need can be found on our website here:
> http://olingo.apache.org/ and the oasis OData website here:
> http://www.odata.org/ have a look at the V4 specification.
>
> About the json metadata topic: The issue you found is an initial draft of
> how the task could look like. Depending on how far the official
> specification is on publishing the final json metadata format the project
> goes forward. There are also many other possibilities when it comes to the
> json serialization. So the first and primary goal for this GSoC is to
> provide the json metadata document but if you are fast we can extend the
> scope for this project.
>
> If you have any questions about this don`t hesitate to write to the
> mailing list or comment on the Jira issue. You can also subscribe to our
> dev and users list by writing a mail to user-subscribe@olingo.apache.org
> and dev-subscribe@olingo.apache.org
>
> You should also know that this is the first time I mentor an GSoC project
> :-)
>
> Best Regards,
> Christian
>
> -----Original Message-----
> From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
> Sent: Dienstag, 17. Februar 2015 18:50
> To: dev@olingo.apache.org
> Subject: GSoC 2015 Introduction
>
> Hi all,
> I am Kevin Ratnasekera, final year Computer Science Engineering
> Undergraduate from University of Moratuwa, Sri Lanka. I successfully
> completed and participated in GSoC 2014. I also have open source industrial
> experience with WSO2 ( an open source middleware company ) where I acquired
> knowledge in the areas of SOA and Web services, technologies such as REST,
> SOAP, XML, JSON etc. I am interested in participating GSoC this year with
> Apache Olingo. I went through the Apache gsoc ideas list, found this
> "Implement OData Json Metadocument Serializer/Parser" project really
> interesting. Even though I got some background knowledge, I am new to OData
> and Olingo. I really appreciate, if a mentor could provide me some guidance
> to get things started and areas which I need to gather knowledge and
> improve.
> Regards
> Kevin
>
>
>
>
>
>
>
>
>
>
>
>
>
> .
>
RE: GSoC 2015 Introduction
Posted by "Amend, Christian" <ch...@sap.com>.
Hi Kevin,
it is awesome that you are interested in our Olingo project. Basically all the information you need can be found on our website here: http://olingo.apache.org/ and the oasis OData website here: http://www.odata.org/ have a look at the V4 specification.
About the json metadata topic: The issue you found is an initial draft of how the task could look like. Depending on how far the official specification is on publishing the final json metadata format the project goes forward. There are also many other possibilities when it comes to the json serialization. So the first and primary goal for this GSoC is to provide the json metadata document but if you are fast we can extend the scope for this project.
If you have any questions about this don`t hesitate to write to the mailing list or comment on the Jira issue. You can also subscribe to our dev and users list by writing a mail to user-subscribe@olingo.apache.org and dev-subscribe@olingo.apache.org
You should also know that this is the first time I mentor an GSoC project :-)
Best Regards,
Christian
-----Original Message-----
From: Kevin Ratnasekera [mailto:djkevincr1989@gmail.com]
Sent: Dienstag, 17. Februar 2015 18:50
To: dev@olingo.apache.org
Subject: GSoC 2015 Introduction
Hi all,
I am Kevin Ratnasekera, final year Computer Science Engineering
Undergraduate from University of Moratuwa, Sri Lanka. I successfully
completed and participated in GSoC 2014. I also have open source industrial
experience with WSO2 ( an open source middleware company ) where I acquired
knowledge in the areas of SOA and Web services, technologies such as REST,
SOAP, XML, JSON etc. I am interested in participating GSoC this year with
Apache Olingo. I went through the Apache gsoc ideas list, found this
"Implement OData Json Metadocument Serializer/Parser" project really
interesting. Even though I got some background knowledge, I am new to OData
and Olingo. I really appreciate, if a mentor could provide me some guidance
to get things started and areas which I need to gather knowledge and
improve.
Regards
Kevin
.