I prefer the term "protocol". It encompasses the medium, the format, the expectations/assumptions and the potential dialog among the participants.
On Sun, May 5, 2013 at 11:22 AM, Owen Densmore <[email protected]> wrote: > Agreed. In unix command line pipe terms, the API is the > goes-into-goes-outof (gozintagozouta) GIGO? for the library. This is how > Sun engineers talked with management about new projects and indeed became a > buzzword. > > TL;DR > > Actually, if you include the unix command arguments, you get a lovely > example of a Turing model: input, state, output. > > > -- Owen > > > On Sat, May 4, 2013 at 5:22 PM, Arlo Barnes <[email protected]> wrote: > >> For either phrase, either assume your audience knows what you are talking >> about or define the terms before you go on. Explain that it is like a >> control panel you can receive data from and send instructions through, and >> being so generally defined does not go into details of implementation. >> -Arlo James Barnes >> >> ============================================================ >> FRIAM Applied Complexity Group listserv >> Meets Fridays 9a-11:30 at cafe at St. John's College >> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com >> > > > ============================================================ > FRIAM Applied Complexity Group listserv > Meets Fridays 9a-11:30 at cafe at St. John's College > to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com >
============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
