- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 30 Apr 2005 13:35:22 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv9472
Modified Files:
wsdl20.xml wsdl20.tex
Log Message:
Added Z Notation for {parent} property.
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.39
retrieving revision 1.40
diff -C2 -d -r1.39 -r1.40
*** wsdl20.tex 22 Apr 2005 06:51:33 -0000 1.39
--- wsdl20.tex 30 Apr 2005 13:35:20 -0000 1.40
***************
*** 1867,1870 ****
--- 1867,1891 ----
+ \hypertarget{zed-InterfaceParent}{}
+
+
+ An Interface component contains nested Interface Operation, Interface Fault, Feature, and Property components.
+ These components MUST have the Interface component as their parent.
+
+ Let $InterfaceParent$ express the constraints on the \{parent\} properties of the nested components of an Interface component:
+
+
+ \begin{schema}{InterfaceParent}
+ ComponentModel2
+ \where
+ \forall c : interfaceComps; if : interfaceFaultComps; io : interfaceOpComps; f : featureComps; p : propertyComps @ \\
+ \t1 if.id \in c.interfaceFaults \implies if.parent = c.id \land \\
+ \t1 io.id \in c.interfaceOperations \implies io.parent = c.id \land \\
+ \t1 f.id \in c.features \implies f.parent = c.id \land \\
+ \t1 p.id \in c.properties \implies p.parent = c.id
+ \end{schema}
+
+
+
\hypertarget{zed-InterfaceClosure}{}
***************
*** 2002,2006 ****
\item
-
An OPTIONAL \texttt{extends} \textit{attribute information item}
as described below in \hyperlink{Interface_extends_attribute}{\textbf{\ref*{Interface_extends_attribute} \texttt{extends} \textit{attribute information item}}}.
--- 2023,2026 ----
***************
*** 3906,3909 ****
--- 3926,3949 ----
+ \hypertarget{zed-FeatureRI}{}
+
+
+ The parent of a Feature MUST be in the component model.
+
+
+ Let $FeatureRI$ express this referential integrity constraint on the Feature component:
+
+
+ \begin{schema}{FeatureRI}
+ ComponentModel2
+ \where
+ \forall Feature | \theta Feature \in featureComps @ \\
+ \t1 ParentRI
+ \end{schema}
+
+ \begin{quote}\begin{small}See\begin{itshape} \hyperlink{zed-ComponentModel2}{ComponentModel2}, \hyperlink{zed-Feature}{Feature}, \hyperlink{zed-ParentRI}{ParentRI}.\end{itshape}\end{small}\end{quote}
+
+
+
\hypertarget{Feature_composition_model}{}
\subsubsection{Feature Composition Model}\label{Feature_composition_model}
***************
*** 4380,4385 ****
ComponentModel2
\where
! \forall x : propertyComps; y : ID @ \\
! \t1 x.valueConstraint = \{typeDefinitionId(y)\} \implies y \in typeDefIds
\end{schema}
--- 4420,4426 ----
ComponentModel2
\where
! \forall Property; y : ID | \theta Property \in propertyComps @ \\
! \t1 valueConstraint = \{typeDefinitionId(y)\} \implies y \in typeDefIds \land \\
! \t1 ParentRI
\end{schema}
***************
*** 4387,4391 ****
\begin{itemize}
! \item The Type Definition component of each Property component is contained in the component model.
\end{itemize}
--- 4428,4433 ----
\begin{itemize}
! \item If the value constraint of a Property component is a type definition, then the Type Definition component is contained in the component model.
! \item The parent of each Property component is contained in the component model.
\end{itemize}
***************
*** 5161,5164 ****
--- 5203,5207 ----
a message exchange of an operation will be formatted.
+
The properties of the Binding Fault component are as
follows:
***************
*** 7427,7431 ****
their \texttt{schemaLocation} \textit{attribute information item}s, such as a fragment identifier
(see \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]} 4.3.1). The semantics of such \textit{element information item}s are
-
governed solely by the XML Schema specification \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}.
Note: It is NOT an error to import two or more schemas from the same
--- 7470,7473 ----
***************
*** 9480,9483 ****
--- 9522,9526 ----
The \texttt{namespace} \textit{attribute information item} sets the namespace to be used with
+
all imported element definitions described in the DTD. It has the following
infoset properties:
***************
*** 9527,9531 ****
-
A RELAX NG schema may be used as the schema language for WSDL. It may be
embedded or imported; import is preferred. A namespace must be specified;
--- 9570,9573 ----
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.226
retrieving revision 1.227
diff -C2 -d -r1.226 -r1.227
*** wsdl20.xml 29 Apr 2005 22:55:27 -0000 1.226
--- wsdl20.xml 30 Apr 2005 13:35:20 -0000 1.227
***************
*** 1834,1837 ****
--- 1834,1868 ----
</z:notation>
+ <z:notation name="InterfaceParent">
+
+ <p>An Interface component contains nested Interface Operation, Interface Fault, Feature, and Property components.
+ These components MUST have the Interface component as their parent.</p>
+
+ <p>Let <z:i>InterfaceParent</z:i> express the constraints on the {parent} properties of the nested components of an Interface component:
+ </p>
+
+ <schema xmlns="http://www.w3.org/2004/zml" name="InterfaceParent">
+ ComponentModel2
+ <where/>
+ <forall/> c : interfaceComps; <nl/>
+ <t1/> if : interfaceFaultComps; io : interfaceOpComps; <nl/>
+ <t1/> f : featureComps; p : propertyComps @ <nl/>
+ <t1/> if.id <in/> c.interfaceFaults <implies/> if.parent = c.id <land/> <nl/>
+ <t1/> io.id <in/> c.interfaceOperations <implies/> io.parent = c.id <land/> <nl/>
+ <t1/> f.id <in/> c.features <implies/> f.parent = c.id <land/> <nl/>
+ <t1/> p.id <in/> c.properties <implies/> p.parent = c.id
+ </schema>
+
+ <z:see names="ComponentModel2"/>
+
+ <ulist>
+ <item><p>Each Interface component is the parent of any Interface Fault component it contains.</p></item>
+ <item><p>Each Interface component is the parent of any Interface Operation component it contains.</p></item>
+ <item><p>Each Interface component is the parent of any Feature component it contains.</p></item>
+ <item><p>Each Interface component is the parent of any Property component it contains.</p></item>
+ </ulist>
+
+ </z:notation>
+
<z:notation name="InterfaceClosure">
<p>
***************
*** 3843,3846 ****
--- 3874,3896 ----
</z:notation>
+ <z:notation name="FeatureRI">
+
+ <p>The parent of a Feature MUST be in the component model.</p>
+
+ <p>
+ Let <z:i>FeatureRI</z:i> express this referential integrity constraint on the Feature component:
+ </p>
+
+ <schema xmlns="http://www.w3.org/2004/zml" name="FeatureRI">
+ ComponentModel2
+ <where/>
+ <forall/> Feature | <theta/>Feature <in/> featureComps @ <nl/>
+ <t1/> ParentRI
+ </schema>
+
+ <z:see names="ComponentModel2 Feature ParentRI"/>
+
+ </z:notation>
+
<div4 id="Feature_composition_model">
<head>Feature Composition Model</head>
***************
*** 4304,4309 ****
ComponentModel2
<where/>
! <forall/> x : propertyComps; y : ID @ <nl/>
! <t1/> x.valueConstraint = {typeDefinitionId(y)} <implies/> y <in/> typeDefIds
</schema>
--- 4354,4360 ----
ComponentModel2
<where/>
! <forall/> Property; y : ID | <theta/>Property <in/> propertyComps @ <nl/>
! <t1/> valueConstraint = {typeDefinitionId(y)} <implies/> y <in/> typeDefIds <land/> <nl/>
! <t1/> ParentRI
</schema>
***************
*** 4311,4315 ****
<ulist>
! <item><p>The Type Definition component of each Property component is contained in the component model.</p></item>
</ulist>
--- 4362,4367 ----
<ulist>
! <item><p>If the value constraint of a Property component is a type definition, then the Type Definition component is contained in the component model.</p></item>
! <item><p>The parent of each Property component is contained in the component model.</p></item>
</ulist>
Received on Saturday, 30 April 2005 13:35:25 UTC