Changes between Version 37 and Version 38 of NDL-OWL

Show
Ignore:
Timestamp:
02/17/11 00:24:24 (8 years ago)
Author:
ibaldin (IP: 173.142.203.126)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v37 v38  
    1 We describe the models in the life cycle of resource reservations and the resource allocation policy and stitching workflow implementation.  
     1= NDL-OWL implementation in ORCA = 
     2 
     3We describe the models in the life cycle of resource reservations and the resource allocation policy and stitching workflow implementation. The implementation details refer to the Camano generation of ORCA code. 
    24 
    35= A. Models =  
    46 
    5 We need a set of unified semantic schemas for representing the data models needed in the life circle of resource reservation. We develop NDL-OWL - an extension of the [http://www.science.uva.nl/research/sne/ndl Network Description Language] using OWL.  We use a number of [wiki:OrcaNDL tools] to create and manipulate NDL-OWL ontologies. We are trying to stay away from the procedural programming model to a semantic query based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications. 
     7We need a set of unified semantic schemas for representing the data models needed in the life circle of resource reservation. We develop NDL-OWL - an extension of the [http://www.science.uva.nl/research/sne/ndl Network Description Language] using OWL.  We use a number of [wiki:OrcaNDL tools] to create and manipulate NDL-OWL ontologies. We deliberately stay away from the procedural programming model in favor of a more flexible semantic query-based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications. 
    68 
    7 There are at least 5 types of models to be defined, that are circulated among the site authorities, broker and service manager. 
     9There are at least 5 types of models to be defined, that are circulated among the ORCA actors (authorities, broker and service manager).  
    810 
    911== 1. Substrate description model == 
    10 This is the substrate specific detailed resource and topology model that is used by the substrate manager to describe its physical resource including edge (compute and storage) resource and network topology. It also describes the domain service exposed to the broker.  
    11  '''a. Domain Service Description(domain.owl)'''  
     12This is the substrate-specific detailed resource and topology model that is used by the owner of the substrate to describe its physical resources including edge (compute and storage) resource and network topology. It also describes the domain services exposed to the broker(s).  
     13 '''a. Domain Service Description ([src:domain.owl)'''  
    1214      The class hierarchy is defined in the diagram below. A substrate (domain) is defined as a collection of !PoPs. Each PoP, with a geographical location, is a collection of network devices and/or data center. The Class domain also has a property ''!NetworkService'' which could have a number of ''!ServiceElement''. This information would be passed to the advertisement RDF. 
    1315             * !AccessMethod: e.g. ORCAActor, or GENI AM API.