wiki:ru/WSDL

Version 8 (modified by vadim.godunko, 8 years ago) ( diff )

--

Support status of WSDL Assestions

AssertionDescriptionStatusComment
Description-1001 The value of the targetNamespace attribute information item SHOULD be dereferencable. - Нет возвожности выполнять запрос удалённых документов
Description-1002 It SHOULD resolve to a human or machine processable document that directly or indirectly defines the intended semantics of those components. - Нет возвожности выполнять запрос удалённых документов
Description-1003 It MAY resolve to a WSDL 2.0 document that provides service description information for that namespace. - Нет возвожности выполнять запрос удалённых документов
Description-1004 If a WSDL 2.0 document is split into multiple WSDL 2.0 documents (which may be combined as needed via 4.1 Including Descriptions), then the targetNamespace attribute information item SHOULD resolve to a master WSDL 2.0 document that includes all the WSDL 2.0 documents needed for that service description. - Не поддерживается импорт компонентов из других файлов
Description-1005 Zero or more element information items amongst its [children], in order as follows +
Description-1006 Its value MUST be an absolute IRI (see [IETF RFC 3987]) and should be dereferencable. - Нет возможности проверить является ли IRI абсолютным. Можно добавить необходимую функцию в League.IRIs
Types-1007 Each XML Schema element declaration MUST have a unique QName. - XML Schema не поддерживается
Types-1008 Each XML Schema type definition MUST have a unique QName. - XML Schema не поддерживается
Interface-1009 To avoid circular definitions, an interface MUST NOT appear in the set of interfaces it extends, either directly or indirectly. -
Interface-1010 For each Interface component in the {interfaces} property of a Description component, the {name} property MUST be unique. +
Interface-1011 The list of xs:QName in an extends attribute information item MUST NOT contain duplicates. +
Interface-1012 Its value, if present, MUST contain absolute IRIs (see [IETF RFC 3987]). - Нет возможности проверить является ли IRI абсолютным.
InterfaceFault-1013 An xs:token with one of the values #any, #none, #other, or #element. +
InterfaceFault-1014 When the {message content model} property has the value #any or #none the {element declaration} property MUST be empty. +
InterfaceFault-1015 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.15 Equivalence of Components). -
InterfaceFault-1016 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 SHOULD be unique, thus allowing such derivation to occur without inadvertent error. -
InterfaceFault-1017 If the element attribute information item has a value, then it MUST resolve to an Element Declaration component from the {element declarations} property of the Description component. - XML Schema не поддерживается
InterfaceOperation-1018 This xs:anyURI MUST be an absolute IRI (see [IETF RFC 3987]). - Нет возможности проверить является ли IRI абсолютным.
InterfaceOperation-1019 These xs:anyURIs MUST be absolute IRIs (see [IETF RFC 3986]). - Нет возможности проверить является ли IRI абсолютным.
InterfaceOperation-1020 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.15 Equivalence of Components). -
InterfaceOperation-1021 For the above reason, it is considered good practice to ensure, where necessary, that the {name} property of Interface Operation components within a namespace SHOULD be unique, thus allowing such derivation to occur without inadvertent error. -
MEP-1022 A message exchange pattern is itself uniquely identified by an absolute IRI, which is used as the value of the {message exchange pattern} property of the Interface Operation component, and which specifies the fault propagation ruleset that its faults obey. +
InterfaceOperation-1023 An Interface Operation component MUST satisfy the specification defined by each operation style identified by its {style} property. -
MessageLabel-1024 The value of this property MUST match the name of a placeholder message defined by the message exchange pattern. +
InterfaceMessageReference-1025 An xs:token with one of the values in or out, indicating whether the message is coming to the service or going from the service, respectively. +
InterfaceMessageReference-1026 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. +
InterfaceMessageReference-1027 An xs:token with one of the values #any, #none, #other, or #element. +
InterfaceMessageReference-1028 When the {message content model} property has the value #any or #none, the {element declaration} property MUST be empty. +
InterfaceMessageReference-1029 For each Interface Message Reference component in the {interface message references} property of an Interface Operation component, its {message label} property MUST be unique. +
MessageLabel-1030 If the messageLabel attribute information item of an interface message reference element information item is present, then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction. +
MessageLabel-1031 If the messageLabel attribute information item of an interface message reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction. +
MessageLabel-1032 If the local name is input then the message exchange pattern MUST have at least one placeholder message with direction "In". +
MessageLabel-1033 If the local name is output then the message exchange pattern MUST have at least one placeholder message with direction "Out". +
MessageLabel-1034 If the local name is infault then the message exchange pattern MUST support at least one fault in the "In" direction. +
MessageLabel-1035 If the local name is outfault then the message exchange pattern MUST support at least one fault in the "Out" direction. +
InterfaceMessageReference-1036 If the element attribute information item has a value, then it MUST resolve to an Element Declaration component from the {element declarations} property of the Description component. - XML Schema не поддерживается
InterfaceFaultReference-1037 The value of this property MUST match the name of a placeholder message defined by the message exchange pattern. +
InterfaceFaultReference-1038 The direction MUST be consistent with the direction implied by the fault propagation ruleset used in the message exchange pattern of the operation. +
InterfaceFaultReference-1039 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. +
InterfaceFaultReference-1040 The messageLabel attribute information item MUST be present in the XML representation of an Interface Fault Reference component with a given {direction}, if the {message exchange pattern} of the parent Interface Operation component has more than one fault with that direction. +
MessageLabel-1041 The messageLabel attribute information item of an interface fault reference element information item MUST be present if the message exchange pattern has more than one placeholder message with {direction} equal to the message direction. +
MessageLabel-1042 If the messageLabel attribute information item of an interface fault reference element information item is present then its actual value MUST match the {message label} of some placeholder message with {direction} equal to the message direction. +
MessageLabel-1043 If the messageLabel attribute information item of an interface fault reference element information item is absent then there MUST be a unique placeholder message with {direction} equal to the message direction. +
Note: See TracWiki for help on using the wiki.