OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [security-services] New Templates for SAML 2.1

Hi Scott & all... 

Regarding conformance clauses and "But I don't know what OASIS actually allows or requires these days"... 

You have a lot of flexibility here. Since you are developing this as a multi-part work, the requirement for conformance clauses applies to the "thing" as a whole. In other words, so long as you have covered the clauses in some fashion, you're good. Some specs have consolidated all the clauses into their introductory document and pointed back to it from the parts, others have split clauses so that each part carries the relevant conformance clauses for their material. 

So really - whatever works best for you and your audience is ok by me. 



On Wed, Jan 22, 2014 at 12:02 AM, Cantor, Scott <cantor.2@osu.edu> wrote:
On 1/21/14, 7:28 PM, "La Joie, Chad" <Chad.LaJoie@covisint.com> wrote:
>First question: given our new focus on having these thematic documents
>be, in some regards, "the starting point", should they come immediately
>after the overview in our part list (actual titles to be determined

I'm maybe in the minority, but still feel like having foundational
documents earlier is better, with the profiles at the end.

>Second question: we discussed the possibility of rolling security
>considerations into the various thematic documents.  Do we still think
>that's a good idea?

I do.

>Last question: we talked before about the general inadequacy of the
>conformance documentation.  Should we try and roll that in to the
>thematic documents?

I think we ought to look at conformance statements covering the profiles
individually, but not try and build overarching conformance classes that
cover the standard as a whole into those documents.

But I don't know what OASIS actually allows or requires these days.

-- Scott

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

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

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]