XML Name-Value pairs Result set encodings
9.4 Result set encodings
9.4.1 XML
The default encoding for returning results is XML. The General Model clause describes the common Summary set fields and XML syntax to be supported by all Protocol Bindings see Subclause 6.3.9.4.2 Name-Value pairs
Additional, the CORBA profile adds a Name-Value NV entry to the message format enumeration see Subclause 9.6. Specifying NV lets the server return results as name- value pairs. Name-value pairs are specified in the OMG CORBA 2.3 DynamicAny specification, but to be complete, the definition is repeated below and in the IDL. Usage of NameValuePair specification from OMG CORBA 2.3 DynamicAny aligns Catalogue Services CORBA Profile with revision 1.1 draft 3 of Simple Feature Access for CORBA. enum MessageFormat {XML, HTML, TXT, NV}; module DynamicAny { struct NameValuePair { string name; any value; }; typedef sequenceNameValuePair NameValuePairSeq; }; So if the server gives the results back as XML in the next example: ?xml version=1.0? DOCTYPE Metadata SYSTEM min.dtd Metadata TitleCountries of EuropeTitle AbstractThis dataset contains the countries of EuropeAbstract GeographicBoundingBox westBoundLongitude-24.17westBoundLongitude eastBoundLongitude40.71eastBoundLongitude northBoundLatitude71.26northBoundLatitude southBoundLatitude27.63southBoundLatitude GeographicBoundingBox Metadata Name-value pair results are as follows: 86 Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. id: Metadata value: NameValuePair Seq id: Title value: Countries of Europe id: Abstract value: This dataset ... id: Geographic BoundingBox value: NameValuePair Seq id: westBound Longitude value: -24.17 Figure 27 — Name-value pair results The advantage is that pure CORBA environments do not have to parse the XML to get the results. They receive them in a suitable general structure. If the CORBA server is combined with another type of client, e.g. a Web client, then probably XML the default will be preferred. The any value member can contain any type: standard types as long, double, string, types as NameValuePair or NameValuePairSeq this gives the possibility to create recursive structures or user-defined types.9.5 General model to CORBA protocol binding operations mapping
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