ALPS ASD (app-state-diagram) 0.3.6 has been released. You can import parts of other application designs online to structure your REST application design. (internet taxonomy !) #HypemediaAPI#ALPS
https://t.co/MrFWxoDzK7
huh! i was today-years-old when i learned that the ASD tool supports markdown within the DOC elements of ALPS profiles.
how did i not know this!?!?!?!
sweet!
@koriym@alps_io
- repo: https://t.co/6Zd3tWKD2k
- ASD tool: https://t.co/x9DBI5F9zB
BEAR.ApiDoc generates API documents from phpdoc/method signatures/JSON schema/ALPS profile combo. Not only saves you the trouble of writing IDL, but also allows you to generate accurate documentation. #automagic https://t.co/5tmWYBXVyj
Review of ALPS https://t.co/3hbo78jCGI by Kristopher Sandoval (https://t.co/JNnP6rGCgw) @nordicapis
"Today, we’re going to look at ALPS and outline its core features. We’ll also look at the new open-source ALPS Unified Utility..." @alps_io#hypermedia#API360#APIDesign
the latter part of the week, I came across this #ASC2020 talk by @mamund on multi-paradigm API specification https://t.co/1AZguUliCN, which is more toward the design-first end of the API implementation spectrum
ALPS Unified Utility on #substack
https://t.co/SujwJqsEF0
"I’ve opened up a stand-alone public repository on github for my Design-First API utility called `unified'."
@alps_io@greatwebapis#APIDesign#API360
“Program to an interface, not an implementation.” -- from "Design Patterns by Gamma", et al, 1992
API consumer apps should program to an @ALPS_io semantic profile, not an OpenAPI @OpenApiSpec document.
"What We Need To Be Machine Readable At API Run Time" -- @kinLane https://t.co/2SHIFxpWVd
"How do we distill down the essential ingredients of API consumption into a single, machine readable unit that can be automated into what Mike Amundsen calls, 'find and bind'?"
i have known @mamund for some time. one of those people who has helped me think of the larger context about APIs and their scope. https://t.co/JfvTzUpPc2