Re: [Geopriv] draft-ietf-geopriv-uncertainty

Ray Bellis <Ray.Bellis@nominet.org.uk> Wed, 22 October 2014 15:00 UTC

DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To:CC: Subject:Thread-Topic:Thread-Index:Date:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=yLRU/Yxegq2xrEG0j9BrZbGrza2O/nXcfRXLLevevQ2nYjgPIfL24XSu DdyOVUBcqEyIwpIvl2mIW9WAbzLKdqzFEF36AgqpowuQK2HKgfZlr1F54 Ow0bLejyOJ53j31Su904Vkp7OeOWqHECuIkCZdvRyHKJV7lzjaabZhcQ/ OiJznFmhS24bzMms/JMfbVVPtnGvVCWWMbWe01xcm+LBjZgydOIHKU3Z+ bWo2Bnq8QQSd+z3//jJo3yN54oHRG;
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Julian Reschke <julian.reschke@gmx.de>
Thread-Topic: [Geopriv] draft-ietf-geopriv-uncertainty
Thread-Index: AQHP7gHvCdqAVG4TrkCGhgo2yWG0NZw8JPmA
Date: Wed, 22 Oct 2014 15:00:11 +0000
Message-ID: <586D89F0-48CE-4674-ADCF-78C2C0C11939@nominet.org.uk>
References: <54478BCA.6060305@gmx.de>
In-Reply-To: <54478BCA.6060305@gmx.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-ID: <47AA22738C0CB24E878700BBAA235642@okna.nominet.org.uk>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/geopriv/Ntxmv0mn3k1w3Mym8OYlL4zU1Lc
Cc: GEOPRIV <geopriv@ietf.org>, "draft-ietf-geopriv-uncertainty@tools.ietf.org" <draft-ietf-geopriv-uncertainty@tools.ietf.org>, "drafts-expert-review-comment@iana.org" <drafts-expert-review-comment@iana.org>
Subject: Re: [Geopriv] draft-ietf-geopriv-uncertainty
Precedence: list

> On 22 Oct 2014, at 11:49, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> Hi there.
> 
> I was asked to review the XML namespace registration, and I have  minor editorial comments.
> 
> <http://tools.ietf.org/html/draft-ietf-geopriv-uncertainty-03#section-8.1> defines the XML namespace
> 
>  "urn:ietf:params:xml:ns:geopriv:conf"
> 
> But that namespace name only occurs once more in the document (in the XML schema).
> 
> It *ought* to appear in <http://tools.ietf.org/html/draft-ietf-geopriv-uncertainty-03#section-4.1> (where the confidence element is described); alternatively, that section could refer to the schema.
> 
> Note that <http://tools.ietf.org/html/draft-ietf-geopriv-uncertainty-03#section-6.4> has the following example:
> 
>>     <pidf:presence
>>         xmlns:pidf="urn:ietf:params:xml:ns:pidf"
>>         xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
>>         xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
>>         xmlns:gs="http://www.opengis.net/pidflo/1.0"
>>         xmlns:gml="http://www.opengis.net/gml"
>>         xmlns:con="urn:ietf:params:xml:ns:pidf:geopriv:conf"
>>         entity="pres:alice@example.com">
>>       <dm:device id="sg89ab">
>>         <pidf:status>
>>           <gp:geopriv>
>>             <gp:location-info>
>>               <gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
>>                 <gml:pos>42.5463 -73.2512</gml:pos>
>>                 <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
>>                   850.24
>>                 </gs:radius>
>>               </gs:Circle>
>>   <!-- c -->  <con:confidence pdf="normal">67</con:confidence>
>>             </gp:location-info>
>>             <gp:usage-rules/>
>>           </gp:geopriv>
>>         </pidf:status>
>>         <dm:deviceID>mac:010203040506</dm:deviceID>
>>       </dm:device>
>>     </pidf:presence>
> 
> That example isn't XMLNS-wellformed, as the "con" namespace is undefined (and yes, that's why I couldn't find it when looking for uses of the newly defined namespace).


Julian,

I’m not an XMLNS guru, but isn’t the line at the top reading xmlns:con=“urn:ietf:params:xml:ns:pidf:geopriv:conf” creating “con” as an alias for that namespace?

kind regards,

Ray

[Geopriv] draft-ietf-geopriv-uncertainty Julian Reschke
Re: [Geopriv] draft-ietf-geopriv-uncertainty Ray Bellis
Re: [Geopriv] draft-ietf-geopriv-uncertainty Ray Bellis
Re: [Geopriv] draft-ietf-geopriv-uncertainty Julian Reschke
Re: [Geopriv] draft-ietf-geopriv-uncertainty Martin Thomson