Arbitrary and Cascading Operations

Slides:



Advertisements
Similar presentations
GML Dev Days, July 2002 Working with GML Application Schemas Milan Trnini}, Galdos Systems, Inc.
Advertisements

Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 5 More SQL: Complex Queries, Triggers, Views, and Schema Modification.
A centre of expertise in digital information management UKOLN is supported by: XML and the DCMI Abstract Model DC Architecture WG Meeting,
1 Web Data Management XML Schema. 2 In this lecture XML Schemas Elements v. Types Regular expressions Expressive power Resources W3C Draft:
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 5 More SQL: Complex Queries, Triggers, Views, and Schema Modification.
CL2 Proposal #9: Mapping requirements to requisites.
UML – Class Diagrams.
Database Systems More SQL Database Design -- More SQL1.
SDD Schema Documentation Preliminary Thoughts Howard Abrams – CA, Inc.
XACML OASIS eXtensible Access Control Markup Language Steve Carmody July 10, 2003 Steve Carmody July 10, 2003.
Lecture Roger Sutton CO530 Automation Tools 5: Class Libraries and Assemblies 1.
OOPSLA 2003 DSM Workshop Diagram Definition Facilities Based on Metamodel Mappings Edgars Celms, Audris Kalnins, Lelde Lace University of Latvia, IMCS,
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
CSE314 Database Systems More SQL: Complex Queries, Triggers, Views, and Schema Modification Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
#N14 Pattern Value (aka Substring attribute) SDD 1.1 Proposal.
Introduction to XML. XML - Connectivity is Key Need for customized page layout – e.g. filter to display only recent data Downloadable product comparisons.
Display Text SDD 1.1 Topic. Current Situation COSMOS team is implementing a CLI for user interaction Need the ability to specify strings for display to.
CL1 Proposal Redefine “install”. Add update artifact. Remove inconsistencies introduced by “baseUninstall” package type.
Proposal for some suggested changes Draft 0.2 Weijia (John) Zhang Dell Inc.
Web Architecture: Extensible Language Tim Berners-Lee, Dan Connolly World Wide Web Consortium 元智資工所 系統實驗室 楊錫謦 1999/9/15.
Human-readable SDD Content Debra Danielson CA. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos.
Display Text SDD 1.1 Topic. Current Situation COSMOS team is implementing a CLI for user interaction Need the ability to specify strings for display to.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
Sheet 1XML Technology in E-Commerce 2001Lecture 2 XML Technology in E-Commerce Lecture 2 Logical and Physical Structure, Validity, DTD, XML Schema.
IETF 57, Vienna1 SDPng Update Dirk Jörg Carsten draft-ietf-mmusic-sdpng-06.txt.
ImplementedBy SDD 1.1 Proposal. Current Situation SDD runtime “walks” resources in topology Resources are cataloged and cross referenced w/ profile(s)
CL2 Localization Proposal No CL2 issue # assigned.
Node Type Implementations How does Required Container Feature interact with Artifact Type? It seems that any given implementation will be based on artifacts.
PRACTICAL KNOWLEDGE REPRESENTATION FOR THE WEB Frank van Harmelen Dieter Fensel AIFB Kim Kangil Structural Complexity Laboratory.
N. HARIKA Lecturer(csc). 3 General Structure Of A Java Program.
IETF 54, Yokohama Kutscher/Ott/Bormann 1 SDPng Update Dirk Jörg Carsten draft-ietf-mmusic-sdpng-05.txt.
#D8 Specification v1.0 Erratum #1 SDD 1.1 Proposal.
Proposal for Property/Response Files reference and value substitutions Draft 0.2 Weijia (John) Zhang Dell Inc.
“Custom” Checks/Constraints/Actions A proposal for the OASIS SDD TC Rich Aquino, Macrovision Julia McCarthy, IBM March 1, 2007.
#N14 Pattern Value (aka Substring attribute) SDD 1.1 Initial Discussion XXX = [Proposal | Initial Discussion | General Direction Proposal]
Chapter 29. Copyright 2003, Paradigm Publishing Inc. CHAPTER 29 BACKNEXTEND 29-2 LINKS TO OBJECTIVES Attach an XML Schema Attach an XML Schema Load XML.
Proposal for Property/Response Files reference and value substitutions Draft 0.3 Weijia (John) Zhang Dell Inc.
Deployment Diagram.
More SQL: Complex Queries, Triggers, Views, and Schema Modification
More SQL: Complex Queries,
IBM Rational Rhapsody Advanced Systems Training v7.5
Customizing custom.
Deployment Diagram.
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Eugenia Fernandez IUPUI
Software Architecture & Design Pattern
HTML Tables CS 1150 Fall 2016.
Object-Oriented Design
SDD 1.1 General Direction Proposal
Keep it simple! - a Nordic view on technical simplification issues
Software Measurement Process ISO/IEC
Questions for Implementers Recommendation
Corresponds with Chapter 7
Semantic Marks A semantic mark is
Namespace Review 21-Nov-18.
Lec 3: Object-Oriented Data Modeling
CS134 Web Design & Development
Chapter 20 Object-Oriented Analysis and Design
More SQL: Complex Queries, Triggers, Views, and Schema Modification
Namespace Review 29-Dec-18.
Software Design Lecture : 15.
Session 2: Metadata and Catalogues
FUNCTION NOTATION AND EVALUATING FUNCTIONS
solution set (describes all values that make an equation true.)
Web Design & Development
Chapter 5 Understanding Requirements.
Design Yaodong Bi.
UTYPES Jonathan McDowell.
Views Base Relation View
Namespace Review 14-Oct-19.
Presentation transcript:

Arbitrary and Cascading Operations CL2 Issues #7 & #8

The Problem There is no way to know how the top-level operation is intended to map to operations on content elements and requisite packages. The semantics of features is problematic if an SDD supports multiple operations.

Proposed Solution: Limit CompositeInstallable elements to a single top-level operation. Restriction does not apply to CL1 SDDs. SDDs without a CompositeInstallable support all operations for which a corresponding artifact is defined. Individual content elements can support any operation and any artifact type needed to accomplish the top-level operation. All artifacts in scope for a particular deployment are used. This may be a temporary v1 restriction. Add operation attribute to ReferencedPackageType to identify the operation that should be applied to the package if it contains a CL1 SDD. If referenced package has a CL2 SDD, the single top-level operation is the one that will be used.

Schema changes: Add operation attribute to CompositeInstallableType <attribute name="operation" type="sdd-dd:OperationApplicabilityType" use="required"/> Add operation attribute to ReferencedPackageType <attribute name="operation" type="sdd-dd:OperationApplicabilityType" use=“optional"/> Interpretation: If the referenced package element points to an SDD with a CompositeInstallable element, the operation identified in the CompositeInstallable is performed if the referenced package is in scope. If the referenced package element points to an SDD without a CompositeInstallable, and Operation is specified by the referenced package, then perform that operation Operation is not specified by the referenced package, then perform the top-level operation of the referencing SDD.