- Original Message -
I like this idea. I'd also propose that the format of the specification be
something machine-readable, such as API-Blueprint (a simple subset of
markdown, apiblueprint.org , also what apiary uses, if you've ever seen
that) or RAML (a more structured YAML-based
- Original Message -
On Sat, Nov 2, 2013 at 4:55 PM, Christopher Armstrong
chris.armstr...@rackspace.com wrote:
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development
will be the consensus building and stabilization of the Solum API
specification. A solid API spec aid in the speeding up the pace of
Jay,
On Nov 2, 2013, at 2:39 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development
will be the consensus building and stabilization of the Solum API
specification. A solid API spec aid in the speeding up the pace of
+1 - with the level of interest among existing vendors I think this will help
others who want to be API compatible with Solum (above and beyond normal
benefits)
On Nov 2, 2013, at 5:48 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages
+1 Couldn't agree more.
Christopher Armstrong chris.armstr...@rackspace.com wrote:
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development will
be the consensus building
