Re: [security-services-comment] Minor typo issue with SAML V2.0 Metadata Extension for Entity Attributes Version 1.0 CS 01

[Chet Ensign <chet.ensign@oasis-open.org>]

Hi Scott,

Actually, other way around.

---
(7) Computer Language Definitions. All normative computer language
definitions that are part of the Work Product, such as XML instances,
schemas and Java(TM) code, including fragments of such, must be well
formed and valid.

(7a) For Standards Track Work Products:

All normative computer language definitions must be provided in
separate plain text files;
Each text file must be referenced from the Work Product; and
-->>Where any definition in these separate files disagrees with the
definition found in the specification, the definition in the separate
file prevails.<<--

---

So if there is a discrepancy between what you have in the
specification document and what is in the schema file, the schema file
trumps.

Best,

/chet

On Wed, Apr 18, 2012 at 12:54 PM, Cantor, Scott <cantor.2@osu.edu> wrote:
> On 4/18/12 12:35 PM, "Timothy Ace" <tace@synacor.com> wrote:
>>
>>If you notice, the <complexType> defines a <choice>, but then closes a
>><sequence>. This is by no means a major issue, but I figured I would
>>point it out. The rest of the spec looks great!
>
> Thank you for catching this.
>
> I imagine the schema artifact must be correct. Supposedly, OASIS considers
> the snippets in documents to be the authoritative schema now, which is,
> well, wrong. But this spec predates that decision in any case.
>
> We have not been collecting errata for post-2.0 work, but I'll file this
> in Jira somehow or in the wiki. I expect this document's material will be
> merged into a future update of the SAML metadata spec anyway, so it can
> get fixed then.
>
> -- Scott



-- 

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open