1 / 7

Proposal from Randy (May 31)

packageDescriptor. packageIdentity files * ds:SignatureType ? deploymentDesciptor ?. Proposal from Randy (May 31). Legend: • ` ? ' denotes optionality (i.e. zero or one occurrences, 0..1), • `*' denotes zero or more occurrences, i.e. 0..*, • `+' one or more occurrences, i.e. 1..*.

netis
Download Presentation

Proposal from Randy (May 31)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. packageDescriptor packageIdentity files * ds:SignatureType ? deploymentDesciptor ? Proposal from Randy (May 31) Legend: • `?' denotes optionality (i.e. zero or one occurrences, 0..1), • `*' denotes zero or more occurrences, i.e. 0..*, • `+' one or more occurrences, i.e. 1..* 2. “location” is added (optional) 3. Signature is added (optional) Choice is provided 4. Choice is provided Descrptor is split into two 1. Descriptor is split into two Good progress! …but some information in AAD is missing. deploymentDescriptor CDL topology content groups * features * requisites * More on ACS alignment proposal

  2. Application Archive Subscribe requests Notify response contents Application Repository Application Consumer Application Producer What is ACS? From the presentation at May F2F meeting • Specification for the ACS repository. • ACS: Application Contents Service • Application Contents Repository Interface (ARI) • WSRF interface for ACS repository to create, retrieve, update and delete archives in the repository • Application Contents Archive Format (AAF) • Information schema for repository operationsfor contents in an archive. Information for lifecycle operations is presented in contents in a archive. Requires the following element and attribute: /DifferentialAAD/AAID/BaseVersion /DifferentialAAD/Contents/Content/@operation More on ACS alignment proposal

  3. The choices • Put them into the packageDescriptor as optional element and attribute:     /packageDescriptor/packageIdentity/baseVersion     /packageDescriptor/Files/File/@operation • Place <xsd:any> in two places and let the revised ACS spec provide normative description and schema for their usage. The SDD describes that the implementation MAY ignore the portion for the <xsd:any> under certain circumstances. For example, the SDD should specify that any extension element MUST have “mayIgnore=true|false” attribute. More on ACS alignment proposal

  4. packageDescriptor packageIdentity files * ds:SignatureType ? deploymentDesciptor ? Proposal from Keisuke (Jun 7) Legend: • `?' denotes optionality (i.e. zero or one occurrences, 0..1), • `*' denotes zero or more occurrences, i.e. 0..*, • `+' one or more occurrences, i.e. 1..* Put “<xsd:any>” here! “aaf2:/BaseVersion” would be specified by ACS 2.0 Put “<xsd:any>” here! “aaf2:/@operation” would be specified by ACS 2.0 More on ACS alignment proposal

  5. packageDescriptor packageIdentity files * ds:SignatureType ? deploymentDesciptor ? And question (Jun 7) Legend: • `?' denotes optionality (i.e. zero or one occurrences, 0..1), • `*' denotes zero or more occurrences, i.e. 0..*, • `+' one or more occurrences, i.e. 1..* Put “<xsd:any>” here! “aaf2:/BaseVersion” would be specified by ACS 2.0 Put “<xsd:any>” here! Do we need to describe about the usage of <xsd:any> in SDD specification? “aaf2:/@operation” would be specified by ACS 2.0 More on ACS alignment proposal

  6. If we have extension point • The single SDD schema can be used for SDD implementation and ACS repository implementation • A Package Descriptor to be processed by ACS implementation can be read by SDD implementation • as long as all extension elements have “mayIgnore=true” attribute • A Package Descriptor to be processed by SDD implementation can be read by ACS implementation Interoperable at the basic level (Identity, list of files) SDD PackageDescriptor ACS AAD • This tiny schema is used to process the below information: • aaf2:/BaseVersion • aaf2:/@operation Valid Valid SDD PackageDescriptor Schema with <xsd:any> ACS AAD Schema More on ACS alignment proposal

  7. If we just have two separate schema • Two separate schema: SDD and AAF • Each package descriptor requires to be validated against separate schema with separate namespace. • AAF can import SDD schema, but the Package Descriptor itself is no longer valid for SDD schema. (It’s valid for AAF) • Only the text description in both specification associate two schema, but ambiguous at what is mandated. No interoperability by default SDD PackageDescriptor Invalid ACS AAD Valid Valid SDD PackageDescriptor Schema w/o <xsd:any> ACS AAD Schema More on ACS alignment proposal

More Related