Changes between Version 50 and Version 51 of GENIExperimenter/RSpecs

Timestamp:

05/15/12 13:00:44 (12 years ago)

Author:

nriga@bbn.com

Comment:

--

GENIExperimenter/RSpecs

@@ -1 +1 @@
 [[PageOutline]]
+= Resource Specification (RSpec) Documents in GENI =
 In order to allow interoperability among different Aggregate Managers(AMs), GENI requires a common language for describing resources, resource requests, and reservations. GENI now uses standardized  Request Specification (RSpec) documents which are XML documents following agreed schemas to represent resources. 
 The schemas support Aggregate or resource specific extensions. [wiki:GeniRspec Ongoing work] covers agreeing upon ontologies for other resource types.
 
-= RSpec Types =
+== RSpec Types ==
 In GENI there are three different types of RSpec, each used to describe resources when communicating with an AM. The communication with an AM, is based 
-on the common [wiki:GAPI_AM_API_V2#APIMethods GENI AM API] that requires from AMs to use [wiki:GAPI_AM_API_V3/CommonConcepts#RSpecdatatype RSpec data types] to communicate.
+on the common [wiki:GAPI_AM_API_V2#APIMethods GENI AM API] that requires AMs to communicate using [wiki:GAPI_AM_API_V3/CommonConcepts#RSpecdatatype RSpec data types].
 
 [[Image(rspec-types.png, 60%)]]
@@ -12 +13 @@
  This is the document that is returned by an AM that describes the resources that the AM has.
 ==== Request RSpec ====
-This is the document that a user sends to an AM to describe the resources that he wants to reserve.
+ This is the document that a user sends to an AM to describe the resources that he wants to reserve.
 ==== Manifest RSpec ====
  This is the document returned by an AM tha describes the resources that a user has at an AM.