• Tidak ada hasil yang ditemukan

Correction of XML Schema GetCapabilitiesResponse.xsd

N/A
N/A
Protected

Academic year: 2017

Membagikan "Correction of XML Schema GetCapabilitiesResponse.xsd"

Copied!
2
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Name:

*

Herve Caumont

Organization:

*

ERDAS

Email:

*

[email protected]

Document

Name/Version:

*

Web Map Tile Service Implementation Standard / 1.0.0

OGC Project

Document:

*

07-057r7

If this is a revision of a previous submission and you have a Change Request Number, then check here:

Enter the CR number here:

Enter the Revsion Number that you are revising here:

Title:

*

Correction of XML Schema GetCapabilitiesResponse.xsd

Source:

*

ERDAS, CREAF

Work item

code:

Category:

*

F (Critical correction)

Reason for

change:

*

Considering both « OGC 07-057r7 » and «

wmtsGetCapabilities_response.xsd » we have discrepancies in the types (integer/positiveInteger) for the following elements of TileMatrixLimits :

There is a need for alignment and text clarification for data types related to "TileMatrixLimits" in OGC 07-057r7 and the ones

in the « wmtsGetCapabilities_response.xsd » XML Schema.

For TileMatrixLimits elements, the spec confirms « 0 values are allowed » when at the same time they refer to «

xs:positiveInteger » Type (in document table 12 or in XML schema file).

MinTileRow, MaxTileRow, MinTileCol, MaxTileCol elements shall shall be casted « integers » (and not PositiveIntegers)

(2)

not approved:

Clauses

affected:

*

Table 12 - "Parts of TileMatrixLimits data structure"

Additional

Documents

affected:

wmtsGetCapabilities_response.xsd

Supporting

Documentation:

Comments:

Table 12 comment (e) shall be corrected as well:

(e) From minTileCol to tileHeight-1 of the tileMatrix section of this tileMatrixSet

tileHeight is defined in Pixels. Should be matrixHeight

Status:

Assigned

Assigned To:

WMS 1.4 SWG

Gambar

Table 12 - "Parts of TileMatrixLimits data structure"

Referensi

Dokumen terkait

Change "description TEXT NOT NULL DEFAULT 'none'," in Table 2 to "description TEXT NOT NULL DEFAULT ''," to match default shown in Table 1. Consequences if

Harmonize with SQL/MM by adding all types currently in SQL/MM and specification of a set of conformance classes corresponding to the SQL/MM standards. Consequences if

One topic was to use KML to portray command and control data according to the MIL-STD-2525B common warfighting symbology.. Consequences if

Update the standard and the schemas to make sure that the default value for the startIndex parameter is 1 everywhere. Consequences if

either define a zipped-x mime type or change the complexinput/output description to allow mutiplie hrefs. Consequences if

Add a StoredQuery into a 'Simple WFS' for receiving a Filter 1.1 Query and processing it as a WFS 1.1 would.. Consequences if

I am aware that if any stage, it is found that any statement made is not true or incomplete or is misleading, the admission, if made will be automatically cancelled and that I shall not

Guarantor shall have approved in writing all key personnel and other elements of the film, received, reviewed, and approved in writing the Approved Budget, Approved Screenplay,