OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-query message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Prelim. WSDL for Pluggable Content Indexing Service


Team,

Attached is some WSDL I cooked up based on Farrukh's description of 
PCIS.  Your comments would be appreciated, but certainly not necessary 
at this point seeing as this is really a v3 task.

Regards,

Matthew MacKenzie
Xml Global
http://www.xmlglobal.com
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="IndexContent" targetNamespace="http://ebxml.org/ns/rr/content-index/1.0" xmlns:this="http://ebxml.org/ns/rr/content-index" xmlns:schema="http://ebxml.org/schema/content-index-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<types>
		<xs:schema elementFormDefault="qualified" attributeFormDefault="unqualified">
			<xs:element name="IndexContentOutput">
				<xs:annotation>
					<xs:documentation>Outermost structure of index output</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:all>
						<xs:element name="ClassificationIndexes">
							<xs:complexType>
								<xs:all>
									<xs:element name="ClassificationIndex" minOccurs="0" maxOccurs="100"/>
								</xs:all>
							</xs:complexType>
						</xs:element>
					</xs:all>
				</xs:complexType>
			</xs:element>
			<xs:element name="IndexContentInput">
				<xs:complexType>
					<xs:all>
						<xs:element name="content" type="string">
							<xs:attribute name="mimeType" type="string" />
							<xs:annotation>
								<xs:documentation>Content should be Base64 encoded, or in the case of content such as XML or HTML, wrapped in a CDATA.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:all>
				</xs:complexType>
			</xs:element>
		</xs:schema>
	</types>
	
	<message name="IndexContentRequest">
		<part name="body" element="schema:IndexContentInput" />
	</message>
	
	<message name="IndexContentResponse">
		<part name="body" element="schema:IndexContentOutput" />
	</message>
	
	<portType name="IndexContentPortType">
		<operation name="IndexContent">
			<input message="this:IndexContentRequest" />
			<output message="this:IndexContentResponse" />
		</operation>
	</portType>
	
	<!--
	     *
	     *  To define binding and services, use WSDL's import mechanism to "extend" this, and add on any bindings & services.
	     *
	 -->
	
</definitions>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC