Changes between Version 28 and Version 29 of GENIExperimenter/RSpecs


Ignore:
Timestamp:
05/14/12 17:06:23 (12 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/RSpecs

    v28 v29  
    1 '''UNDER CONSTRUCTION'''
    21[[PageOutline]]
    3 In order to truly 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.
     2In 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.
    43The schemas support Aggregate or resource specific extensions. [wiki:GeniRspec Ongoing work] covers agreeing upon ontologies for other resource types.
    54
    … …  
    3433If you write your own RSpecs, then you can use [https://www.protogeni.net/trac/protogeni/wiki/RSpecDebugging rspeclint] to verify the validity of the document. `rspeclint.py` is a script written in python
    3534that will check the validity of an xml document against its schema.
     35
     36''' For comments and corrections on this page please [mailto:help@geni.net mail us].