Re: Disposition of Comments for PDTR 14252 (part 1 of 2) The Disposition of Comments for PDTR 14252 is being distributed to WG15 in two segments. This first segment is the DoC for comments from the US. The second segment is the disposition of comments from SC22, which will be send out immediately following this message. This DoC, together with any additional modifications that may be generated at the editorial meeting to be held Thursday, October 20, will be presented to the WG15 meeting at Whistler, along with a recommendation (to be developed at the editorial meeting). Jon F. Spencer spencerj@rtp.dg.com (uunet!rtp.dg.com!spencerj) Data General Corp. Phone : (919)248-6246 62 T.W. Alexander Dr, MS #119 FAX : (919)248-6108 or 6352 or 5942 Research Triangle Park, NC 27709 Office RTP 116/3 Reality is an illusion - perception is what counts. There is no amount of success that can compensate for failure at home. --------------------------------------------------------------------------------------------------------------------- United States Comments concerning PDTR 14252 on "Guide to the POSIX Open System Environment", doc. ISO/IEC JTC 1/SC 22 N 1596, alias IEEE P1003.0 Draft 16.1 --------------------------------------------------------------------------------------------------------------------- @ 202 Entire Document c 2 2. Sect Entire Document. Editorial Comments - Typos PROBLEM: Typos in document. ACTION: Page 203, line 4: modify from: "... by users who wants ..." should be to: "... by users who want ..." Page 207, line 162: modify from: "Attempts to exclude options in implementations becomes ..." to: "Attempts to exclude options in implementations become ..." Page 211, lines 337, 344: delete the phrase such as the work being done by POSC Page 213, line 6: modify from: "both AEPs and platforms profiles." should be to: "both AEPs and platform profiles." DISPOSITION: Accept CHANGE TO DOCUMENT: Page 203, line 4: modify from: "... by users who wants ..." should be to: "... by users who want ..." Page 207, line 162: modify from: "Attempts to exclude options in implementations becomes ..." to: "Attempts to exclude options in implementations become ..." Page 211, lines 337, 344: delete the phrase such as the work being done by POSC Page 213, line 6: modify from: "both AEPs and platforms profiles." should be to: "both AEPs and platform profiles." ------------------------------------------------------------------------- @ 205 0 c 2 2. Sect General COMMENT Problem: There is an inconsistency in the format used to reference standards in the tables. For example see Table 4-6, pg 74, line 1209 and line 1211. In one case the 'name' of the standard is given, and in the other it is not. This inconsistency is pervasive throughout the document. The name, however, is a helpful cue to the reader as to the significance of the specification and should be used where available. ACTION: Add brief names to standards tables where such names are available and space is available. DISPOSITION: Accept CHANGE TO DOCUMENT: Add brief names to standards tables where such names are available and space is available. ------------------------------------------------------------------------- @ 205 0 c 1 1. Sect General COMMENT Problem: It is my understanding that 'P1003.x' refers to the working group and '1003.x' refers to the actual documents. The OSE document refers to both the working group and the document with 'P1003.x'. ACTION: Please verify the correct way to reference the working groups and documents and make the necessary changes to the text (i.e. 'P1003.x' refers to the working group and '1003.x' refers to the actual documents). DISPOSITION: Accept CHANGE TO DOCUMENT: Please verify the correct way to reference the working groups and documents and make the necessary changes to the text (i.e. 'P1003.x' refers to the working group and '1003.x' refers to the actual documents). ------------------------------------------------------------------------- @ 201 3.y o 5 5 Section 3.y OBJECTION. page 21, line 1 to end PROBLEM: There is much inconsistency in the use of the term "service", throughout Section 3, per the definition in Section 2. The confusion caused by the usage is so pervasive that it is not reasonable to identify each of them. The following list of terms and their incorrect usage in Section 3 illustrates the pervasive nature of the inconsistencies. Section page line 3 21 1 3 21 29 3.1 22 37 3.2.3 32 364 3.3 34 413 3.2.3 32 365 4 39 1 4.n.5.1 40 54 4.1 41 103 (title) 4.2 50 385 (title) 4.2.4 52 431 (title) 4.2.4.1 52 447 (title) 4.2.4.1 52 457 4.2.4.1.2 54 539 (title) 4.2.6 63 838 (title) 4.2.6.1 63 839 (title) - and many others The text and the definition are inconsistant, but it is the definition which requires modification. The service is the *functionality* provided at the interface, not the *method* by which the functionality is provided. The method of provision is a characteristic of the standard selected, and may change as new standards are selected. ACTION: modify section 2.2.2.45 service, pg. 18 line 254 to read as follows: service: The functionality which is provided to ... DISPOSITION: Accept CHANGES TO DOCUMENT: modify section 2.2.2.45 service, pg. 18 line 254 to read as follows: service: The functionality which is provided to ... ------------------------------------------------------------------------------- @ 211 gen c 4 PROBLEM: Index is too thin, too light, at only 5% of the size of the text. ACTION: Add the following term to the index: scope of concensus A complete set of index references will generated when the document moves to international ballot. DISPOSITION: Accept CHANGE TO DOCUMENT: Add the following term to the index: scope of concensus A complete set of index references will generated when the document moves to international ballot. ---------------------------------------------------------------------------------------------------------------------- POSIX .0 Section 3 Comments and Objections ---------------------------------------------------------------------------------------------------------------------- @ 205 3.1 c 30 30. Sect 3.1 COMMENT. p.22, line 36: Problem: Title is inconsistent. DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.1, on p.22, line 36, delete the hyphen from the title. ------------------------------------------------------------------------- @ 201 3.1 o 6 6 Section 3.1 OBJECTION. page 23, line 81: PROBLEM: OSE standards that define functionality are exempted by the text, and should be included. ACTION: modify section 3.1, pg. 23 line 81 to read as follows: OSE standards specify methods to access services at interfaces, and do not specify service implementation. However, where the standard must refer ... DISPOSITION: Accept CHANGES TO DOCUMENT: modify section 3.1, pg. 23 line 81 to read as follows: OSE standards specify methods to access services at interfaces, and do not specify service implementation. However, where the standard must refer ... ------------------------------------------------------------------------- @ 201 3.1 o 7 7 Section 3.1 OBJECTION. page 23, line 88: PROBLEM: The text suggests scalability applies only to a single platform. Scalability also applies to systems that dribute processing across multiple platforms. The matter of complexity is irrelevant to scalability. Note: distributed system scalability is a separate issue and is addressed in the text which follows on lines 97 through 107. ACTION: modify to read ... to allow inclusion of platforms with varying speed, throughput, and implementation architecture (e.g. multiprocessing)." DISPOSITION: Accept CHANGES TO DOCUMENT: modify to read ... to allow inclusion of platforms with varying speed, throughput, and implementation architecture (e.g. multiprocessing)." ------------------------------------------------------------------------- @ 201 3.2 o 10 10 Section 3.2 OBJECTION. page 24, line 80: PROBLEM: This entire section, 3.2, deals with the POSIX OSE while the text of the section is generalized to all OSEs. The details described in Section 3.2 apply to POSIX OSEs but may not be correct for non-POSIX OSEs. ACTION: None: The requested changes are implemented in Draft 16.1. DISPOSITION: Accept CHANGES TO DOCUMENT: None: The requested changes are implemented in Draft 16.1. ------------------------------------------------------------------------- @ 205 3.1 c 31 31. Sect 3.1 COMMENT. p.24, line 109: Problem: Sentence is missing text. ACTION: In section 3.1 on p.24, line 109, insert the phrase "the application regardless of" between "to" and "the". DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.1 on p.24, line 109, insert the phrase "the application regardless of" between "to" and "the". ------------------------------------------------------------------------- @ 201 3.1 o 8 8 Section 3.1 OBJECTION. page 24, line 114 PROBLEM: Interface definitions do not completely define an application platform. They may define the aspects of that platform that are relevant to OSE. ACTION: Modify section 3.1 page 24, line 114 as follows: Insert the following between the" and "application": "means by which a service is obtained from an". DISPOSITION: Accept CHANGES TO DOCUMENT: Modify section 3.1 page 24, line 114 as follows: Insert the following between the" and "application": "means by which a service is obtained from an". ------------------------------------------------------------------------- @ 205 3.1 o 32 32. Sect 3.1 OBJECTION. p.24, line 114-115: Problem: The sentence "The interface specifications are the complete definition of the application platform" is not true. The interface specifications are at best the boundary between the application and the application platform. ACTION: In section 3.1, in p.24, line 114-115: Modify the sentence to read "The interface specifications should provide a complete definition of the behavior of the application platform at those interfaces. DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.1, in p.24, line 114-115: Modify the sentence to read "The interface specifications should provide a complete definition of the behavior of the application platform at those interfaces. ------------------------------------------------------------------------- @ 205 3.1 c 33 33. Sect 3.1 COMMENT. p.24, line 115-116: Problem: Bad grammar and no value added in the last sentence of this paragraph. ACTION: In sect 3.1, on p.24, line 115-116, delete the last sentence. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.1, on p.24, line 115-116, delete the last sentence. ------------------------------------------------------------------------- @ 209 3.1 o 4 4 Section 3.1 OBJECTION p. 24 lines: 117-123 PROBLEM: This paragraph on ``Functional Requirements of the User'' is unclear or ambiguous. I'm not sure :-) The entire section (3.1) seems to be a statement of the objectives of an OSE, based on the principles of portability and interoperability. This objective seems self-referential. It is possible to achieve application portability and interoperability in a variety of ways. The additional requirements place further constraints on the solution. For example, it is possible to achieve portability by selecting a single vendor or implementation of the technology. The added requirement for Accomodation of Standards provides for multi-vendor solutions. In the case of the obejctive cited, some could claim that portability and interoperability is achieved when the portable functionality includes only operating system services, while others would require portable graphical user interface, data storage and communications services. This objective explicitly states that the user of the information system which is the final authority with respect to completeness of the services required, and that broader, rather than narrower scope of functionality is required. ACTION: In section 3.1, on p. 24 substitute for the last sentence on lines: 121-123. The user of the information system is the final authority with respect to completeness of the services required to achieve full portability. In particular, the range of services required is broader than those traditionally identified as operating system services. DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.1, on p. 24 substitute for the last sentence on lines: 121-123. The user of the information system is the final authority with respect to completeness of the services required to achieve full portability. In particular, the range of services required is broader than those traditionally identified as operating system services. ------------------------------------------------------------------------------- @ 205 3.1 c 34 34. Sect 3.1 COMMENT. p.24, line 120: Problem: Inconsistent adjective to portability. ACTION: In section 3.1 on . p.24, line 120, change software to application software. DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.1 on . p.24, line 120, change software to application software. ------------------------------------------------------------------------- @ 203 3.1 c 3 3 Sect 3.2 EDITORIAL COMMENT page 25 line 155 PROBLEM: "the basic elements" has been changed to "the OSE reference model", so the reference to "these" in the next sentence is now incorrect. ACTION: In sect 3.2 on page 25 line 155, replace "These include ..." with "The model identifies ...". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2 on page 25 line 155, replace "These include ..." with "The model identifies ...". ------------------------------------------------------------------------- @ 205 3.2 c 36 36. Sect 3.2 COMMENT. p.25, line 160-161: Problem: Sentence is awkward. ACTION: In sect 3.2, on p.25, line 160-161, A more detailed discussion of each service category is provided in section 4. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2, on p.25, line 160-161, A more detailed discussion of each service category is provided in section 4. ------------------------------------------------------------------------- @ 205 3.2 c 37 37. Sect 3.2 COMMENT. p.26, line 181: Problem: Sentence is redundant. ACTION: In sect 3.2 on p.26, line 181, delete "the" and second occurrence of "discussion"; add an "s" to "EEI". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2 on p.26, line 181, delete "the" and second occurrence of "discussion"; add an "s" to "EEI". ------------------------------------------------------------------------- @ 205 3.2 c 38 38. Sect 3.2 COMMENT. p.26, line 197: Problem: Parenthetical statement adds no value to the discussion. ACTION: In sect 3.2 on p.26, line 197 delete "(i.e., "things")". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2 on p.26, line 197 delete "(i.e., "things")". ------------------------------------------------------------------------- @ 201 3.2.1 c 11 11 Section 3.2.1 COMMENT. page 28, line 249: PROBLEM: The reference to an "average person" is misleading. It is impossible, in a practical sense, to identify even a single person who exhibits all the arithmetic averages for human factors. ACTION: In Section 3.2.1 on page 28, line 249 Replace "average" by "typical". DISPOSITION: Accept CHANGES TO DOCUMENT: In Section 3.2.1 on page 28, line 249 Replace "average" by "typical". ------------------------------------------------------------------------- @ 205 3.2.2 c 40 40. Sect 3.2.2 COMMENT. p.28, line 256-258: Problem: These two sentences are awkward as separate paragraphs. ACTION: In sect 3.2.2, on p.28, line 256-258 combine two sentences into one paragraph. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2.2, on p.28, line 256-258 combine two sentences into one paragraph. ------------------------------------------------------------------------- @ 208 3.2 c 5 5. Section 3.2.2.2 COMMENT. Page 30, Line 313 Problem: "Communications Services, including communications services" is redundant and not particularly informative. If there is no lower-level concept it makes sense to list, nothing should be listed. ACTION: In section 3.2.2.2, on page 30, line 313 this bullet should say just "Communication Services". DISPOSITION: Accept CHANGE TO DOCUMENT: In section 3.2.2.2, on page 30, line 313 this bullet should say just "Communication Services". ------------------------------------------------------------------------------ @ 205 3.2.2.2 c 41 41. Sect 3.2.2.2 COMMENT. p.31, line 323: Problem: Wordy intro. ACTION: In sect 3.2.2.2, on p.31, line 323, modify the first sentence to read "These four categories of API services describe the range. . ." DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2.2.2, on p.31, line 323, modify the first sentence to read "These four categories of API services describe the range. . ." ------------------------------------------------------------------------- @ 205 3.2.3 c 42 42. Sect 3.2.3 COMMENT. p.32, line 368-369: Problem: The phrase 'and can be thought of as having been "translated" into,' adds no value to the discussion. ACTION: In sect 3.2.3, on p.32, line 368-369: modify the phrase '... the API is dependant upon, and can be thought of as having been "translated" into, communication ... ' to read ... the API is dependant upon communication ... DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2.3, on p.32, line 368-369: modify the phrase '... the API is dependant upon, and can be thought of as having been "translated" into, communication ... ' to read ... the API is dependant upon communication ... ------------------------------------------------------------------------- @ 207 3.2 o 1 1. Sect 3.2.4 OBJECTION. page 33, line 393 PROBLEM: The graphic (Figure 3-5) incorrectly labels the interconnection between the two application platforms. ACTION: In sect 3.2.4 on page 33, line 393, re-label Communications Services API inside the perceived application platform as communications Services EEI DISPOSITION: Accept CHANGES TO DOCUMENT: In sect 3.2.4 on page 33, line 393, re-label Communications Services API inside the perceived application platform as communications Services EEI ------------------------------------------------------------------------- @ 205 3.2.4 c 43 43. Sect 3.2.4 COMMENT. p.33, line 401: Problem: Redundant use of "for example" as it is already stated in line 398. ACTION: In sect 3.2.4, on p.33, line 401 delete the phrase "For example,". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.2.4, on p.33, line 401 delete the phrase "For example,". ------------------------------------------------------------------------- @ 205 3.3 c 44 44. Sect 3.3 COMMENT. p.34, line 413-421: Problem: This paragraph doesn't add value to the discussion and actually hurts the argument. ACTION: In sect 3.3, on p.34, line 413-421: reword the paragraph to read "Applications may use services that are distributed among a number of different computers. This implies that one application may use many POSIX services." DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.3, on p.34, line 413-421: reword the paragraph to read "Applications may use services that are distributed among a number of different computers. This implies that one application may use many POSIX services." ------------------------------------------------------------------------- @ 205 3.4 c 46 46. Sect 3.4 COMMENT. p.34, Line 439: Problem: "Therefore" implies cause and effect, which doesn't appear to be the case between these two paragraphs. ACTION: In sect 3.4 on p.34, Line 439: delete the "Therefore,". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4 on p.34, Line 439: delete the "Therefore,". ------------------------------------------------------------------------- @ 205 3.4.1.1 c 47 47. Sect 3.4.1.1 COMMENT. p.35, Line 449: Problem: Current wording implies a continuum, however, in this clause should be describing the general concept. The idea of a continuum is important. It would be difficult to imagine a perfectly open forum, i.e. one that has absolutely no barriers to participation. The openness of a forum can only be judged in a relative sense. If the criteria cited included only completely open forums, it is possible that none would qualify. ACTION: In sect 3.4.1.1 on p.35, Line 449 replace the second sentence in the paragraph with: The fewer the barriers to participation, and the greater the number of contituencies represented, the more open is the forum. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.1.1 on p.35, Line 449 replace the second sentence in the paragraph with: The fewer the barriers to participation, and the greater the number of contituencies represented, the more open is the forum. ------------------------------------------------------------------------- @ 201 3.4.1.1 o 12 12 Section 3.4.1.1 OBJECTION. page 35, line 450: PROBLEM: The concept of openness as applied to standards remains unaffected by whether all affected constituencies are represented. The matter for concern is that they may be represented, not that they actually are. ACTION: In Section 3.4.1.1 on page 35, line 450 replace "are" by "may be". DISPOSITION: Accept CHANGES TO DOCUMENT: In Section 3.4.1.1 on page 35, line 450 replace "are" by "may be". ------------------------------------------------------------------------- @ 201 3.4.1.2 c 13 13 Section 3.4.1.2 COMMENT. page 35, line 457: PROBLEM: The text implies there is a standards life cycle. The only one with which I am familiar came from X3. ACTION: Replace Section 3.4.1.2 page 35, line 457-459 with the following text: Most standards follow a sequence from approved development, through draft, and so on to approved standard, in a process which has been defined by the standards development body. The progression and expected completion date for the final specification need to be taken into account. DISPOSITION: Accept CHANGES TO DOCUMENT: Replace Section 3.4.1.2 page 35, line 457-459 with the following text: Most standards follow a sequence from approved development, through draft, and so on to approved standard, in a process which has been defined by the standards development body. The progression and expected completion date for the final specification need to be taken into account. ------------------------------------------------------------------------- @ 205 3.4.1.2 c 48 48. Sect 3.4.1.2 COMMENT. p.35, Line 460-461: Problem: Tense inconsistent with rest of document. ACTION: In sect 3.4.1.2, on p.35, Line 460-461: reword to read ". . .choices are required among standards, those approved or close to approval are favored". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.1.2, on p.35, Line 460-461: reword to read ". . .choices are required among standards, those approved or close to approval are favored". ------------------------------------------------------------------------- @ 205 3.4.1.3 c 49 49. Sect 3.4.1.3 COMMENT. p.35, Line 463: Problem: Use of the second "This" is inappropriate. ACTION: In sect 3.4.1.3, on p.35, Line 463: change the second "This concept ..." to "The concept of stability ...". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.1.3, on p.35, Line 463: change the second "This concept ..." to "The concept of stability ...". ------------------------------------------------------------------------- @ 205 3.4.1.4 c 50 50. Sect 3.4.1.4 COMMENT. p.35, Line 470: Problem: The phrase "Formal standards development bodies" differs from the defined phrase in this document. ACTION: In sect 3.4.1.4, on p.35, Line 470: change to "Accredited standards development bodies". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.1.4, on p.35, Line 470: change to "Accredited standards development bodies". ------------------------------------------------------------------------- @ 201 3.4.2.2 o 14 14 Section 3.4.2.2 OBJECTION. page 37, line 514: PROBLEM: It is inappropriate for an IEEE guide to include as references, for inclusion in a model, those documents that fail to meet key factors in standards selection (refer to Section 3.4). 1. Openness - often there are obstacles to participation that are much more harsh than those of traditional voluntary standards organizations 2. Stage of Development - often organizations do not exhibit sound management principles for the control of their requirements definition process and engineering development process 3. Stability - often the processes are uncontrolled from the perspective of the organization's members and as such design changes are frequent 4. Geographic Scope of Consensus - often the scope of geographic applicability is not a consideration in specifications developed outside the formal standards process 5. Functional Scope Addressed Within this Guide - since this document is the product of a formal standards organization, its scope should remain limited to formal standards 6. Consistency with ISO/IEC 9945-1 - often specifications that are potentially related to the scope of the guide do not even address their relationship to 9945-1 7. Availability for Unencumbered Implementation - often there are encumbrances that are barriers to implementation ACTION: In Section 3.4.2.2 on page 37, line 514 Substantial investment of time and resource is made after an organization commits itself to a specification, and such committment should be carefully considered. The following concepts identify some of the criteria used to select standards for inclusion in the POSIX OSE. Other organizations may find these criteria useful as well, in situations where no clear cut selection is available, and judgement is required. DISPOSITION: Accept CHANGES TO DOCUMENT: In Section 3.4.2.2 on page 37, line 514 Substantial investment of time and resource is made after an organization commits itself to a specification, and such committment should be carefully considered. The following concepts identify some of the criteria used to select standards for inclusion in the POSIX OSE. Other organizations may find these criteria useful as well, in situations where no clear cut selection is available, and judgement is required. ------------------------------------------------------------------------- @ 217 gen o 1 PROBLEM: The document acknowledges a "real world" and "defacto standards" without providing the definitions. It is recognized, however, this document is not a standard, but a guide to user organizations (and others) in identifying standards which address the objectives listed in section 3.1. Where no standards exist, we provide guidance in identifying and selecting specifications which have not been formally balloted, but which have some concensus. Use of these public specifications is suggested only where the alternatives are to (1) adopt one vendors proprietary specifications or (2) stop work and wait for the standards community to deliver a specification. This is a pressing problem for many users. A de facto standard is one which has been widely accepted in practical use by the users. This may include widely used formal standards, consortia documents, or product offerings that are widely used. a very useful form of specification is one which is both a de facto and a formal standard. ACTION: On pg 37, lines 514-516, replace existing text with Approved (as opposed to draft) specifications (widely adopted, but not formal standards) developed and/or maintainted in an open forum including consortia specifications or certain de facto standards. Add text to pg. 37, between 518 and 519, A defacto standard is one which has been widely accepted in practical use by users. This may include widely used formal standards, consortia documents or product offerings that are widely used. a very useful form of specification is one which is both a de facto and a formal standard. DISPOSITION: Accept CHANGE TO DOCUMENT: On pg 37, lines 514-516, replace existing text with Approved (as opposed to draft) specifications (widely adopted, but not formal standards) developed and/or maintainted in an open forum including consortia specifications or certain de facto standards. Add text to pg. 37, between 518 and 519, A defacto standard is one which has been widely accepted in practical use by users. This may include widely used formal standards, consortia documents or product offerings that are widely used. a very useful form of specification is one which is both a de facto and a formal standard. ------------------------------------------------------------------------------- @ 205 3.4.2.2 c 51 51. Sect 3.4.2.2 COMMENT. p.37, Line 515: Problem: Use of undefined term "formal standards". ACTION: In sect 3.4.2.2, on p.37, Line 515: modify to read ... formal, balloted standards ... DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.2.2, on p.37, Line 515: modify to read ... formal, balloted standards ... ------------------------------------------------------------------------- @ 205 3.4.2.2 c 52 52. Sect 3.4.2.2 COMMENT. p.37, Line 516-518: Problem: Parenthetical comments add no value. ACTION: In sect 3.4.2.2, on p.37, Line 516-518: delete parenthetical comments DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.4.2.2, on p.37, Line 516-518: delete parenthetical comments ------------------------------------------------------------------------- @ 205 3.5 c 53 53. Sect 3.5 EDITORIAL COMMENT. p.37, Line 524: Problem: Font size is inconsistent. ACTION: In sect 3.5, on p.37, Lines 524 and 536: make font consistent with other clause titles. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.5, on p.37, Lines 524 and 536: make font consistent with other clause titles. ------------------------------------------------------------------------- @ 209 3.5 o 5 5 Section 3.5 OBJECTION p. 37 lines: 524-535 Problem: This section is titled POSIX Profiles, yet it NEVER mentions the word POSIX anywhere within it. The text seems to address a simple introduction to profiling concepts within Section 3. ACTION: In section 3.5 on p. 37 lines: 524, change the title to read POSIX OSE Profiles. Append the following sentence to the first paragraph (line 527) POSIX OSE profiles are those which restrict themselves to standards providing services at the interfaces identified in the POSIX OSE reference model. DISPOSITION: Accept CHANGE TO THE DOCUMENT: In section 3.5 on p. 37 lines: 524, change the title to read POSIX OSE Profiles. Append the following sentence to the first paragraph (line 527) POSIX OSE profiles are those which restrict themselves to standards providing services at the interfaces identified in the POSIX OSE reference model. ------------------------------------------------------------------------------- @ 201 3.5 o 16 16 Section 3.5 OBJECTION. page 37, line 525: PROBLEM: The use of the term "base standard" in this sentence is inconsistent with the definition in Section 2. ACTION: In Section 3.5 on page 37, line 525, replace "are collected into" by "contribute to". DISPOSITION: Accept CHANGES TO DOCUMENT: In Section 3.5 on page 37, line 525, replace "are collected into" by "contribute to". ------------------------------------------------------------------------- @ 201 3.5 o 17 17 Section 3.5 OBJECTION. page 37, line 533: PROBLEM: The OSE itself does not help to characterize functionality. The POSIX OSE model does that. ACTION: In section 3.5 on page 37, line 533, replace "OSE" by "POSIX OSE model". DISPOSITION: Accept CHANGES TO DOCUMENT: In section 3.5 on page 37, line 533, replace "OSE" by "POSIX OSE model". ------------------------------------------------------------------------- @ 208 3.6 e 6 6. Sect. 3.6 EDITORIAL COMMENT. Page 37, Line 536 Problem: At this point the acronym "PII" has not been defined in the main text, although it has been in the Terms Definition section. ACTION: It should be written out in full in this section, probably in the section title. DISPOSITION: Accept CHANGE TO DOCUMENT: Expand the PII acronym on both line 536 and 543 to Platform Internal Interfaces. ------------------------------------------------------------------------------ @ 205 3.6 c 54 54. Sect 3.6 COMMENT. p.37, Line 536: DISPOSITION: accept ACTION: In sect 3.6, on p.37, Line 536 and 543: Expand the acronym PII to Platform Internal Interfaces. as in 3.2.2.1 and 3.2.2.2. DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.6, on p.37, Line 536 and 543: Expand the acronym PII to Platform Internal Interfaces. as in 3.2.2.1 and 3.2.2.2. ------------------------------------------------------------------------- @ 205 3.6 o 55 55. Sect 3.6 OBJECTION. p.37, Line 538-539: Problem: A new concept is introduced that is beyond the objectives of the application platform, namely, "platform interoperability". ACTION: In sect 3.6, on p.37, Line 538-539: modify to read "and application interoperability". DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 3.6, on p.37, Line 538-539: modify to read "and application interoperability". ------------------------------------------------------------------------- @ 209 4.0 o 6 6 Section 4 OBJECTION p. 39 lines: 1-2 PROBLEM: The text makes a general hand wave to ``objectives identified in this guide.'' What objectives? The 3.1 objectives? The Scope? ACTION: In section 4, on p. 39 lines: 1-2, modify the text to read as follows: ... objectives identified in section 3.1 of this guide. DISPOSITION: Accept CHANGE TO DOCUMENT: In section 4, on p. 39 lines: 1-2, modify the text to read as follows: ... objectives identified in section 3.1 of this guide. ------------------------------------------------------------------------------- @ 219 (b124c24) 4.0 o 1 #24 Sect 4 et al OBJECTION page 40-41, line 48, 74-84: PROBLEM: It is not clear what authority mandates when something is a "public specification, or being listed with a "P" designation in any and all sections. However, it is recognized that this document is not a standard, but a guide to user organizations (and others) in identifying standards which address the objectives listed in section 3.1. Where no standards exist, we provide guidance in identifying and selecting specifications which have not been formally balloted, but which have some concensus. Use of these public specifications is suggested only where the alternatives are to (1) adopt one vendors proprietary specifications or (2) stop work and wait for the standards community to deliver a specification. This is a pressing problem for many users. The process, selection criteria, precendence order, etc. suggested within the guide are not mandated for use by any individual or organization. The guidance in this document is the result of substantial discussion among people who have had standard selection responsibility for their organizations, and is no more or less than expert advice. See rationale document number 1 ACTION: In section 4.0, on pg. 41 line 79, delete the word all and insert consortia after government. On line 84, insert the following sentence before the sentence that starts with The risks must... There is also risk because such specifications are not approved by an accredited SDO. DISPOSITION: Accept CHANGE TO THE DOCUMENT: In section 4.0, on pg. 41 line 79, delete the word all and insert consortia after government. On line 84, insert the following sentence before the sentence that starts with The risks must... There is also risk because such specifications are not approved by an accredited SDO. ------------------------------------------------------------------------------- @ 205 5 c 120 56. Sect 4.1.1 COMMENT. p.42, Line 122: Problem: Phrase "is not standards conforming" is awkward. ACTION: In sect 4.1.1, on p.42, Line 122: reword to read ". . .code that does not conform to the standard." DISPOSITION: Accept CHANGE TO DOCUMENT: In sect 4.1.1, on p.42, Line 122: reword to read ". . .code that does not conform to the standard." ------------------------------------------------------------------------- Ballot resolution Ballots: 20 - Fritz Schulz Objections/Comments 53/38 Ballot resolution Ballots: 20 - Fritz Schulz Objections/Comments 53/38 page 16 3/10/94 page 17 3/10/94 Re: PDTR 14252 Disposition of Comments, Part 2 of 2 This segment contains the SC22 comments. -- Jon F. Spencer spencerj@rtp.dg.com (uunet!rtp.dg.com!spencerj) Data General Corp. Phone : (919)248-6246 62 T.W. Alexander Dr, MS #119 FAX : (919)248-6108 or 6352 or 5942 Research Triangle Park, NC 27709 Office RTP 116/3 Reality is an illusion - perception is what counts. There is no amount of success that can compensate for failure at home. ---------------------------------------------------------------------------- Ballot Disposition Summary National Body # Disposition Subject ------------------------------------------------------------------------------------------------------------------------------- Netherlands 101 Accept - EEI/PEI terms and TR10K-3 102 Accept - add SDO definition 103 Accept - delete reference to services 104 Accept - definitions application platform & service 105 Accept - definitions profile & base standard 106 Accept - have definition of EEI address services 107 Accept - change applications to application 108 Accept - change software and data to application 109 Accept - change 'information system' by 'application platform' 110 Accept - see item Netherlands 105 111 Accept - usage of the term entity 112 Accept - see item Netherlands 104 113 Accept - see item Netherlands 104 114 Accept - Data Portability 115 Accept - Entity and Component 116 Accept - replace 'OSE' by 'POSIX OSE' 117 Accept - insert 'POSIX OSE' in figure title 118 Accept - usage of terms 'services' and 'facilities' 119 Accept - delete the term 'Programming' 120 Accept - insert term API services into figures 121 Accept - citation of REXX as programming language 122 Accept - insert 'POSIX OSE' in figure title 123 Accept - unit of concurrency 124 Accept - align figure with Communications service section titles 125 Accept - insert 'POSIX OSE' in figure title 126 Accept - duplicate discussion of communications services 127 Accept - list communications API service categories 128 Accept - system to platform 129 Accept - system to platform 130 Accept - qualify services as communications 131 Accept - qualify services as communications 132 Accept - interface arrows and 1003.8 133 Accept - insert 'POSIX OSE' in figure title 134 Accept - database application 135 Accept - database services 136 Accept - database services 137 Accept - service components 138 Accept - key entities 139 Accept - insert POSIX OSE in figure title 140 Accept - insert POSIX OSE in figure title 141 Accept - transaction processing 142 Accept - TP table and section titles 143 Accept - command -> user command 144 Accept - user command 145 Accept - insert POSIX OSE in figure title 146 Accept - incomplete user command API service discussion 147 Accept - description of ISO/IEC JTC1 9945-2 148 Accept - character based user interface 149 Accept - terminal -> user 150 Accept - insert POSIX OSE in figure title 151 Accept - modern component 152 Accept - window system application software entity diagram 153 Accept - insert 'POSIX OSE' in figure title 154 Accept - entities/services discussions 155 Accept - window system API 156 Accept - synchronize service diagram and list 157 Accept - windowing system interapplication services 158 Accept - insert POSIX OSE in figure title 159 Accept - delete computer 160 Accept - insert POSIX OSE in figure title 161 Accept - virtual device 162 Accept - virtual device 163 Accept - virtual device 164 Accept - development -> development support 165 Accept - insert 'POSIX OSE' in figure title 166 Accept - OSE to POSIX OSE 167 Accept - insert 'POSIX OSE' in figure title 168 Accept - EWOS profile process reference Japan 002 Accept - TR10K-3 Harmonization 003 Accept - TR10K-3 Harmonization 006 Accept - TR10K-3 Harmonization 014 Accept - TR10K-3 Harmonization 024 Accept - TR10K-3 Harmonization --------------------------------------------------------------------------------------------------------------------- NNI Comments concerning PDTR 14252 on "Guide to the POSIX Open System Environment", doc. ISO/IEC JTC 1/SC 22 N 1596, alias IEEE P1003.0 Draft 16.1 ------------------------------------------------------------------------------------------------------------------ Netherland-101 Section 2 ACTION: - replace the term 'External Environment Interface (EEI)' by 'Platform External Interface (PEI)' and 'External Environment' by 'External World' conform ISO/IEC TR 10000-3. DISPOSITION: Accept DTR 14252 text is consistant with June 94 version of TR10000-3 (under ballot as a PDTR). The ballot version of TR10000-3 does not use the term PEI, but does use the term "external environment interface". CHANGE TO DOCUMENT: none ------------------------------------------------------------------------------------------------------------------ Netherland-102 Section 2 ACTION: line 99/100: define the term 'standards development organization' DISPOSITION: Accept. CHANGE TO DOCUMENT: After line 267, add,  Standards Development Organization. An accredited organization that formally develops and coordinates standards for use by a community. ------------------------------------------------------------------------------------------------------------------ Netherland-103 Section 2 ACTION: line 102: delete the term 'services', because this term is already used in a different specific meaning DISPOSITION: Accept CHANGE TO DOCUMENT: On line 102, delete, (services/facilities). ------------------------------------------------------------------------------------------------------------------ Netherland-104 Section 2 ACTION: line 109: the term 'application platform' is circular defined with the term 'service' (2.2.2.45) DISPOSITION: Accept. CHANGE TO DOCUMENT: On lines 254 and 255, change the definition of service to,A distinct part of the functionality which is provided by an entity on one side of an interface to an entity on the other side of the interface. ------------------------------------------------------------------------------------------------------------------ Netherland-105 Section 2 ACTION: line 120: the term 'base standard' is circular defined with the term 'profile' (2.2.2.38) DISPOSITION: Accept. CHANGE TO DOCUMENT: delete the following text from lines 121, ...that is used in the definition of a profile. ------------------------------------------------------------------------------------------------------------------ Netherland-106 Section 2 ACTION: line 138/139 : why "information is exchanged" instead of "services are provided" as in the definition of API? DISPOSITION: Accept. CHANGE TO DOCUMENT: On lines 138-139, change information is exchanged to services are provided. ------------------------------------------------------------------------------------------------------------------ Netherland-107 Section 2 ACTION: line 182 : replace 'applications' by 'application' DISPOSITION: Accept. CHANGE TO DOCUMENT: On line 182, change applications to application. ------------------------------------------------------------------------------------------------------------------ Netherland-108 Section 2 ACTION: line 212 : replace 'software and data' by 'an application' DISPOSITION: Accept CHANGE TO DOCUMENT: On line 212, change, software and data to application software ------------------------------------------------------------------------------------------------------------------ Netherland-109 Section 2 ACTION: line 213 : replace 'information system' by 'application platform' DISPOSITION: Accept. CHANGE TO DOCUMENT: On line 213, change information system to application platform. ------------------------------------------------------------------------------------------------------------------ Netherland-110 Section 2 ACTION: line 232 : the term 'profile' is circular defined with the term 'base standard' (2.2.2.7) DISPOSITION: Accept. CHANGE TO DOCUMENT: None - this item is addressed by resolution of Netherland-105 ------------------------------------------------------------------------------------------------------------------ Netherland-111 Section 2 ACTION: line 238 : what is the meaning of an entity in this context? DISPOSITION: Accept. The usage of the term entity is in the dictionary sense. CHANGE TO DOCUMENT: None ------------------------------------------------------------------------------------------------------------------ Netherland-112 Section 2 ACTION: line 254 : the term 'service' is circular defined with the term 'application platform' (2.2.2.4) DISPOSITION: Accept CHANGE TO DOCUMENT: None - this item is addressed by resolution of Netherlands-104 ------------------------------------------------------------------------------------------------------------------ Netherland-113 Section 2 ACTION: line 254 : replace the word 'to' by 'by' DISPOSITION: Accept. CHANGE TO DOCUMENT: None - this item is addressed by resolution of Netherlands-104 ------------------------------------------------------------------------------------------------------------------ Netherland-114 Section 3 ACTION: the requirement Data portability from par 1.1 is missing as a general objective. DISPOSITION: accept Data is viewed as a part of application software, and data portability is viewed as integral to application portability. This needs to be clarified in the introduction. CHANGE TO DOCUMENT: Substitute for pg. vii lines 65 through 87: The POSIX OSE described in this guide should provide services to satisfy the following objectives, summarized from section 3.1: - Application Portability at the Source Code Level to allow for movement of source code and data to a variety of application platforms - System Interoperability to allow application software and application platform interoperability - User Portability to allow people to use a wide range of application platforms without retraining. - Accomodation of Standards to provide all users and vendors with equitable access to key interface specifications - Accomodation of New Information System Technology to allow for migration to new technology and a variety of marketplace solutions - Application Platform Scalability to allow portability and software reuse across application platforms types and a range of power - Distributed System Scalability to assure that related standards to not inappropriately limit the growth of distributed systems - Implementation Transparency to allow the widest latitude in implementing technology solutions to user needs - Functional Requirements of the User to allow clear statement of user needs and provide context for identifying related standards. ------------------------------------------------------------------------------------------------------------------ Netherland-115 Section 3 ACTION: line 211-212 (in the External Environment box of figure 3-2), 248-255, 393, 385-386: because the term 'entity' is used for identifying the system elements of the Reference Model, replace the term 'entity' by 'component' as a subdivision of an entity or use the term 'fundamental element ' conform ISO/IEC TR 10000-3 instead of the term 'entity' DISPOSITION: accept The term entity is used in the dictionary sense, with no hierarchy implied. The only distinction needed in this discussion is the distinction between a thing (or entity), and an interface (or boundary between things). Establishing a new term to be used for a sub-component invites the observation that all entities are subcomponents since a higher level entity can always be found. This approach is clarified with the addition of text below in paragraph 3.2. CHANGE TO DOCUMENT: insert the following paragraph on page 26 between line 197 and 198: The term entity is used in the dictionary sense, with no hierarchy implied. The only distinction needed in this discussion is the distinction between a thing (or entity), and an interface (or boundary between things). ------------------------------------------------------------------------------------------------------------------ Netherland-116 Section 4 ACTION: line 143, 2229, 2236, 2274, 2275, 2500, 2780, 3646 :replace 'OSE' by 'POSIX OSE' DISPOSITION: accept CHANGE TO DOCUMENT: section 4 line 143, 2229, 2236, 2274, 2275, 2500, 2780, 3646 : replace 'OSE' by 'POSIX OSE' ------------------------------------------------------------------------------------------------------------------ Netherland-117 Section 4 ACTION: line 147 : should be 'Figure 4-1 - POSIX Language Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 147: change figure title to read: 'Figure 4-1 - POSIX OSE Language Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-118 Section 4 ACTION: line 149 : replace'services' by 'facilities' DISPOSITION: accept (services cross interface, and access is required - facilities imply entities) CHANGE TO DOCUMENT: modify line 149 to read: ... requires access to only basic operating system services will ... ------------------------------------------------------------------------------------------------------------------ Netherland-119 Section 4 ACTION: line 159 : delete the term 'Programming' DISPOSITION: accept CHANGE TO DOCUMENT: line 159 : delete the term 'Programming' ------------------------------------------------------------------------------------------------------------------ Netherland-120 Section 4 ACTION: line 268-269, 385-386 : the term API Services should be placed between the API-ring and the Application Platform box. DISPOSITION: accept (assume the line references point to figures 4-1 and 4-2 respectively) CHANGE TO DOCUMENT: lines 147, 418: insert the term API Services into figures 4-1 and 4-2, placed between the API-ring and the Application Platform box, to the left of the vertical arrows. ------------------------------------------------------------------------------------------------------------------ Netherland-121 Section 4 ACTION: line 378-380: because REXX is a command language, why is it mentioned in the Language Services subsection? DISPOSITION: accept CHANGE TO DOCUMENT: delete lines 378-380 ------------------------------------------------------------------------------------------------------------------ Netherland-122 Section 4 ACTION: line 418 : should be 'Figure 4-2 - POSIX Core System Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 418: modify figure title to read: 'Figure 4-2 - POSIX OSE Core System Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-123 Section 4 ACTION: line 538 : another use of the term 'entity' than as used in the Reference Model DISPOSITION: accept CHANGE TO DOCUMENT: modify line 538 to read ... lighter-weight unit of concurrency. ------------------------------------------------------------------------------------------------------------------ Netherland-124 Section 4 ACTION: line 951-952 : add - Transparent Network Services to the Communication Services API list also, replace 'General Communication User Commands' by 'Network User Interface Services' DISPOSITION: accept CHANGE TO DOCUMENT: on line 951-952, add - Transparent Network Services to the Communication Services API list also, replace 'General Communication User Commands' by 'Network User Interface Services' ------------------------------------------------------------------------------------------------------------------ Netherland-125 Section 4 ACTION: line 952 : should be 'Figure 4-3 - POSIX Communication Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 952: modify figure title to read 'Figure 4-3 - POSIX OSE Communication Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-126 Section 4 ACTION: line 959-1009 : delete these lines, because these topics are already described in par. 4.3.4 DISPOSITION: accept section 4.3.3.1 and 4.3.3.2 should discuss reference model and entities. Text appears to be appropriate for moving to 4.3.4. CHANGE TO DOCUMENT: Delete lines 959-967 Delete lines 1014-1016 through "..those services" Move lines 968-976 to line 1014 Delete lines 977-1009 ------------------------------------------------------------------------------------------------------------------ Netherland-127 Section 4 ACTION: line 1012 : should be: 4.3.4.1 API Services This subclause describes the major categories of communication services available of the Communication Services API. These services are: - Directory Services - - - Distributed System Services DISPOSITION: accept (see also Netherland-128) CHANGE TO DOCUMENT: Insert the following text between lines 1012 and 1013: 4.3.4.1 API Services This subclause describes the major categories of communication services available of the Communication Services API. These services are: - Transparent Network Services - Directory Services - Application-to-Platform Services - Application-to-Application Service - Distributed System Services ------------------------------------------------------------------------------------------------------------------ Netherland-128 Section 4 ACTION: line 1031 : replace 'System' by 'Platform' DISPOSITION: accept (other changes added for consistancy) CHANGE TO DOCUMENT: lines 978, 966 and 1031 : replace 'System' by 'Platform' ------------------------------------------------------------------------------------------------------------------ Netherland-129 Section 4 ACTION: line 1032 : replace 'These' by 'The Application-to-Platform Services' DISPOSITION: accept CHANGE TO DOCUMENT: line 1032 : replace 'These' by 'The Application-to-Platform Services' ------------------------------------------------------------------------------------------------------------------ Netherland-130 Section 4 ACTION: line 1042 : replace 'Service' by 'Communication Services' DISPOSITION: accept CHANGE TO DOCUMENT: line 1042 : replace 'Service' by 'Communication Services' ------------------------------------------------------------------------------------------------------------------ Netherland-131 Section 4 ACTION: line 1043 : replace 'services' by 'communication services' DISPOSITION: accept CHANGE TO DOCUMENT: line 1043 : replace 'services' by 'communication services' ------------------------------------------------------------------------------------------------------------------ Netherland-132 Section 4 ACTION: line 1430-1431 : interfaces should be noted by arrows instead of lines; replace 'P1003.12' at the first arrow by 'P1003.8' DISPOSITION: accept RATIONALE: P1003.8 is not one of these interfaces. P1003.8 interacts with the file-system. P1003.12 (now P1003.1g) contains the "Detailed Network Interface".A picture of P1003.8 would be as follows: APPLICATION /|\ /|\ P1003.8 | | P1003.1 | | (open/close/read/write) -------------------------------- | | | | | \|/ \|/ | | File System | | /|\ | | | | | \|/ | | Network Transport | | /|\ | ----------------|---------------- External Environment It seems that adding this detail would make Figure 4-4 too complicated. In addition, I expect there would be some disagreement exactly how the file-system connects to the network services. It seems that in the interest of consensus, leaving 1003.8 off the figure is the safest approach. I think that the concept in the above diagram is already well explained in lines 1427-1437. CHANGE TO DOCUMENT: line 1431: on figure 4-4, change API lines to be noted by arrows instead of lines. ------------------------------------------------------------------------------------------------------------------ Netherland-133 Section 4 ACTION: line 1595 : should be 'Figure 4-6 - POSIX Database Services Reference Model' DISPOSITION: Accept CHANGE TO DOCUMENT: line 1595 : modify figure title to read: 'Figure 4-6 - POSIX OSE Database Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-134 Section 4 ACTION: line 1598 : replace 'application' by 'database application' DISPOSITION: accept CHANGE TO DOCUMENT: line 1598 : replace 'application' by 'database application' ------------------------------------------------------------------------------------------------------------------ Netherland-135 Section 4 ACTION: line 1598, 1705 : replace 'database API' by 'database services API' DISPOSITION: accept CHANGE TO DOCUMENT: line 1598, 1705 : replace 'database API' by 'database services API' ------------------------------------------------------------------------------------------------------------------ Netherland-136 Section 4 ACTION: line 1705 : replace 'database API' by 'database services API' DISPOSITION: accept CHANGE TO DOCUMENT: line 1705 : replace 'database API' by 'database services API' ------------------------------------------------------------------------------------------------------------------ Netherland-137 Section 4 ACTION: line 1910, 1915 : replace 'component' by 'services component' DISPOSITION: accept CHANGE TO DOCUMENT: line 1910, 1915 : replace 'component' by 'services and formats' ------------------------------------------------------------------------------------------------------------------ Netherland-138 Section 4 ACTION: line 1925-1926 : delete the sentence "The key entities ... and the External Environment." DISPOSITION: accept CHANGE TO DOCUMENT: line 1925-1926 : delete the sentence "The key entities ... and the External Environment." ------------------------------------------------------------------------------------------------------------------ Netherland-139 Section 4 ACTION: line 1928 : should be 'Figure 4-7 - POSIX Data Interchange Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 1928 : should be 'Figure 4-7 - POSIX OSE Data Interchange Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-140 Section 4 ACTION: line 2292 : should be 'Figure 4-9 - POSIX Transaction Processing Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 2292 : should be 'Figure 4-9 - POSIX OSE Transaction Processing Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-141 Section 4 ACTION: line 2294 : delete the term 'Transaction' DISPOSITION: accept CHANGE TO DOCUMENT: line 2294 : modify to read: 'Communications with Transaction Processing application programs' ------------------------------------------------------------------------------------------------------------------ Netherland-142 Section 4 ACTION: line 2403 : replace 'Terminal Communications' by 'Presentation Service'; does 'Application Platform Interoperation' need to be replaced by 'Platform-Independent Exception Handling' and 'Concurrent Execution'? DISPOSITION: accept CHANGE TO DOCUMENT: line 2403 : replace 'Terminal Communications' by 'Presentation Service'; lines 2406: replace 'Application Platform Interoperation' with 'Platform-Independent Exception Handling' and 'Concurrent Execution'? ------------------------------------------------------------------------------------------------------------------ Netherland-143 Section 4 ACTION: line 2480, 2484, 2488, 2489-2490, 2499, 2500, 2504, 2507, 2519, 2522, 2525, 2531, 2532-2533, 2536, 2558, 2631, 2642, 2644, 2736: replace 'command' by 'user command' DISPOSITION: accept (assume 2736 is actually 2726) CHANGE TO DOCUMENT: line 2480, 2484, 2488, 2489-2490, 2499, 2500, 2504, 2507, 2519, 2522, 2525, 2531, 2532-2533, 2536, 2558, 2631, 2642, 2644, 2726: replace 'command' by 'user command' ------------------------------------------------------------------------------------------------------------------ Netherland-144 Section 4 ACTION: line 2530 : replace 'user' by 'user command' DISPOSITION: accept CHANGE TO DOCUMENT: line 2530 : replace 'user' by 'user command' ------------------------------------------------------------------------------------------------------------------ Netherland-145 Section 4 ACTION: line 2503 : should be 'Figure 4-10 - POSIX User Command Interface Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 2503 : modify figure title to read: 'Figure 4-10 - POSIX User Command Interface Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-146 Section 4 ACTION: line 2535-2546 : incomplete description of Figure 4-10 concerning the User Command Interface Services API DISPOSITION: accept, though no change to text is proposed. The document attempts to capture, not every possible service, but those in common use. CHANGE TO DOCUMENT: none ------------------------------------------------------------------------------------------------------------------ Netherland-147 Section 4 ACTION: line 2676-2677 : what does this sentence mean? DISPOSITION: accept Text should identify the service provided by the ISO/IEC 9945-2 command language standard. CHANGE TO DOCUMENT: modify line 2676 and 2676 to read: - A command set which provides access to a specific set of services and utilities commonly used by people interacting with computer systems. These services and programs .... ------------------------------------------------------------------------------------------------------------------ Netherland-148 Section 4 ACTION: line 2751, 2760 : replace 'character-based' by 'character-based user' DISPOSITION: accept CHANGE TO DOCUMENT: line 2751, 2760 : replace 'character-based' by 'character-based user' ------------------------------------------------------------------------------------------------------------------ Netherland-149 Section 4 ACTION: line 2780, 2783-2784 : replace 'terminal' by 'user interface' DISPOSITION: accept CHANGE TO DOCUMENT: line 2780, 2783-2784 : replace 'terminal' by 'user interface' ------------------------------------------------------------------------------------------------------------------ Netherland-150 Section 4 ACTION: line 2784 : should be 'Figure 4-11 - POSIX Character-based User Interface Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 2784 : modify figure title to read: 'Figure 4-11 - POSIX OSE Character-based User Interface Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-151 Section 4 ACTION: line 2917 : replace "interface is a modern component" by "services are a modern facility" DISPOSITION: accept CHANGE TO DOCUMENT: line 2917 : replace "interface is a modern component" by "services are a modern feature" ------------------------------------------------------------------------------------------------------------------ Netherland-152 Section 4 ACTION: line 2982-2983 : the Application Software box should be --------------- --------- --------- ------------- | Window | | Window | | Desktop | | Client | | System Server | | Manager | | Manager | | Application | --------------- --------- --------- ------------- ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ | | | | | | | | | | | | v v v v v v v v v v v v DISPOSITION: accept Showing separate application software entities seems to cause readers to assume that application programs corresponding the partitioning above is the only design/implementation allowed. The bullet list in figure 4-12, labelled Examples: is intended to more clearly indicate that the services to be provided are the subject under discussion, rather than an allocation of function to a specific list of application programs. CHANGE TO DOCUMENT: modify text in figure 4-12 (line 2983) from Server Process to Window System Server ------------------------------------------------------------------------------------------------------------------ Netherland-153 Section 4 ACTION: line 2983 : should be 'Figure 4-12 - POSIX Windowing System Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 2983 : modify title of figure to read: 'Figure 4-12 - POSIX OSE Windowing System Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-154 Section 4 ACTION: line 3014-3079: delete these lines, because these topics are already described in par. 4.9.4 DISPOSITION: accept It is intended that section 4.9.3 discuss the entities of the reference model, and 4.9.4 discuss the services exchanged among the entities. Text retained in 4.9.3 is within scope. CHANGE TO DOCUMENT: delete lines 3014 through 3017; delete lines 3062 through 3079 ------------------------------------------------------------------------------------------------------------------ Netherland-155 Section 4 ACTION: line 3090 : replace 'Application' by 'Windowing System' DISPOSITION: accept CHANGE TO DOCUMENT: line 3090 : replace 'Application' by 'Windowing system API' ------------------------------------------------------------------------------------------------------------------ Netherland-156 Section 4 ACTION: line 3306-3318 : the mentioned area-names does not match with the items in the Window Services EEI of figure 4-12 DISPOSITION: accept CHANGE TO DOCUMENT: modify line 3308 to read: Window System Look and Feel, and Drivability modify line 3313 to read: Windowing Information Interfaces modify line 3316 to read: Network Interface Protocols modify Windowing Services EEI list in figure 4-12 pg 128 to read -Window System Look and Feel, and Drivability -Windowing Information Interfaces -Network Interface Protocols ------------------------------------------------------------------------------------------------------------------ Netherland-157 Section 4 ACTION: line 3319-3328 : delete these paragraphs, because these items are not mentioned in figure 4-12 DISPOSITION: accept Paragraph cited was to address services exchanged among windowing system related application software entities. It is not necessary to represent these services on diagram 4-12, but the text was re-written. CHANGE TO DRAFT: For section 4.9.4.3, change title of section from "Interapplication Entity Services" to "Interapplication Entity Communcation Services" line 3320 replace first sentence with "These services provide generalized communication support for conventions and specifications for interaction between graphical window system components." Insert the following after "about graphical window system objects" - " These services provide a generalized communication protocol that is neccessary for exchange of information between windowing systems." ------------------------------------------------------------------------------------------------------------------ Netherland-158 Section 4 ACTION: line 3652 : should be 'Figure 4-14 - POSIX Graphics Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 3652 : modify title of figure to read 'Figure 4-14 - POSIX OSE Graphics Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-159 Section 4 ACTION: line 3678 : delete the term 'Computer' DISPOSITION: accept CHANGE TO DOCUMENT: line 3678 : delete the term 'Computer' ------------------------------------------------------------------------------------------------------------------ Netherland-160 Section 4 ACTION: line 3822 : should be 'Figure 4-15 - POSIX Graphics Services Reference Model Standards' DISPOSITION: accept CHANGE TO DOCUMENT: line 3822 : should be 'Figure 4-15 - POSIX OSE Graphics Services Reference Model Standards' ------------------------------------------------------------------------------------------------------------------ Netherland-161 Section 4 ACTION: line 3966 : delete the term 'virtual' DISPOSITION: accept CHANGE TO DOCUMENT: line 3966 : delete the term 'virtual' ------------------------------------------------------------------------------------------------------------------ Netherland-162 Section 4 ACTION: line 3967 : delete the first sentence DISPOSITION: accept CHANGE TO DOCUMENT: line 3967 : delete the first sentence ------------------------------------------------------------------------------------------------------------------ Netherland-163 Section 4 ACTION: line 3977 : delete the term 'Virtual Device' DISPOSITION: accept CHANGE TO DOCUMENT: line 3977 : delete the term 'Virtual Device' ------------------------------------------------------------------------------------------------------------------ Netherland-164 Section 4 ACTION: line 4087 : replace 'development' by 'development support' DISPOSITION: accept CHANGE TO DOCUMENT: line 4087 : replace 'development' by 'development support' ------------------------------------------------------------------------------------------------------------------ Netherland-165 Section 4 ACTION: line 4090 : should be 'Figure 4-16 - POSIX Application Software Development Support Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 4090 : change title of figure to read: 'Figure 4-16 - POSIX OSE Application Software Development Support Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-166 Section 5 ACTION: line 1-2, 707, 927 : replace 'OSE' by 'POSIX OSE' DISPOSITION: accept CHANGE TO DOCUMENT: line 1-2, 707, 927 : replace 'OSE' by 'POSIX OSE' ------------------------------------------------------------------------------------------------------------------ Netherland-167 Section 5 ACTION: line 935 : should be 'Figure 5-1 - POSIX Systems Management Services Reference Model' DISPOSITION: accept CHANGE TO DOCUMENT: line 935 : modify figure title to read: 'Figure 5-1 - POSIX OSE Systems Management Services Reference Model' ------------------------------------------------------------------------------------------------------------------ Netherland-168 Section 6.3.3.5 ACTION: It is no longer clear that there will be one profile development method; certainly the reference to the EWOS document is outdated. Replace lines 270-274 by: 6.3.3.5 Outline of the Profile Development Process As a profile needs to reflect a number of aspects of the described functionality, the creation of a profile cannot be a mechanical process. A number of these aspects are described below. The EWOS Expert Group on Open Systems Environment (EWOS EG-OSE) is currently developing an EWOS Technical Guide, which should clarify the profile development process and support the related activities. DISPOSITION: accept Accept that there are many methods under development, from many sources. CHANGE TO DOCUMENT: Modify the sentence on pg. 210 lines 273-274 which begins The purpose of this... to read as The purpose of this clause is to discuss topics that such a method would include. ------------------------------------------------------------------------------------------------------------------------------ Japanese Comments concerning PDTR 14252 on "Guide to the POSIX Open System Environment", doc. ISO/IEC JTC 1/SC 22 N 1596, alias IEEE P1003.0 Draft 16.1 Japan-2 Problem: The definition of AEP is not consistent with PDTR 10000-3. Action: Harmonize the POSIX.0 an PDTR 10000-3, and use consistent definitions. Dispostion: accept Note: Definition of AEP was deleted from TR-100000-3, but interface labels are modified. Change to D16: Modify as follows: pg. 30 line 289 - Insert paragraph: Three interfaces identified below, are EEI type interfaces. pg. 30 line 290 - Modify to read: The Human/Computer Interface is the boundary... pg. 30 line 290 - Modify to read: The Information Services Interface is the boundary across ... pg. 30 line 290 - Modify to read: The Communications Services Interface provides access ... Insert the following definitions into section 2.2: Application Program Interface (API): The interface between application software and application platform, across which services are provided. Communication Services Interface (CSI): The external environment interface across which access to services for interaction between internal application software entities and application platform external entities is provided. Human/Computer Interface (HCI): The external environment interface across which physical interaction between a human being and the application platform takes place. Information Services Interface (ISI): The external environment interface across which external, persistant storage service is provided. ------------------------------------------------------------------------------------------------------------------ Japan-3 Problem: The term of Component Profile has different meaning between the POSIX.0 and PDTR 10000-3. Action: Harmonize the POSIX.0 an PDTR 10000-3, and use consistent definitions. Dispostion: accept Note: Definition of Component Profile was deleted from TR10000-3. Change to D16: None at this time ------------------------------------------------------------------------------------------------------------------ Japan-6 Problem: The definition of Profile is not consistent with PDTR 10000-1.3. Action: Harmonize the POSIX.0 an PDTR 10000-1.3, and use consistent definitions. Dispostion: accept Change to D16: change definition to read: profile: a set of one or more base standards, and, where applicable, the identification of chosen classes, conforming subsets, options, and parameters of those base standards, necessary for accomplishing a particular function. ------------------------------------------------------------------------------------------------------------------ Japan-14 Problem: The types of the (POSIX) Profile and taxonomy of the profiles are not consistent with PDTR 10000-3. Action: Harmonize with PDTR 10000-1.3. Dispostion: accept Note: The June 94 TR10000-3 document provides a format for labeling profiles. The label identifies which of the four OSE interfaces are addressed in the profile. P1003.0 draft 17 does not address labels for profiles, and therefore does not conflict with TR10000-3. P1003.0 draft 17 discusses general types of OSE profiles (see section 6.4) and records some early experiences in defining OSE profiles, but deletes all text which defines a specific taxonomy. Change to D16: ------------------------------------------------------------------------------------------------------------------ Japan-24 Problem: The term public specification used in POSIX.0 and PAS discussed in the SGFS are confusing. Action: Clarify those terms and use consistent terms where appropriate. Dispostion: accept Note: The term Public Specifications is discussed in the P1003.0 introduction to section 4, where the table of contents for succeeding sections is outlined (pg. 41 4.n.5.2.2 Public Specifications). The terms public specifications and publicly available specifications (PAS) have been removed from TR10000-3, eliminating conflict between the documents. Change to D16: < see changes in Draft 17 pg. 41 4.n.5.2.2 Public Specifications> Proposed Disposition of Ballot 2 7/14/94