particular, is anyone doing schema validation?
On 2/14/12 4:08 PM, Martin Thomson wrote:
> Since the extension point in the existing schema is marked ##other and
> lax, a processor with an old schema will reject an instance document
> that contains the "unknown" {urn:ietf:params:xml:ns:pidf:rpid}:lunch
> element.
>
> That's a backwards compatibility break.
>
> --Martin
>
> On 14 February 2012 14:36, Robert Sparks <rjsparks@nostrum.com
> <mailto:rjsparks@nostrum.com>> wrote:
>
> This erratum will change the schema for RPID registered with IANA.
> (I've confirmed with IANA that they can handle a change made this way).
>
> There have been discussions in several groups about registry
> maintenance with some
> confusion about whether changes can be made to an existing schema.
> Our XML experts
> (Peter in this case) assure us that schema changes are OK.
>
> In most cases, I would ask that a change to a registration like this
> be done with a document.
> That's definitely required if we're doing anything more than
> correcting an obvious mistake.
> In this case, however, it is obvious that these values were intended
> to be included in the
> affected list from the beginning.
>
> I plan to approve this erratum a week from today. If you believe
> this is not the right thing to do,
> please speak now.
>
> RjS
>
>
> -------- Original Message --------
> Subject: [Technical Errata Reported] RFC4480 (3121)
> Date: Tue, 14 Feb 2012 13:54:39 -0800 (PST)
> From: RFC Errata System <rfc-editor@rfc-editor.org>
> <mailto:rfc-editor@rfc-editor.org>
> To: hgs+simple@cs.columbia.edu <mailto:hgs+simple@cs.columbia.edu>,
> vkg@lucent.com <mailto:vkg@lucent.com>, pkyzivat@cisco.com
> <mailto:pkyzivat@cisco.com>, jdrosen@cisco.com
> <mailto:jdrosen@cisco.com>, gonzalo.camarillo@ericsson.com
> <mailto:gonzalo.camarillo@ericsson.com>, rjsparks@nostrum.com
> <mailto:rjsparks@nostrum.com>, ben@nostrum.com
> <mailto:ben@nostrum.com>, hisham.khartabil@gmail.com
> <mailto:hisham.khartabil@gmail.com>
> CC: stpeter@stpeter.im <mailto:stpeter@stpeter.im>, simple@ietf.org
> <mailto:simple@ietf.org>, rfc-editor@rfc-editor.org
> <mailto:rfc-editor@rfc-editor.org>
>
>
>
> The following errata report has been submitted for RFC4480,
> "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4480&eid=3121 <http://www.rfc-editor.org/errata_search.php?rfc=4480&eid=3121>
>
> --------------------------------------
> Type: Technical
> Reported by: Peter Saint-Andre <stpeter@stpeter.im> <mailto:stpeter@stpeter.im>
>
> Section: 7.2
>
> Original Text
> -------------
> <xs:element name="looking-for-work"
> type="empty" />
> <xs:element name="meal"
> type="empty" />
>
> Corrected Text
> --------------
> <xs:element name="looking-for-work"
> type="empty" />
> <xs:element name="lunch"
> type="empty" />
> <xs:element name="meal"
> type="empty" />
>
> Notes
> -----
> Erratum #2959 claimed that the element "lunch" needs to be removed from the specification since it is not included in the schema. However, the schema was in error. This erratum corrects the schema so that, if approved, IANA can update the information at http://www.iana.org/assignments/xml-registry/schema/pidf/status/rpid.xsd
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC4480 (draft-ietf-simple-rpid-10)
> --------------------------------------
> Title : RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
> Publication Date : July 2006
> Author(s) : H. Schulzrinne, V. Gurbani, P. Kyzivat, J. Rosenberg
> Category : PROPOSED STANDARD
> Source : SIP for Instant Messaging and Presence Leveraging Extensions
> Area : Real-time Applications and Infrastructure
> Stream : IETF
> Verifying Party : IESG
>
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org <mailto:Geopriv@ietf.org>
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Simple mailing list
Simple@ietf.org
https://www.ietf.org/mailman/listinfo/simple
