[tdwg-tapir] Schema modification: r584 - trunk/protocol

[tdwg-tapir at lists.tdwg.org]

Author: renato
Date: 2006-10-10 14:28:12 +0200 (Tue, 10 Oct 2006)
New Revision: 584

Modified:
   trunk/protocol/tapir.xsd
Log:
* Removed <diagnostics> element from requestType.
* Updated TAPIR web address.
* Removed authors from appinfo (complete list will appear in the specs).
* Updated some of the annotations.



Modified: trunk/protocol/tapir.xsd
===================================================================
--- trunk/protocol/tapir.xsd	2006-10-10 12:15:40 UTC (rev 583)
+++ trunk/protocol/tapir.xsd	2006-10-10 12:28:12 UTC (rev 584)
@@ -12,17 +12,14 @@
 	<xsd:annotation>
 		<xsd:documentation xml:lang="en">
 			TAPIR XML Schema.  TAPIR is an acronym for TDWG Access Protocol for Information Retrieval.
-			A unified and extended protocol based on DiGIR and BioCASE. TAPIR specifies a standardised, 
-			stateless, HTTP transmittable, XML-based request and response protocol for accessing, structured 
+			It is a unified and extended protocol based on DiGIR and BioCASE. TAPIR specifies a standardised, 
+			stateless, HTTP transmittable, XML-based request and response protocol for accessing structured 
 			data that may be stored on any number of distributed databases of varied physical and logical 
-			structure. TAPIR documents are either request or response types, as defined by their root element.	
+			structure.	
 		</xsd:documentation>		
 		<xsd:appinfo>
 			<dc:title>TAPIR XML Schema</dc:title>
-			<dc:creator>Markus Döring [m.doering at bgbm.org]</dc:creator>
-			<dc:creator>Renato De Giovanni [renato at cria.org.br]</dc:creator>
-			<dc:relation>http://ww3.bgbm.org/protocolwiki</dc:relation>
-			<dc:contributor>Charles Copp [eim at globalnet.co.uk]</dc:contributor>
+			<dc:relation>http://www.tdwg.gbif.org/subgroups/tapir/</dc:relation>
 		</xsd:appinfo>
 	</xsd:annotation>
 	<!-- ============================================= -->
@@ -111,8 +108,7 @@
 			<xsd:documentation>A Header is part of request and response messages. The Header describes the source of the request or response 
 				and optionally its destination. It may also describe the software that sent the request or response 
 				and there is a custom section for extending the information e.g. with information related to security or access.
-				If the noresponse attribute is set to true the request is meant for logging only and no response should be generated.
-			               The header can list several sources, where for instance, a request is cascaded through one or more portals. </xsd:documentation>
+			        The header can list several sources, where for instance, a request is cascaded through one or more portals. </xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence>
 			<xsd:element name="source" maxOccurs="unbounded">
@@ -143,7 +139,7 @@
 													<xsd:sequence minOccurs="0">
 														<xsd:element name="dependency" type="softwareInformationType" minOccurs="0" maxOccurs="unbounded">
 															<xsd:annotation>
-																<xsd:documentation>A singledependency for the software,e.g. a library, framework, component, OS,...</xsd:documentation>
+																<xsd:documentation>A single dependency for the software, e.g. a library, framework, component, OS, etc.</xsd:documentation>
 															</xsd:annotation>
 														</xsd:element>
 													</xsd:sequence>
@@ -195,7 +191,7 @@
 	</xsd:complexType>
 	<xsd:complexType name="diagnosticsListType">
 		<xsd:annotation>
-			<xsd:documentation>Provides the means to present  a list of diagnostic messages from the service.</xsd:documentation>
+			<xsd:documentation>Provides the means to present a list of diagnostic messages from the service.</xsd:documentation>
 		</xsd:annotation>
 		<xsd:sequence minOccurs="0">
 			<xsd:element name="diagnostic" type="diagnosticMessageType" minOccurs="0" maxOccurs="unbounded"/>
@@ -740,9 +736,6 @@
 					</xsd:complexType>
 				</xsd:element>
 				<xsd:element name="search">
-					<xsd:annotation>
-						<xsd:documentation>A search with TBD... </xsd:documentation>
-					</xsd:annotation>
 					<xsd:complexType>
 						<xsd:choice>
 							<xsd:element name="template" type="externalResourceType"/>
@@ -754,7 +747,6 @@
 					</xsd:complexType>
 				</xsd:element>
 			</xsd:choice>
-			<xsd:element name="diagnostics" type="diagnosticsListType" minOccurs="0"/>
 		</xsd:sequence>
 	</xsd:complexType>
 	<xsd:attributeGroup name="globalParametersGroup">
@@ -772,7 +764,7 @@
 	<!-- ============================================= -->
 	<xsd:element name="response" type="responseType">
 		<xsd:annotation>
-			<xsd:documentation>Global element representing a response.This is a root element
+			<xsd:documentation>Global element representing a response. This is a root element
 				and must contain reference to the schema and namespaces used</xsd:documentation>
 		</xsd:annotation>
 	</xsd:element>
@@ -795,8 +787,8 @@
 			<xsd:element name="diagnostics" type="diagnosticsListType" minOccurs="0">
 				<xsd:annotation>
 					<xsd:documentation>The diagnostics element is an optional part of TAPIR requests and response messages.
-						Diagnostics may contain many  pieces of information used for debugging and providing warnings or error messages.
-						Individual diagnostics are held in a diagnosticList  with an enumerated attribute for level and attributes for code and time.
+						Diagnostics may contain many pieces of information used for debugging and providing warnings or error messages.
+						Individual diagnostics are held in a diagnosticList with an enumerated attribute for level and attributes for code and time.
 						</xsd:documentation>
 				</xsd:annotation>
 			</xsd:element>