Mike Amundsen

spec is "floaty" but will def mark an internal v change for you. ​

pretty sure this is what appears in the proposed templates doc, right? all URIs are RFC6570 templates [1] `model` is for simple bodies (your L1)[2] `templates` is for complex write...

IMO, it is overkill to REQUIRE the use of `` for cases that are easily handled by RFC6570 form-style templates such as: `p={personid}` -> `p=123` or `c={list)` -> `c=red,green,blue` or...

again, we're on the same page, just working out how to get to the end. TBH, specs can only encourage or discourage behavior. we're on the Internet and expecting to...

@ciaranj Thanks for the pull request. Yes, I messed up and failed to work up package files. I'm at OSCON this week, but hope to review this in a day...

@aminya thanks for the interest. the `src` folder in this repo has all the code (it's just an `index.js` file for nodejs) along with some examples. i will create a...

good catch, @corntoole.

> Descriptors for state transitions should use camel-case; data descriptors should use camel-case or snake-case as appropriate. I assume this is "best/oreferred practice" for proto files, right? any chance you...

@corntoole: very good. thanks for the great proto styleguide reference![1] so, for `.proto` files we'll use upper camel case (aka Pascal case[2]) for `MessageNames`, `ServiceNames`, and `MethodNames`. Then snake case...

@corntoole: added a branch w/ your suggested changes: https://github.com/mamund/alps-unified/pull/13 can you check this out and add remarks? if all is good, i'll do the merge when you're ready.