A few weeks ago I had the privilege of attending and speaking at the API Strategy and Design Conference in Austin, TX. First and foremost, if you haven't been to Austin, and you get the chance to go - do. The key takeaway, Frank's - a hotdog joint where you can order ridiculous hotdogs and get cheesy fries with salsa (absolutely a delicious heart attack waiting to happen).
The other takeaways:
APIs are Critical to Success
Businesses everywhere are realizing just how important APIs are to their success. No longer can businesses afford to be silo'd, but even the most isolated companies find themselves now implementing SaaS services and having to extend their platform.
The real takeaway is, if you don't invest in your API, you can be sure your competitors will invest in theirs. And developers and consumers alike are shifting to a platform as a services (PaaS) mindset.
Models Are Key
During the hypermedia track, we took a look at the specifications out there (including Collection+JSON, HAL, Siren, CPHL, and others).
Wow, the 2 weeks since our last blog posts have been amazing, again. We've received an incredible amount of great feedback for the RAML 1.0 RC specification itself, and for the tooling (especially API Workbench), via email, and twitter, and the RAML.org forum, and github, even in person. Reading all these has been a real pleasure, and had demonstrated not only that things are on the right track with 1.0 and the tooling but also generally the value that a very broad community gets from RAML and its ecosystem. So where are things now -- how close are we to finalizing 1.0?
It's been a month since the 1.0 RC was published, and it's now looking like it'll take another couple of weeks or so to fully finalize it. We're making a lot of improvements in the wording and in the specificity, correcting some typos and examples, disambiguating in a few remaining places, and also tweaking some functionality based on this very constructive feedback. Here are highlights of those tweaks and improvements:
It’s been two weeks since the release of RAML 1.0 (RC), the new raml.org website, and the API Workbench; all been very well received in the community. A lot happened in this two weeks, so let me share some details on the release and quotes we had from the community on different channels.
It's a big day for RAML. We're excited to announce the publication of the RAML 1.0 (RC) spec, as well as the launch of a gorgeous new RAML.org site. In addition, our community is now launching a set of brand new development tools that support RAML 1.0 as well as 0.8. Here's what you need to know.
What's new with RAML 1.0?
RAML has always been about making it easy for developers to manage the whole API lifecycle from design to implementation to operation and sharing. It's a concise, intuitive language for specifying APIs that allows developers to only write what they need to define an API, drawing from and contributing to commonly-used patterns, such as the YAAS (SAP hybris) pattern library.
We’re about to finalize the next version of RAML. Last month we published the result of many months of community feedback, development modeling, and API analysis, in which we figured out how a rather small number of changes in RAML 1.0 (relative to its predecessor, RAML 0.8) could result in dramatic improvements to the modeling capabilities. The list resolves some gaps, enhances capabilities, and maintains the simplicity of RAML. This month, that list will turn into RAML 1.0.
Why so few changes?
I am really happy to post a new article in our category [Guest Posts]. This time, Kai Spichale talks a little bit about the API first approach with RAML. I hope you will enjoy his article and thank you Kai for contributing!
There is no standard to describe REST APIs but different formats and best practices emerged over time and profited from the experiences of their respective predecessors. The latest addition to this series is RAML, a "RESTful API Modeling Language" that is discussed in this article as an important tool for API First Development.
Hi @all, we are proud to announce that we were able to add a couple of new projects to our list. Check them out on: raml.org/projects.html Here an overview:
Currently we are compiling a series of guest posts where we ask happy RAML user to tell their stories about how they are using RAML, or their tools they developed and contributed to the RAML community. In our very first post in this series, I am happy to have ePages to talk about their experience and the tool they developed. If you want to talk about your story or tool, why not sending us an email to email@example.com.
Today, InfoQ released an interview with Uri Sarid, the founder of the RAML project. Uri is talking about the current status of the project, the new sponsorship of the Swagger project from SmartBear, and also scratches a little bit on RAML 1.0. Enjoy the full interview here.
MuleSoft has released a couple of new key features around their Anypoint Platform offering in February 2015. One in particular is interesting for the RAML community. The RAML console got a refreshed UI as well as new features which I will briefly explain here.Before we start, for everyone who does not know the console, let’s have a quick overview of it. The RAML console is an open source application and gives you a graphical insight of your API specification. It lists all resources and by clicking on the attached HTTP verbs on a specific resource you will be able to deep dive into the resource details. The detail page features a general description, descriptions of every possible HTTP status, examples and schemas on the response’s and/or request’s body, and other aspects you defined in your RAML specification.So what really is new? As I said - the UI was completely refreshed and got a more modern look & feel.