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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: RE: [Use Case:] PFC


Title: RE: [Use Case:] PFC

SAML format is here:
http://www.oasis-open.org/committees/security/docs/draft-sstc-doc-guidelines-02.txt

I believe the above guidelines were amended though to accept word files as acceptable for documents instead of requiring XML documents for everything. Also, JPEG is acceptable for images, but Powerpoint is required if any editing of the image will be needed. Also, I don't see it listed in here, but I think it is a good idea to include line numbering in the formatting of the document to ease discussion.

Regarding change history, I don't think it needs to be burdensome or overly complicated, but it is good to know why some types of changes are made. General editing and formatting don't have to be detailed, but the finalized use case could end up dramitically different from the original submission and it would help to know why significant changes were made. Having it in the document, I feel is better because it is available to the reviewer to read and understand and keeps us from having to set up an external revision control system.

Ken Yagen
Director, Software Development
CrossLogix, Inc
www.crosslogix.com
 

-----Original Message-----
From: bill parducci [mailto:bill@parducci.net]
Sent: Monday, August 13, 2001 1:31 PM
To: Ken Yagen; xacml
Subject: Re: [Use Case:] PFC


> Ken Yagen wrote:
>
> [...]
> Could we use a change history log detailing
> modifications to the use case with a date and brief description for
> the change?

i started out thinking that but then figured that maybe external
versioning control might be better (in terms of reflecting updates and
actually being used). what do you think? anyone else have an opinion?

> Also, will we have seperate glossaries for each use case
> or will the glossaries be merged into one?

i assume we will have a single dictionary/glossary, but in light of the
fact that we haven't finished that task yet (as far as i know), i
provided the field here to ensure that the message of the use case is
definitively conveyed. ostensibly, subsequent versions of the use cases
will reflect the adoption of a standardized glossary/dictionary. maybe
this will help drive the adoption of a standardized dictionary/glossary.

> Also, do we have a documentation standard for XACML documents? We
> could use the one from SAML.

that is fine with me. i chose lowest common denominator for the dev
cycle to make sure it is accessible to everyone easily. can you post the
saml format to this list? anyone think that this is not a good idea or
have an alternative?

thanks

b



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


Powered by eList eXpress LLC