Editorial comments on draft-sstc-saml-reqs-00

["Eve L. Maler" <eve.maler@east.sun.com>]

The numbers below refer to lines.  Some of the comments suggest new 
Glossary entries (which would affect draft-sstc-saml-spec-00) along with 
corrections/additions to the Requirements document text.

	Eve



1: Add header information according to guidelines

23ff: Add "UML", "use case", and "scenario" to Glossary

25: s/Modelling/Modeling/

34: Delete "use cases, i.e."

57: Add "The scenarios are not binding on the ultimate SAML design."

63ff: Rationalize use of "will" vs. "should" vs. "shall"

74: Delete "for"

76-80: Rationalize use of "timeout", "termination", "expiry" and define
in Glossary instead of here

81-83: Remove this sense of anonymous to the Glossary

146: s/detail/detail is/

171ff: Add "document" and "message" to Glossary or use other terms

173-177: What are these references, documents, and event descriptions?

273: Add "Buyer" and "Seller" labels to stick figures

286: Delete "The Web user is the Principal."

299: The word "responsible" seems to be hanging

319: Delete extra "security" and s/acts/act/

320: Delete "and" before Attribute Authority

325ff: Should these Steps be numbered?

360ff: Don't understand the user session use case

368: Delete "is" before "logs into"

371: Delete "and" before "Attribute Authority" and "a" before "Session
Authority"

379: Define "reference/token/ticket" or use different term

380: I don't understand how this differs from step 2

383: Add "and" before "optionally"

385: Is there a "Scenario 4-2 User Session Timeout" header missing?

392: Is there a "Scenario 4-3 User Session Logout" header missing?
--
Eve Maler                                             +1 781 442 3190
Sun Microsystems XML Technology Development  eve.maler @ east.sun.com