<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for mamund</title><link>http://disqus.com/by/mamund/</link><description></description><atom:link href="http://disqus.com/mamund/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 27 Dec 2017 12:42:55 -0000</lastBuildDate><item><title>Re: My Year In Review From A to Z</title><link>http://wvxu.org/post/my-year-review-z#comment-3680389541</link><description>&lt;p&gt;love this piece. thanks for all the good work!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 27 Dec 2017 12:42:55 -0000</pubDate></item><item><title>Re: Hypermedia API vs complex processes - Tomasz Pluskiewicz</title><link>http://t-code.pl/blog/2015/12/hypermedia-maturity-model/#comment-2417782816</link><description>&lt;p&gt;Nice blog post. I gave a talk earlier this year that identifies some common patterns that can be used to cover the last two levels in your model. &lt;a href="http://amundsen.com/talks/2015-08-qcon-rio/index.html" rel="nofollow noopener" target="_blank" title="http://amundsen.com/talks/2015-08-qcon-rio/index.html"&gt;http://amundsen.com/talks/2...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Transcript/Recording is not available yet, but the slides will give you the basic idea.&lt;/p&gt;&lt;p&gt;Would be interested in your comments/feedback on what I posted there.&lt;/p&gt;&lt;p&gt;cheers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Sat, 19 Dec 2015 17:40:54 -0000</pubDate></item><item><title>Re: Service Discovery, The Easy Way</title><link>http://www.bizcoder.com/service-discovery-the-easy-way#comment-2234423490</link><description>&lt;p&gt;&amp;lt;snip&amp;gt;&lt;br&gt;web browsers that use a link to discover a service for searching.&lt;br&gt;&amp;lt;/snip&amp;gt;&lt;br&gt;if that's the discovery you have in mind, i don't think i have anything else to add here.&lt;/p&gt;&lt;p&gt;cheers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 03 Sep 2015 14:24:26 -0000</pubDate></item><item><title>Re: Service Discovery, The Easy Way</title><link>http://www.bizcoder.com/service-discovery-the-easy-way#comment-2234330375</link><description>&lt;p&gt;rel="search" -- is that what this blog post is about?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 03 Sep 2015 13:52:27 -0000</pubDate></item><item><title>Re: Service Discovery, The Easy Way</title><link>http://www.bizcoder.com/service-discovery-the-easy-way#comment-2234260578</link><description>&lt;p&gt;not to put too fine a point on it but what you describe here is service *usage*, not discovery. the website _uses_ services. the human already *discovered* the website back in the past and _uses_ a bookmark (or typing skills) to return to that site.&lt;/p&gt;&lt;p&gt;there is no need for the website to _force_ humans to "discover" the CDN, ad-providers, etc. since the website has that handled. and most of our API implementations are like that, too. we do't do any runtime discovery at all.&lt;/p&gt;&lt;p&gt;so, we don't need to create  "discovery service" for what you describe since *there is no discovery going on at all.*&lt;/p&gt;&lt;p&gt;no, if you really wanted to engage in discovery...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 03 Sep 2015 13:39:21 -0000</pubDate></item><item><title>Re: Five Years Of API Evangelist</title><link>http://apievangelist.com/2015/07/03/five-years-of-api-evangelist/#comment-2115615103</link><description>&lt;p&gt;+100 all the way. thanks for all you do.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Fri, 03 Jul 2015 19:43:58 -0000</pubDate></item><item><title>Re: What is ALPS?</title><link>http://apievangelist.com/2015/03/10/what-is-alps/#comment-1902151607</link><description>&lt;p&gt;Anthony:&lt;/p&gt;&lt;p&gt;Mark Foster is the key driving force on this spec right now. he has the most hands-on experience implementing it and is doing quite a bit to improve the spec in general. it's great working w/ him on it.&lt;/p&gt;&lt;p&gt;hope to see you on the list, too!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 11 Mar 2015 18:00:47 -0000</pubDate></item><item><title>Re: What's a link?</title><link>http://evertpot.com/whats-in-a-link/#comment-1900256176</link><description>&lt;p&gt;if you start pursuing a hypermedia-style route, be sure to post to the hypermedia-web list. lots of smart folks there who can offer feedback.&lt;/p&gt;&lt;p&gt;cheers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 10 Mar 2015 20:49:26 -0000</pubDate></item><item><title>Re: What's a link?</title><link>http://evertpot.com/whats-in-a-link/#comment-1900132060</link><description>&lt;p&gt;no problem. love what you're working on here.&lt;/p&gt;&lt;p&gt;i did something a bit dff several years ago by focusing on a higher-level abstraction of links and forms -- H-Factors. &lt;br&gt;&lt;a href="http://amundsen.com/hypermedia/hfactor/" rel="nofollow noopener" target="_blank" title="http://amundsen.com/hypermedia/hfactor/"&gt;http://amundsen.com/hyperme...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;the idea is to identify common actions within media-types and give them a name. most all media types support the LO factor (link-outbound) and few support the LI factor (idempotent write). and so forth.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 10 Mar 2015 19:19:30 -0000</pubDate></item><item><title>Re: What's a link?</title><link>http://evertpot.com/whats-in-a-link/#comment-1900117292</link><description>&lt;p&gt;check out Stephen Mizell's HyperDescribe project: &lt;a href="http://smizell.com/weblog/2014/converting-between-hypermedia-types" rel="nofollow noopener" target="_blank" title="http://smizell.com/weblog/2014/converting-between-hypermedia-types"&gt;http://smizell.com/weblog/2...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;I think you two may be working toward a similar goal.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 10 Mar 2015 19:09:27 -0000</pubDate></item><item><title>Re: What is ALPS?</title><link>http://apievangelist.com/2015/03/10/what-is-alps/#comment-1899645924</link><description>&lt;p&gt;Kin:&lt;/p&gt;&lt;p&gt;Thanks for the shout-out on ALPS. I should point out that ALPS is a joint effort I am working on w/ Mark Foster of Apiary and is based on ideas initially worked out w/ Leonard Richardson (Richardson Maturity Model, RESTful Web Services, RESTful Web APIs, etc.).&lt;/p&gt;&lt;p&gt;As you can tell from the thread you're watching, there is still quite a bit of work to be done to make ALPS useful and I am always willing to talk w/ folks about it anytime, anywhere. Anyone interested in helping us sort this out and make it better can visit &lt;a href="http://alps.io" rel="nofollow noopener" target="_blank" title="http://alps.io"&gt;http://alps.io&lt;/a&gt; and find links to the current IETF Draft, the repo and discussion list.&lt;/p&gt;&lt;p&gt;Thanks for putting us in your radar!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 10 Mar 2015 15:49:28 -0000</pubDate></item><item><title>Re: The Machine Readable Questions We Should Ask Of Terms Of Service</title><link>http://apivoice.com/2014/06/04/the-machine-readable-questions-we-should-ask-of-terms-of-service/#comment-1420173402</link><description>&lt;p&gt;would be interesting to see how many of the keywords in tosdr can be matched to keywords in other dictionaries/registries such as &lt;a href="http://www.iana.org/assignments/link-relations/" rel="nofollow noopener" target="_blank" title="http://www.iana.org/assignments/link-relations/"&gt;http://www.iana.org/assignm...&lt;/a&gt;,  &lt;a href="http:schema.org" rel="nofollow noopener" target="_blank" title="http:schema.org"&gt;http:schema.org&lt;/a&gt;, &lt;a href="http://microformats.org" rel="nofollow noopener" target="_blank" title="microformats.org"&gt;microformats.org&lt;/a&gt;, and &lt;a href="http://dublincore.org" rel="nofollow noopener" target="_blank" title="dublincore.org"&gt;dublincore.org&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 04 Jun 2014 20:35:18 -0000</pubDate></item><item><title>Re: I have a voice</title><link>http://ngoding.co/code/i-have-a-voice/#comment-1390034601</link><description>&lt;p&gt;initial spec for OPTIONS was very loose. to prevent future problems, it was marked no-cache and there we are. unable to "undo" a contract promise here in the future, we are living we/ the outcome. it's not the first/only regret on the initial HTTP design, but hey...&lt;/p&gt;&lt;p&gt;that's why relying on OPTIONS as the avenue for describing hypermedia controls is a bad idea. use the message body. if you refuse to include controls in your initial response, you need to get used to the idea of asking for additional GETs in order to find out what's possible. HTML, Collection+JSON, Siren, all accept this reality and return controls in the initial body.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Fri, 16 May 2014 19:13:57 -0000</pubDate></item><item><title>Re: Hello World Product API With Blueprint, RAML And Swagger</title><link>http://apievangelist.com/2014/03/08/hello-world-product-api-with-blueprint-raml-and-swagger/#comment-1279726018</link><description>&lt;p&gt;np. we can discuss when we're together in Amsterdam for #APIStrat later this month.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 11 Mar 2014 03:16:09 -0000</pubDate></item><item><title>Re: Hello World Product API With Blueprint, RAML And Swagger</title><link>http://apievangelist.com/2014/03/08/hello-world-product-api-with-blueprint-raml-and-swagger/#comment-1277915148</link><description>&lt;p&gt;nice post. FWIW, i threw together a version of the "Product API" using ALPS. maybe we can talk about it sometime: &lt;a href="https://gist.github.com/mamund/9443276" rel="nofollow noopener" target="_blank" title="https://gist.github.com/mamund/9443276"&gt;https://gist.github.com/mam...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Sun, 09 Mar 2014 17:17:37 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193332600</link><description>&lt;p&gt;always trying to learn...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 09 Jan 2014 01:44:24 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193292799</link><description>&lt;p&gt;"as part of the content type"...&lt;/p&gt;&lt;p&gt;what does Fielding mean when he says:&lt;br&gt;"A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state, or in defining extended relation names and/or hypertext-enabled mark-up for existing standard media types."&lt;/p&gt;&lt;p&gt;BTW - your version of the above was:&lt;br&gt;"Automated agents are dependent on their understanding of the media types, link types, or microformat extensions provided in representations."&lt;/p&gt;&lt;p&gt;specifically, i am asking you what he means when he lists three things: "media types", "extended relation names", and "hypertext-enabled markup." why three? are they all (as you assert here) "part of the content type"?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 09 Jan 2014 00:34:02 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193280141</link><description>&lt;p&gt;from the top of this thread:&lt;br&gt;"using HTML is RESTful"&lt;br&gt;and now you say:&lt;br&gt;"I don't think it's possible to implement a domain-specific API that is RESTful using HTML."&lt;/p&gt;&lt;p&gt;i got that right?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 09 Jan 2014 00:13:37 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193274634</link><description>&lt;p&gt;OK, try this:&lt;br&gt;"If someone wanted to create an API for ecommerce would they not need a "place-order" URL? That's why I'm saying I don't think it's possible to implement a domain-specific API that is RESTful using HTML"&lt;/p&gt;&lt;p&gt;Is that a true statement?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Thu, 09 Jan 2014 00:05:06 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193269049</link><description>&lt;p&gt;@MikeSchinkel&lt;/p&gt;&lt;p&gt;"use the place order URL"? you're joking right? there is no such thing in Cj. links and forms in Cj work exactly the same as links and forms in HTML.&lt;/p&gt;&lt;p&gt;for example:&lt;br&gt;HTML: &amp;lt;a href="..." rel="alternate"&amp;gt;...&amp;lt;/a&amp;gt; &lt;br&gt;works *exactly* the same as &lt;br&gt;Cj: {link:{href:"..." rel:"alternate" prompt="..."}}&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 08 Jan 2014 23:56:33 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193252634</link><description>&lt;p&gt;@MikeSchinkel:&lt;br&gt;&amp;lt;snip&amp;gt;&lt;br&gt;"Cj Browsers" cannot know how to process all potential links.&lt;br&gt;&amp;lt;/snip&amp;gt;&lt;/p&gt;&lt;p&gt;you've not actually tried to implement a Cj app have you?&lt;/p&gt;&lt;p&gt;in fact, all the HTTP protocol details are defined and immutable in Cj. and yes, "Cj Browsers" *always* know how to process potential links - without the need to refer to human readable documentation.&lt;/p&gt;&lt;p&gt;Just like a compliant HTML browser can work with any server that emits valid HTML representations, a compliant Cj browser can work with any server that emits valid Cj.&lt;/p&gt;&lt;p&gt;BTW - this is not true for HAL. it's important not to  conflate their design goals or implementation requirements.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 08 Jan 2014 23:33:09 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193205121</link><description>&lt;p&gt;HTML is a generic media type and yet you say HTML is RESTful and Cj is not. What, in the definition of HTML is different from Cj that makes this so?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 08 Jan 2014 22:56:44 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193175500</link><description>&lt;p&gt;@MikeSchinkel:&lt;/p&gt;&lt;p&gt;you mean if Cj didn't have 6.5 it'd be RESTful?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 08 Jan 2014 22:31:42 -0000</pubDate></item><item><title>Re: What Is A Hypermedia API?</title><link>http://apievangelist.com/2014/01/07/what-is-a-hypermedia-api/#comment-1193129928</link><description>&lt;p&gt;@MikeSchinkel:&lt;/p&gt;&lt;p&gt;HTML is RESTful and HAL and Cj are not? &lt;br&gt;- why is cj.template *not* RESTful and HTML.FORM is RESTful?&lt;br&gt;- why is &lt;a href="http://cj.link" rel="nofollow noopener" target="_blank" title="cj.link"&gt;cj.link&lt;/a&gt;@embed="true" *not* RESTful and HTML.IMG is RESTful?&lt;/p&gt;&lt;p&gt;and why is "application/invoice" RESTful?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Wed, 08 Jan 2014 21:37:27 -0000</pubDate></item><item><title>Re: Will Internet of Things And The SDK Push Out REST?</title><link>http://apievangelist.com/2014/01/07/will-internet-of-things-and-the-sdk-push-out-rest/#comment-1191545661</link><description>&lt;p&gt;Always good to 'talk' w/ you. Looking forward to APIStrat Amsterdam, too. Cheers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Amundsen</dc:creator><pubDate>Tue, 07 Jan 2014 20:42:38 -0000</pubDate></item></channel></rss>