Overview Insert action XML encoding
10.11.3 XML encoding
10.11.3.1 Overview
The following XML schema fragment defines the XML encoding of the Transaction operation request: xsd:element name=Transaction type=csw:TransactionType xsd:complexType name=TransactionType xsd:complexContent xsd:extension base=csw:RequestBaseType xsd:sequence xsd:choice minOccurs=1 maxOccurs=unbounded xsd:element name=Insert type=csw:InsertType xsd:element name=Update type=csw:UpdateType xsd:element name=Delete type=csw:DeleteType xsd:choice xsd:sequence xsd:attribute name=requestId type=xsd:anyURI use=optional xsd:attribute name=verboseResponse type=xsd:boolean use=optional default=false xsd:extension xsd:complexContent xsd:complexType The Transaction element defines an atomic unit of work and is a container for one or more insert, update andor delete actions. The requestId attribute may be used by a client application to associate a user-defined identifier with the operation. The verboseResponse attribute is a boolean that may be used by a client to indicate to a server the amount of detail to generate in the response. A value of FALSE means that a CSW should generate a terse or brief transaction response. A value of TRUE, or the absence of the attribute, means that the normal detailed transaction response should be generated. The schema of transaction response is defined in Subclause 10.11.4.10.11.3.2 Insert action
The following XML-Schema fragment defines an insert action: xsd:complexType name=InsertType id=InsertType xsd:sequence xsd:any processContents=strict namespace=other maxOccurs=unbounded xsd:sequence xsd:attribute name=handle type=xsd:ID use=optional xsd:complexType The Insert element is a container for one or more records that are to be inserted into the catalogue. The schema of the records shall conform to the schema of the 166 Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. information model that the catalogue supports as described using the DescribeRecord operation. The handle attribute is an additional parameter not defined in the general model. It is used in the XML encoding to associate a mnemonic name with each action contained in a Transaction element for the purpose of error handling. If a CSW encounters an error processing a transaction request and the handle attribute is defined, the CSW can localize the source of the problem for the client by specifying the handle in the exception response as described in Subclause 10.3.7.10.11.3.3 Update action
Parts
» UML notation Change Requests | OGC
» Introduction OGC_Common catalogue query language
» Extending the Common Catalogue Query Language
» Introduction Core queryable properties
» Core returnable properties Core catalogue schema
» Document terms and definitions Introduction Introduction
» Introduction getCapabilities operation OGC_Service class
» Introduction “query” operation Discovery class
» “present” operation Discovery class
» describeRecordType operation Discovery class
» getDomain operation Discovery class
» Introduction “initialize” operation Session class
» “close” operation Session class
» “status” operation Session class
» “cancel” operation Session class
» Introduction ”transaction” operation Manager class
» harvestResource operation Manager class
» Introduction “order” operation Brokered Access class
» Introduction UML state diagram notation
» Catalogue server state machine Discovery state
» Access state diagram Dynamic model
» Management state Explain state diagram
» Introduction Z39.50 BER implementation notes
» Message encoding Additional search info Order extended service
» SearchRetrieve Web Service SRWSRU implementation notes
» XML Name-Value pairs Result set encodings
» Introduction Enumerations Structures and unions
» Definitions for brokered access Capabilities
» General messages Interface definition - IDL
» Discovery messages Interface definition - IDL
» Management messages Interface definition - IDL
» Access messages Exceptions Interface definition - IDL
» Catalogue Service interfaces Interface definition - IDL
» Overview Message headers The HTTP protocol
» Introduction Core queryable and returnable realization
» Full record Core queryable and returnable realization
» Summary record Core queryable and returnable realization
» Namespaces Predicate languages b
» General model message mapping Common request parameters
» Introduction Operation request GetCapabilities operation
» Operation response OperationsMetadata section standard contents
» Introduction KVP encoding DescribeRecord operation
» NAMESPACE parameter TypeName parameter outputFormat parameter
» XML encoding Response DescribeRecord operation
» Introduction KVP encoding GetDomain operation
» XML encoding Response GetDomain operation
» Introduction KVP encoding GetRecords operation
» XML encoding GetRecords operation
» NAMESPACE parameter requestId parameter resultType parameter
» outputFormat parameter outputSchema parameter
» Provide functional extensibility Precedence
» Tight and loose queries Property references
» Predicate languages DistributedSearch parameter
» ResponseHandler parameter Parameter descriptions
» Introduction KVP encoding GetRecordById operation
» ElementSetName parameter Id parameter outputFormat parameter outputSchema parameter
» XML encoding Examples GetRecordById operation
» Overview Insert action XML encoding
» Introduction KVP encoding Response
» Introduction KVP encoding Harvest operation
» Source parameter ResourceType parameter
» ResourceFormat parameter ResponseHandler parameter
» XML encoding Response Harvest operation
» Introduction Change Requests | OGC
» Interface definitions Change Requests | OGC
» Query languagemodel Query model components
» Catalogue Application Profiles Change Requests | OGC
» Introduction System context Structure and format
Show more