[Requests] Comments on OGC 10-034r3 Rev: 0.6

Kavuri, Chandra Sekhara Murthy Chandra.Kavuri at intergraph.com
Tue Jul 27 00:33:27 EDT 2010


Hello,

Here are four comments on the document mentioned below.

Thanks

Kcs

 

 

PART A

 

 

1. Evaluator:

       Murti KCS, Intergraph Consulting pvt ltd, Hyderabad , India,
Chandra.kavuri at intergraph.com

 

 

2. Submission: 

OGC 10-034r3; Rev 0.6, OGC MovingObjectSnapshot:  An application schema
of the OGC Geography Markup Language

 

 

PART B.1

 

 

1. Requirement: 

Scope of moving object definition has to be extended to represent real
world scenarios.

 

2. Implementation Specification Section number: 

Section-1

 

3. Criticality: [Major, Minor, Editorial, etc.]

Major

 

4. Comments/justifications for changes: 

Fundamental abstractions for moving objects  are : moving point, point
sets, lines and  moving regions. All the above abstractions are
necessary to  model  real world problems.  The proposed schema should be
extended to support all above. As an example: forest, forest  fire and
fire _ fighter are  moving objects where forest, forest fire are moving
regions and fire fighter is moving point.

 

PART B.2

 

1. Requirement: 

The proposed schema should support  continuity and discontinuity of
motion

2. Implementation Specification Section number: 

Section-5.1

 

3. Criticality: [Major, Minor, Editorial, etc.]

Major

4. Comments/justifications for changes: 

The proposed schema should support  continuity and discontinuity of
motion . (ex) A moving point ceases motion for some time. The motion is
undefined in certain time period. (GPS fails)  The start and end
instances of the moving object etc.

 

PART B.3

 

1. Requirement: 

Splitting and merging of a moving objects need to be within the scope of
definition and schema should support this.

2. Implementation Specification Section number: 

Section-5

3. Criticality: [Major, Minor, Editorial, etc.]

Major

4. Comments/justifications for changes: 

Though the abstraction of splitting and merging of a moving object is
not very common, this support  in the schema helps  certain scenarios.
(ex: Certain carriers are coupled at an instance and de-coupled after
reaching some distance)

 

PART B.4

 

1. Requirement: 

Should support motion at periodic intervals.

2. Implementation Specification Section number: 

Section-5

3. Criticality: [Major, Minor, Editorial, etc.]

Major

4. Comments/justifications for changes: 

The  schema  has to be  extended  to   support  sliced representation of
the moving objects? (i.e) location at defined periodic intervals.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opengeospatial.org/pipermail/requests/attachments/20100727/71003b02/attachment.htm 


More information about the Requests mailing list