Java Script library Name voting result

["Kobler-Morris, Sven" <sv...@sap.com>]

Hi, 

for the name the majority is for "OlingoJS".

So we use OlingoJS as name.

Regards,
Sven

-----Original Message-----
From: V.A, Chandan [mailto:chandan.v.a@sap.com] 
Sent: Montag, 21. Juli 2014 14:32
To: dev@olingo.apache.org
Subject: RE: [VOTE] Java Script library Name

OlingoJS +1

Thanks,
Kind Regards
Chandan VA

-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com] 
Sent: Monday, July 21, 2014 2:19 PM
To: dev@olingo.apache.org
Subject: [VOTE] Java Script library Name

Hi all,

below is a list of collected names for the Java Script OData client library which makes sense from our point of view. For voting please ad a +1 behind your favorite choice.

1. datajs
2. OlingoJS

3. ODataJS

4. Olingo.OData.JS


regards,
Sven

RE: Java Script library Name voting result

[Mark Stafford <ma...@microsoft.com>]

I agree very strongly with Yi. The "official" (defined as a library primarily sponsored by members of the TC) set of libraries should not have unique brands attached to them. Case in point, the .NET library is simply called OData Client for .NET. I believe that introducing unique brands will simply cause OData newcomers confusion. When I search for "OData" and "JavaScript" and see "Breeze.js" and "Olingo.js" show up as results, it's very difficult to distinguish which is the "official" client. I think the best thing we can do for the OData community is try to adopt naming conventions that focus on the OData brand. I think it's perfectly fine to use OlingoJS in namespaces and code, but when searching for the library on Bower or NuGet I'd much rather see us use the name OData.js or OData Client for JavaScript. If we can agree on a naming convention we will try to bring the name of the .NET client into conformance.

Thanks,
Mark

-----Original Message-----
From: Yi Ding [mailto:yiding@microsoft.com] 
Sent: Thursday, July 24, 2014 2:20 PM
To: dev@olingo.apache.org
Subject: RE: Java Script library Name voting result

Hi all,

I would propose that we reconsider using the name OData.JS or ODataJS. OlingoJS certainly got majority of the votes but the number of votes is small (only 6 votes).

This JavaScript client library for OData is the core client library for JavaScript mainly developed by sponsors of the TC of OASIS for OData (at least this first version), so it qualifies as an official JavaScript library of OData. Having OData.JS or ODataJS as its name will vastly increase the possibility that users will turn to our library as the first choice when he searches on the internet for "OData JavaScript library" and names like "OData.js", "Breeze.js", "JayData", etc. show up at the same time. Using OlingoJS will likely to cause brand dilution. Apache Olingo as the project name is totally respected but having OData as part of the library name would also be very beneficial. 

It would be really helpful if people voted on OlingoJS can shed light on your reasons for this choice so that we can discuss about it. 

Best,
Yi

-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com] 
Sent: Wednesday, July 23, 2014 11:02 PM
To: dev@olingo.apache.org
Subject: Java Script library Name voting result

Hi, 

for the name the majority is for "OlingoJS".

So we use OlingoJS as name.

Regards,
Sven

-----Original Message-----
From: V.A, Chandan [mailto:chandan.v.a@sap.com] 
Sent: Montag, 21. Juli 2014 14:32
To: dev@olingo.apache.org
Subject: RE: [VOTE] Java Script library Name

OlingoJS +1

Thanks,
Kind Regards
Chandan VA

-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com] 
Sent: Monday, July 21, 2014 2:19 PM
To: dev@olingo.apache.org
Subject: [VOTE] Java Script library Name

Hi all,

below is a list of collected names for the Java Script OData client library which makes sense from our point of view. For voting please ad a +1 behind your favorite choice.

1. datajs
2. OlingoJS

3. ODataJS

4. Olingo.OData.JS


regards,
Sven

RE: Java Script library Name voting result

[Yi Ding <yi...@microsoft.com>]

Hi all,

I would propose that we reconsider using the name OData.JS or ODataJS. OlingoJS certainly got majority of the votes but the number of votes is small (only 6 votes).

This JavaScript client library for OData is the core client library for JavaScript mainly developed by sponsors of the TC of OASIS for OData (at least this first version), so it qualifies as an official JavaScript library of OData. Having OData.JS or ODataJS as its name will vastly increase the possibility that users will turn to our library as the first choice when he searches on the internet for "OData JavaScript library" and names like "OData.js", "Breeze.js", "JayData", etc. show up at the same time. Using OlingoJS will likely to cause brand dilution. Apache Olingo as the project name is totally respected but having OData as part of the library name would also be very beneficial. 

It would be really helpful if people voted on OlingoJS can shed light on your reasons for this choice so that we can discuss about it. 

Best,
Yi

-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com] 
Sent: Wednesday, July 23, 2014 11:02 PM
To: dev@olingo.apache.org
Subject: Java Script library Name voting result

Hi, 

for the name the majority is for "OlingoJS".

So we use OlingoJS as name.

Regards,
Sven

-----Original Message-----
From: V.A, Chandan [mailto:chandan.v.a@sap.com] 
Sent: Montag, 21. Juli 2014 14:32
To: dev@olingo.apache.org
Subject: RE: [VOTE] Java Script library Name

OlingoJS +1

Thanks,
Kind Regards
Chandan VA

-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com] 
Sent: Monday, July 21, 2014 2:19 PM
To: dev@olingo.apache.org
Subject: [VOTE] Java Script library Name

Hi all,

below is a list of collected names for the Java Script OData client library which makes sense from our point of view. For voting please ad a +1 behind your favorite choice.

1. datajs
2. OlingoJS

3. ODataJS

4. Olingo.OData.JS


regards,
Sven