• Tidak ada hasil yang ditemukan

Change Requests | OGC

N/A
N/A
Protected

Academic year: 2017

Membagikan "Change Requests | OGC"

Copied!
2
0
0

Teks penuh

(1)

Open Geospatial Consortium

OGC Doc 06-112

CR-Form-v3

CHANGE REQUEST

SOS 1.0 CR ?

 rev

-

 Current version: 1.0 

For

HELP

 

on using this form, see bottom of this page or look at the pop-up text over the  symbols.

Proposed change affects:  AS Imp Spec X Best Practices Paper Other

Title:  Addition of the InsertResult Operation

Source:  Kuo-Yu slayer Chuang, Hsu-Chun Yu

Work item code:Date:  2008-09-30

Category:B

Use one of the following categories:

F (Critical correction)

A (corresponds to a correction in an earlier release)

B (Addition of feature),

C (Functional modification of feature)

D (Editorial modification)

Detailed explanations of the above categories can be found in the TC Policies and Procedures.

Reason for change:  The GetResult operation allows a client to repeatedly obtain sensor data from the same set of sensors. But there is no corresponding InsertResult operation that allows a client to repeatedly upload sensor data.

Summary of change:  Add the InsertResult operation to the transaction operations profile or the enhanced operations profile. A client has to upload the observation template only in the first time, and then it can upload sensor data without format description, so as to reduce network bandwidth usage and increase uploading efficiency.

Consequences if

not approved: A client has to encapsulate format description in sensor data each time while uploading.

Clauses affected:  Clause 9 or Clause 10

Other specs  Other core specifications 

Affected: Abstract specifications

(2)

The OGC Technical Committee Policies & Procedures 05-020r3

1.

Client sends a RegisterSensor request which includes an O&M Observation instance

that is an observation template.

2.

SOS-T responds with an AssignedSensorId which designates the new sensor.

3.

Client sends an InsertResult request which includes the AssignedSensorId and the

result element of an O&M Observation. SOS-T uses the O&M template in Step 1 to

parse this result element.

4.

SOS-T responds with an assigned Observation identifier. (This response is the same

as that of the InsertObservation operation.)

Referensi

Dokumen terkait

Reason for change:  A number of elements and types representing temporal aggregates are specified in SWE Common (within SensorML, OGC 07-000). These

Reason for change:  Three standard elements or attributes are available to hold object identifiers in GML applications: @gml:id, gml:name and gml:identifier.. There is need for

Reason for change:  A significant number of components in GML were included after insufficient implementation testing, or in retrospect were inappropriate in the core GML schema

Reason for change:  ISO 19111-2 has extended the scope of ISO 19111 coordinate reference systems to include ‘parametric coordinate reference systems’ often used in

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

Reason for change:  To enable remote referencing and the possibility of avoiding inline metadata bloat in AIXM instances. Summary of change:  Enable remote referencing on 3

Summary of change:  Remove the SWE Common data model specification description from the SensorML specification, and reference the corresponding SWE Common specification

Reason for change:  The WPS 1.0.0 specification does not provide any mechanism for querying the status of an asynchronous process, though the specification does require an