Author: lmandel
Date: Thu Nov 17 14:38:24 2005
New Revision: 345350
URL: http://svn.apache.org/viewcvs?rev=345350&view=rev
Log:
Added assertions for description, types, interface, proprety, and features.
Added suggested warning messages.
Modified:
incubator/woden/java/src/org/apache/woden/internal/Messages.properties
Modified: incubator/woden/java/src/org/apache/woden/internal/Messages.properties
URL:
http://svn.apache.org/viewcvs/incubator/woden/java/src/org/apache/woden/internal/Messages.properties?rev=345350&r1=345349&r2=345350&view=diff
==============================================================================
--- incubator/woden/java/src/org/apache/woden/internal/Messages.properties
(original)
+++ incubator/woden/java/src/org/apache/woden/internal/Messages.properties Thu
Nov 17 14:38:24 2005
@@ -115,6 +115,140 @@
types-0023.ref = 3.2
types-0023.assertion = A specification of extension syntax for an alternative
schema language MUST include the declaration of an element information item,
intended to appear as a child of the wsdl:types element information item, which
references, names, and locates the schema instance (an ?import? element
information item).
+description-0024 =
+description-0024.ref = 2.1.2
+description-0024.assertion = Each WSDL 2.0 or type system component MUST be
uniquely identified by its qualified name. That is, if two distinct components
of the same kind (Interface, Binding, etc.) are in the same target namespace,
then their QNames MUST be unique. However, different kinds of components (e.g.,
an Interface component and a Binding component) MAY have the same QName. Thus,
QNames of components must be unique within the space of those components in a
given target namespace.
+description-0025 =
+description-0025.ref = 2.1.2.1
+description-0025.assertion = The type of the targetNamespace attribute
information item is xs:anyURI. Its value MUST be an absolute IRI (see [IETF RFC
3987]).
+
+types-0026 =
+types-0026.ref = 2.1.2.1
+types-0026.assertion = It is an error if there are multiple type definitions
for each QName.
+
+interface-0027 =
+interface-0027.ref = 2.2.1
+interface-0027.assertion = To avoid circular definitions, an interface MUST
NOT appear as an element of the set of interfaces it extends, either directly
or indirectly.
+
+interface-fault-0028 =
+interface-fault-0028.ref = 2.2.1
+interface-fault-0028.assertion = The namespace name of the {name} property of
each Interface Fault in this set MUST be the same as the namespace name of the
{name} property of this Interface component.
+
+interface-operation-0029 =
+interface-operation-0029.ref = 2.2.1
+interface-operation-0029.assertion = The namespace name of the {name} property
of each Interface Operation in this set MUST be the same as the namespace name
of the {name} property of this Interface component.
+
+interface-0030 =
+interface-0030.ref = 2.2.1
+interface-0030.assertion = For each Interface component in the {interfaces}
property of a Description component, the {name} property MUST be unique.
+
+interface-0031 =
+interface-0031.ref = Section 2.2.2.3
+interface-0031.assertion = The type of the styleDefault attribute information
item is list of xs:anyURI. Its value, if present, MUST contain absolute IRIs
(see [IETF RFC 3987]).
+
+interface-fault-0032 =
+interface-fault-0032.ref = 2.3.1
+interface-fault-0032.assertion = For each Interface Fault component in the
{interface faults} property of an Interface component, the {name} property must
be unique. Interface Fault components are uniquely identified by the the QName
of the enclosing Interface component and QName of the Interface Fault component
itself.
+
+interface-fault-0033 =
+interface-fault-0033.ref = 2.3.1
+interface-fault-0033.assertion = In cases where, due to an interface extending
one or more other interfaces, two or more Interface Fault components have the
same value for their {name} property, then the component models of those
Interface Fault components MUST be equivalent (see 2.17 Equivalence of
Components).
+
+interface-fault-0034 =
+interface-fault-0034.ref = 2.3.1
+interface-fault-0034.assertion = Note that, due to the above rules, if two
interfaces that have the same value for the namespace name of their {name}
property also have one or more faults that have the same value for their {name}
property then those two interfaces cannot both form part of the derivation
chain of a derived interface unless those faults are the same fault.
+
+interface-operation-0035 =
+interface-operation-0035.ref = Section 2.4.1
+interface-operation-0035.assertion = For each Interface Operation component in
the {interface operations} property of an Interface component, the {name}
property MUST be unique. Interface Operation components are uniquely identified
by the the QName of the enclosing Interface component and QName of the
Interface Operation component itself.
+
+interface-operation-0036 =
+interface-operation-0036 = 2.4.1
+interface-operation-0036.assertion = In cases where, due to an interface
extending one or more other interfaces, two or more Interface Operation
components have the same value for their {name} property, then the component
models of those Interface Operation components MUST be equivalent (see 2.17
Equivalence of Components).
+
+mep-0037 =
+mep-0037.ref = 2.4.1.1
+mep-0037.assertion = A message exchange pattern is uniquely identified by an
absolute IRI which is used as the value of the {message exchange pattern}
property the Interface Operation component, and it specifies the fault
propagation ruleset that its faults obey.
+
+interface-operation-0038 =
+interface-operation-0038.ref = 2.4.1.2
+interface-operation-0038.assertion = An Interface Operation component MUST
satisfy the specification defined by each operation style identified by its
{style} property. If no Interface Operation component can simultaneously
satisfy all of the styles, the document is invalid.
+
+message-label-0039 =
+message-label-0039.ref = 2.5.1
+message-label-0039.assertion = The value of this property MUST match the name
of a placeholder message defined by the message exchange pattern.
+
+interface-message-ref-0040 =
+interface-message-ref-0040.ref = 2.5.1
+interface-message-ref-0040.assertion = The direction MUST be the same as the
direction of the message identified by the {message label} property in the
{message exchange pattern} of the Interface Operation component this is
contained within.
+
+interface-message-ref-0041 =
+interface-message-ref-0041.ref = 2.5.1
+interface-message-ref-0041.assertion = When the {message content model}
property has the value #any or #none the {element declaration} property MUST be
empty.
+
+interface-message-ref-0042 =
+interface-message-ref-0042.ref = 2.5.1
+interface-message-ref-0042.assertion = For each Interface Message Reference
component in the {interface message references} property of an Interface
Operation component, its {message label} property MUST be unique.
+
+interface-fault-ref-0043 =
+interface-fault-ref-0043.ref = 2.6.1
+interface-fault-ref-0043.assertion = The value of this property MUST match the
name of a placeholder message defined by the message exchange pattern.
+
+interface-fault-ref-0044 =
+interface-fault-ref-0044.ref = 2.6.1
+interface-fault-ref-0044.assertion = The direction MUST be consistent with the
direction implied by the fault propagation ruleset used in the message exchange
pattern of the operation.
+
+interface-fault-ref-0045 =
+interface-fault-ref-0045.ref = 2.6.1
+interface-fault-ref-0045.assertion = For each Interface Fault Reference
component in the {interface fault references} property of an Interface
Operation component, the combination of its {interface fault} and {message
label} properties MUST be unique.
+
+feature-ref-0046 =
+feature-ref-0046.ref = 2.7.1
+feature-ref-0046.assertion = This xs:anyURI MUST be an absolute IRI as defined
by [IETF RFC 3987].
+
+feature-ref-0047 =
+feature-ref-0047.ref = 2.7.1
+feature-ref-0047.assertion = The {ref} property of a Feature component MUST be
unique within the {features} property of an Interface, Interface Fault,
Interface Operation, Interface Message Reference, Interface Fault Reference,
Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding
Fault Reference, Service, or Endpoint component.
+
+property-ref-0048 =
+property-ref-0048.ref = 2.8.1
+property-ref-0048.assertion = This xs:anyURI MUST an absolute IRI as defined
by [IETF RFC 3987].
+
+property-0049 =
+property-0049.ref = 2.8.1
+property-0049.assertion = A reference to a Type Definition component in the
{type definitions} property of the Description component constraining the value
of the Property, or the token #value if the {value} property is not empty.
+
+property-0050 =
+property-0050.ref = 2.8.1
+property-0050.assertion = The {ref} property of a Property component MUST be
unique within the {properties} property of an Interface, Interface Fault,
Interface Operation, Interface Message Reference, Interface Fault Reference,
Binding, Binding Fault, Binding Operation, Binding Message Reference, Binding
Fault Reference, Service, or Endpoint component.
+
+property-0051 =
+property-0051.ref = 2.8.1.1
+property-0051.assertion = However, it is in general feasible to test specified
values for either equality or membership in value sets. All specified values
MUST be equal and belong to each specified value set.
+
+# ------------SECTION 3: WSDL-related warnings -------------------
+# These warnings were pulled from the WSDL 2.0 spec and are possible warnings
+# for the validator to report.
+
+description-S0001 =
+description-S0001.ref = 2.1.2
+description-S0001.assertion = The value of the targetNamespace attribute
information item SHOULD be a dereferenceable IRI (see [IETF RFC 3987])
+
+interface-fault-S0002 =
+interface-fault-S0002.ref = 2.3.1
+interface-fault-S0002.assertion = For the above reason, it is considered good
practice to ensure, where necessary, that the local name of the {name} property
of Interface Fault components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
+
+interface-operation-S0003 =
+interface-operation-S0003.ref = 2.4.1
+interface-operation-S0003.assertion = For the above reason, it is considered
good practice to ensure, where necessary, that the {name} property of Interface
Operation components within a namespace are unique, thus allowing such
derivation to occur without inadvertent error.
+
+feature-ref-S0004 =
+feature-S0004.ref = 2.7.1
+feature-S0004.assertion = This IRI SHOULD be dereferenceable to a document
that directly or indirectly defines the meaning and use of the Feature that it
identifies.
+
+property-ref-S0005 =
+property-ref-S0005.ref = 2.8.1
+property-ref-S0005.assertion = This IRI SHOULD be dereferenceable to a
document that directly or indirectly defines the meaning and use of the
Property that it identifies.
------------------- End of Messages ----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
