LRI+IG+Analysis+Meeting+Minutes+2011-5-26

include component="page" wikiName="siframework" page="LRI Header" =LRI IG Analysis WG Meeting Minutes=
 * Date:** 05/26/2011
 * Time:** 3:00PM - 4:00PM EDT
 * Dial in:** 1-408-600-3600
 * Access code:** 665 924 380
 * Meeting Agenda:** 5/26/2011 Agenda

Attendance
Jitin Asnaani, Tom Boal, Kathryn Calderone, Joan DuHaime, Ernest Grove, Freida Hall, Kate Hamilton, Hal Jiang, Lester Keepper, Austin Kreisler, Jingdong Li, Nikolay Lipskiy, Cheryl Liu, Bob Lutolf, Ken McCaslin, Riki Merrick, Glen Moy, Nam Nguyen, Erik Pupo, Rob Snelick, Jonathan Tadese, Meredith Vida, Ken Willett, Bob Yencha

Action Items

 * = **#** ||= **Date Initiated** ||< **Action** ||= **Owner** ||= **Status** ||= **Date Closed** ||
 * = 1 ||= 05/26/2011 ||< Read over the [|Conformance Verbs] and [|Conformance Usage] documents and decide on group agreement next week. ||= All ||= Open ||=  ||
 * = 2 ||= 05/26/2011 ||< Look at and evaluate the [|Verb Usage Mapping] document. ||= All ||= Open ||=  ||

Agenda Items
1. Discussion of the [|Verb Usage Mapping] document, which consolidates the [|Conformance Verbs 2.8] and [|Conformance Verbs with Table]documents 2. Continue discussion of [|Conformance Usage] document

Meeting Notes

 * Optionality/Usage Indicator- For an implementation profile, all optional elements must be profiled to R, RE, C, CE, or X.
 * Description Required - It was determined that a receiving application shall process the information conveyed by the required element. However, one must be careful to differentiate between the sender and receiver.
 * A suggestion - Have two columns to define and make sure that document specifies between sender and receiver.
 * Verify and make sure that everyone knows which table is being referred to.
 * The receiver profile has a possibility of being optional.
 * X: shall not implement "X" Elements.
 * Group will define what X's and O's and R's mean.
 * The team agreed on "C" being defined as Conditional.

**Documents Reviewed**


 * MUST or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.


 * MUST NOT or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.


 * SHOULD or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.


 * SHOULD NOT or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.


 * MAY or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item.


 * An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)


 * Note that the force of these words is modified by the requirement level of the document in which they are used.

Next Meeting

 * Date:** 05/31/2011
 * Time:** 3:00PM - 4:00PM EDT
 * Dial in:**1-408-600-3600
 * Access code:** 660 141 868 (join WebEx first)

Reference Materials
 code code code
 * 1) [|Conformance Verb Document]
 * 2) [|Conformance Usage Document]
 * 3) [|Conformance Verbs v2.8]
 * Keywords to Indicate Requirement Levels **[1]**  **

code code The following keywords in this document are to be interpreted as follows: code code

code code ** MUST ** or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. code code code code ** MUST NOT ** or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification. code code code code ** SHOULD ** or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. code code code code ** SHOULD NOT ** or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. code code code code ** MAY ** or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. code code code code <span style="font-family: "Bookman Old Style","serif";">An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.) code code code code <span style="font-family: "Bookman Old Style","serif";">Note that the force of these words is modified by the requirement level of the document in which they are used. code

[1] <span style="font-family: "Bookman Old Style","serif"; font-size: 8.0pt;"> Adapted from IETF RFC 2119

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"