summaryrefslogtreecommitdiff
path: root/spore_implementation.pod
diff options
context:
space:
mode:
authorLars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <daxim@cpan.org>2011-03-13 01:38:24 +0100
committerfranck cuny <franck@lumberjaph.net>2011-03-17 08:57:57 +0100
commit918b4c7db839a64a9e812b2041ff1c092dd522cc (patch)
tree02098f8adc3321567403b4f9369b06d7ada17404 /spore_implementation.pod
parentspelling (diff)
downloadspore-specifications-918b4c7db839a64a9e812b2041ff1c092dd522cc.tar.gz
REST interfaces by definition cannot have out-of-band description documents
Diffstat (limited to 'spore_implementation.pod')
-rw-r--r--spore_implementation.pod5
1 files changed, 3 insertions, 2 deletions
diff --git a/spore_implementation.pod b/spore_implementation.pod
index 8218651..83f82e1 100644
--- a/spore_implementation.pod
+++ b/spore_implementation.pod
@@ -6,7 +6,8 @@ Spore (B<S>pecifications to a B<Po>rtable B<R>EST B<E>nvironment) Description Im
=head1 ABSTRACT
-Spore is a specification for describing REST API that can be parsed and used
+Spore is a specification for describing HTTP APIs which happen to suffice some
+constraints laid out by the REST architectural style. It can be parsed and used
automatically by client implementations to communicate with the described API.
This document describes what features are required in a Spore client
@@ -18,7 +19,7 @@ implementation.
=item API
-An I<API> is a REST application that can exchange data with client
+An I<API> is the interface to an application that can exchange data with client
applications over HTTP/HTTPS. It presents one or more method endpoints which
accept HTTP requests with varying headers, parameters and body content to
perform specific operations.