Re: [Geopriv] building GML in PIDF

["Winterbottom, James" <[e-mail]>]

Hannes,

There is an option d), which is redefine the meaning of the resolution bits so that they are useful for conveying uncertainty.
See http://tools.ietf.org/html/draft-thomson-geopriv-3825bis-01


Cheers
James
 

-----Original Message-----
From: [e-mail] on behalf of Hannes Tschofenig
Sent: Sat 3/1/2008 1:09 AM
To: Robert Sparks
Cc: GEOPRIV
Subject: Re: [Geopriv] building GML in PIDF
 
Thanks for the nice summary.

There are essentially three ways to solve this issue (based on my 
understanding):

(a) Express RFC 3825 information in GML
(b) Provide rules on how to transform RFC 3825 parameters into GML
Example can be found in 
http://tools.ietf.org/html/draft-ietf-geopriv-pdif-lo-profile-05#appendix-B
(c) Provide a way to make the translation simple
Example can be found at 
http://tools.ietf.org/wg/geopriv/draft-tschofenig-geopriv-dhcp-circle-00.txt

Case (a) is essentially telling the GML folks that they were wrong with 
what they did in the past. I would be interested to see how they react.

Case (b) leaves us with a fairly simple description but with some errors 
as that version of the PIDF-LO document explained.

Case (c) requires more work.

None of the approaches sound particularly great to me.

Ciao
Hannes

Robert Sparks wrote:
> I've spent the last couple of days reading and re-reading the binary- 
> lci related threads.
>
> I'm thinking hard about how the group can make progress, and what the  
> truly important things to make progress are on here.
> Feel free to help me figure that out (change the subject line if  
> that's what you are responding to - this subject is for the rest of  
> the message).
>
> Agreement about one thing in this thread is clear: GEOPRIV needs to  
> clearly state how to build a PIDF document when handed a bare pair of  
> lat/long coordinates.
>
> There are a bunch of other things in those threads, but lets focus on  
> that one thing for a moment.
>
> To help separate this from DHCP and the discussions around the  
> clarifications in the binary-lci document, let me put forth this use  
> case.
> It's a little (but only a little) contrived, but I hope it teases out  
> one of the things we need to get clarity on.
>
> Imagine an operator getting a call from someone where the transport  
> or source of the call gave them no help on identifying where the  
> problem spot was.
> The only way that information is conveyed is verbal.
> This could be someone radioing in from a boat, or someone with an old  
> CB radio talking to a family member with a land line - whatever.
> The person with the problem has some way to know their lat/long  
> (lunars and declinations, an old GPS, something scribbled on the  
> brass in the rock, again, whatever).
>
> The operator gets, verbally, that the problem is at 49.0N, 114.0W.
>
> What should the system the operator feeds that into emit (as a PIDF- 
> LO in, for example, a LOST query)?
>
> How is the answer different if operator gets 49.03N, 114.00W?
>
> (For those who haven't followed the threads, there's growing  
> understanding that simply putting those values in as
> GML 3.0 points isn't the right thing to do, and we're trying to  
> figure out what the right thing is).
>
> Thanks,
>
> RjS
> _______________________________________________
> Geopriv mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/geopriv
>   

_______________________________________________
Geopriv mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/geopriv


------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/geopriv