- From: Daniel Harris <daniel@kendra.org.uk>
- Date: Sat, 14 Feb 2015 15:55:06 +0000
- To: public-social-interest@w3.org
Hello All, 1. I'm not 'in' the SocialWG so I'll make my comments here regarding the discussion that took place at: http://lists.w3.org/Archives/Public/public-socialweb/2015Feb/thread.html#msg99 "2 APIs and the charter" 2. Also this relates to my questions, about formal processes/methodologies for protocol/API creation, in: http://www.w3.org/2015/02/11-socialig-minutes.html See around "dahacouk: is there a formal way to derive them down to something simple ?" Where "them" is referring to use cases / user stories. Firstly, I don't see any formal process/methodology/tool being used for protocol/API creation. Are there any around? Are there any collaboration like systems that are specifically designed for creating protocols/APIs? I don't mean the technical end, yet. I mean how we get to the technical end. How do we distill down a big list of user stories which will then inform requirements? Any pointers would be most welcome to formal processes. Secondly, pointing at the discussion in the SocialWG regarding "2 APIs and the charter"... I'm confused as to how the number and type of protocols/APIs could be defined before there has even been a confirmed set of use cases / user stories defined. Surely the use cases / user stories should dictate everything? Anyway, I do feel that formal methodology for protocol/API creation would greatly enhance our efficiency in this work. Any pointers? Cheers Daniel
Received on Saturday, 14 February 2015 15:55:42 UTC