Hi Allison, Consider yourself registered as an API user! We don't have a planned date for API user registration but joining the sourceforge devel mailing list and keeping us updated with your app plans is probably the best option if you are taking a production quality dependency on us.
I see the problem, but unfortunately the titles for reference data can and will change relatively frequently without notice as these aren't code, they're data - instead we should provide you the ID number (in this case, 1) for the level type (which won't change). We will introduce and retire Level types and connectors etc so your app need to be able to cope with changes in the data and ideally not use hard coded text as filters. Perhaps I could review a test version of your app to check? In addition, we are also working on a component/widget which companies can embed on their own site and it will likely duplicate the type of functionality you have built (I'm just guessing), you may decide in the future to switch over to that once it's ready if it suits your requirements? Although its not very helpful to you our API page currently does have the following disclaimer: API V0.2a April 2011 - Note: this service and documentation is alpha/beta quality and is subject to change without notice. That said, we don't actually want to break your app if we can avoid it, letting us know about your app helps us look out for problems in advance and test after we've deployed changes. We can help by providing Reference ID numbers in the data for you to filter on instead of the text value. If you're using the JSON data feed then you already have that information being returned to you by our API but I've just noticed the XML output doesn't include the reference id, it only has the text so if your using the XML (or other) output then I can see a problem. We will add the reference ID for the ChargerType for you to filter on in that case.
In general I would keep in touch with us about your plans and if you can provide a test/demo version of the app to myself then I can make sure we don't do anything to jeopardise it's success.
Best Regards,Christopher Cook
On 25 October 2011 at 15:36 Allison M Cooper <amcooper@...> wrote:
Thanks for getting back with me. We were looking for 'level 1' on the power type to set different colored pin points, and when it changed to "Level 1 (very slow charge)" (can't think of the exact wording off the top of my head), it showed all of our levels as blank. Would these advance notices be in the What's Happening? section in SourceForge or should I be looking elsewhere? I see a bunch of listings there regarding changes, but I don't see a high level sentence or two for the changes and a date of when the change would be in production.
You mentioned there will be a simpler way to register as an API user. Do you have an idea of how soon this will be? Will these users be notified of changes ahead of time? We are gearing up for QA testing, but may put it on hold until there is a simpler way to register as an API user. My fear is that we roll out to production, a change is made, and then we are broken and it will look poorly on us.
From: Christopher Cook <christopher.cook@...: "amcooper@..." <amcooper@...: 10/22/2011 10:09 AMSubject: Fwd: [Openchargemap-devel] recent change
Hi, With regards to breaking changes, I wasn't aware of any but they're probably my fault if they occur. If you join the openchargemap devel list on sourceforge you should hear about any major changes in advance.
We will be providing a simpler way to register as an API user shortly.
If your project is publically available we'd love to see it. If you have any technical queries please send them to this list.
Best regards Christopher Cook From: Lee Howard Sent: 18/10/2011 14:18 To: A Cooper Cc: openchargemap-devel@... Subject: Re: [Openchargemap-devel] recent change
I'm replying to the appropriate mailing list where your question can be answered.
A Cooper wrote: > Anand Bahl was an intern working at Consumers Energy on an intern > project with using OpenChargeMap as our foundation to show users plug > in charger locations. His internship has ended, so the mobile application > delivery team has taken over this project. We noticed recently that some > of the data has changed, so our plotting levels aren\'t being displayed > correctly. Do you have a list of people you contact before making these > changes, so we could proactively change our project so things don\'t > break? If so, I\'d like to be on the list. I tried to submit this question from > your website, but the form doesn\'t display. Please respond to: > amcooper@... . Thanks. > > -- > This message has been sent to you, a registered SourceForge.net user, > by another site user, through the SourceForge.net site. This message > has been delivered to your SourceForge.net mail alias. You may reply > to this message using the "Reply" feature of your email client, or > using the messaging facility of SourceForge.net at: > https://sourceforge.net/sendmessage.php?touser=3586679 > > >
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ openchargemap-devel mailing list openchargemap-devel@... https://lists.sourceforge.net/lists/listinfo/openchargemap-devel ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ openchargemap-devel mailing list openchargemap-devel@... https://lists.sourceforge.net/lists/listinfo/openchargemap-devel