| Re: [higgins-dev] IContextFactory policy |
I think that we still need them, as we will need java bindings and other bindings like web services
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Jim Sermersheim" <jimse@xxxxxxxxxx>
Sent by: higgins-dev-bounces@xxxxxxxxxxx 08/02/2006 06:48 PM
|
|
I believe that its all metadata and what we have to declare is the schema for the metadata, there will be different dialects (which are URIs) for different metadata.
The Web service Metadata element is a collection of metadata units such as [WSDL] definitions, XML Schema [XML Schema Part 1, Part 2] documents, [WS-Policy] expressions, etc. Each unit corresponds to metadata for a given scope, domain, or namespace. The collection of units is represented by a Metadata element, and units within the collection are represented by Metadata Section elements.
To facilitate processing, Metadata Sections are tagged with a @Dialect and (optionally) @Identifier of the metadata unit. To ensure scalability, a unit of metadata may be included in-line within its Metadata Section or may be included by reference, either an endpoint reference [WS-Addressing] (Metadata Reference) or a URL (Location).
An outline for the Metadata element would be (as described in WS-MetaDataExchange):
<mex:Metadata ...>
<mex:MetadataSection Dialect="xs:anyURI"
(Identifier="xs:anyURI")? ...>
(
<DialectSpecificElement>...</DialectSpecificElement>
|
<mex:MetadataReference ...>
endpoint-reference
</mex:MetadataReference>
|
<mex:Location>xs:anyURI</mex:Location>
)
</mex:MetadataSection>*
</mex:Metadata>
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Jim Sermersheim" <jimse@xxxxxxxxxx>
Sent by: higgins-dev-bounces@xxxxxxxxxxx 08/01/2006 11:57 PM
|
|
