Note that there are some explanatory texts on larger screens.

plurals
  1. POIs a Protocol based on an existing Protocol still a Protocol?
    primarykey
    data
    text
    <p>I am developing an open "protocol" for dynamic ridesharing services using mobile phones. It is based on XML-RPC and uses marshalled objects as parameters (quite like Soap).</p> <p>Every entity and operation will be heavily documented in the draft. As example, look at this first skeleton of a documented Prefs object to be used in the Protocol.</p> <hr> <p><strong>Prefs object</strong></p> <p>Stores the preferences of a Trip set by the Person who creates it [..]</p> <pre><code>Attribute Type Requirement age string MAY nonsmoking boolean MAY gender string MAY drive boolean MAY ride boolean MAY </code></pre> <ul> <li>Even if all attributes of Prefs objects are optional, objects of type Prefs MUST be provided when doing XML-RPC calls. In case of <strong>zero attributes</strong> provided, an empty object representend with an empty XML-RPC struct MUST be provided</li> <li><strong>gender</strong> <em>MUST</em> be any of the values <em>{'M', 'F', 'B'}</em>, meaning 'male', 'female' or 'both'</li> </ul> <p>The following is a valid Prefs object used in Protocol operations:</p> <pre><code>&lt;struct&gt; &lt;member&gt; &lt;name&gt;nonsmoking&lt;/name&gt; &lt;value&gt; &lt;boolean&gt;0&lt;/boolean&gt; &lt;/value&gt; &lt;/member&gt; &lt;member&gt; &lt;name&gt;gender&lt;/name&gt; &lt;value&gt; &lt;string/&gt; &lt;/value&gt; &lt;/member&gt; &lt;member&gt; &lt;name&gt;ride&lt;/name&gt; &lt;value&gt; &lt;boolean&gt;0&lt;/boolean&gt; &lt;/value&gt; &lt;/member&gt; &lt;member&gt; &lt;name&gt;drive&lt;/name&gt; &lt;value&gt; &lt;boolean&gt;0&lt;/boolean&gt; &lt;/value&gt; &lt;/member&gt; &lt;member&gt; &lt;name&gt;age&lt;/name&gt; &lt;value&gt; &lt;string&gt;18-40&lt;/string&gt; &lt;/value&gt; &lt;/member&gt; &lt;/struct&gt; </code></pre> <hr> <p>An operation using Prefs objects would have a complete description of an HTTP POST operation with all the details etc.</p> <p>Would you call this one a Protocol or still an API? I.e., if we write a Protocol which is based on another Protocol (in this case XML-RPC), is the derivative work a Protocol again?</p> <p>I would like to know that because I will talk about this in my bachelor thesis and I don't want to say something very stupid :)</p> <p>Thank you!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload