Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-geojson-03

[Tim Schaub <[e-mail]>]

Bad response on my part about the OGC URN.

Does anyone know if http://www.opengis.net/def/crs/OGC/1.3/CRS84 is
supposed to resolve to something other than an ogc:ExceptionReport
(I'm seeing Failed resolving http://www.opengis.netcrs/OGC/1.3/CRS84)?

Should we go back to the urn:ogc:def:crs:OGC::CRS84 URN?  Or maybe
remove this sentence altogether?

Tim


On Thu, Jun 2, 2016 at 12:07 AM, Tim Schaub <[e-mail]> wrote:
> Thanks for the comments Meral.  I've proposed
> https://github.com/geojson/draft-geojson/pull/208 to incorporate them.
> Responses below ...
>
> On Wed, Jun 1, 2016 at 3:51 PM, Meral Shirazipour
> <[e-mail]> wrote:
>
> ...
>
>> -[Page 3], "any thing"--typo-->"anything"
>
> I *think* the original text was meant to emphasize "thing", but it
> ends up sounding awkward to me.  I think we should go with "anything"
> if others agree.
>
>> -[Page 4], KML not spelled out at first use (Keyhole Markup Language?)
>
> Done.
>
>> -[Page 11],PIDF-LO, please spell out at first use and maybe reference
>> RFC5139.
>
> Done.  But see below ...
>
>> -[Page 11], it says
>>
>> "Applications such as PIDF-LO that are sensitive to location
>>
>>    uncertainty and confidence might treat ...
>>
>> "
>>
>> Not clear: if this is not an OK behavior, it should say "should not
>> treat..."? If this is an ok behavior, maybe it should say "MAY treat ..."
>
> I agree that this paragraph might add confusion.  I think the section
> on Uncertainty and Confidence would be clearer if the whole paragraph
> were removed.
>
>> -[Page 12], "in the the case"---typo-->"in the case"
>
> Good catch.  There were three of these.
>
>> -[Page 12], "the OGC's "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
>> [OGCURL]. "
>>
>> Should the URL  be moved to reference section?
>
> Since http://www.opengis.net/def/crs/OGC/1.3/CRS84 is a URN, I don't
> think it makes sense to include in the reference section.  It would be
> nice if it resolved to something useful so it could serve as a
> reference though.
>
>> -[Page 13], "or to to have"--typo-->"or to have"
>
> Changed.
>
>> -[Page 16], "the the semantics"--typo-->"the semantics"
>
> Also changed.
>
>> -[Page 18], "can not be"---->"cannot be"
>
> Done.
>
> Tim
>
>>
>>
>> Best Regards,
>>
>> Meral
>>
>> ---
>>
>> Meral Shirazipour
>>
>> Ericsson Research
>>
>> www.ericsson.com