The requirements for public available documentation is overstated. If a company wasn’t to use the specification for a non-public, internal-use only application, it shouldn’t be necessary with public available documentation

More clearly state the purpose of the documentation, and refrain from dictation of the business relationship under which the specification is adopted

Page 3
line 33-34 Part 1
Section 2.6

Ed

Proposed Disposition of DIS 29500 Comment DK-0066 (Modified: 2007-12-07) Agreed; the following change will be made to Part 1, ยง2.6, page 3, line 33: For the guidelines to be meaningful, a software application should be accompanied by publicly available documentation that describes what subset of this Standard it supports. Similar Comments: DE-0122 , FR-0004 , GB-0026 , JP-0024 , KE-0015 , PT-0022 , US-0255

Tag and Go

No Comments

Sorry, the comment form is closed at this time.

  • Argentina (1)
  • Australia (30)
  • Austria (1)
  • Belgium (1)
  • Brazil (64)
  • Bulgaria (3)
  • Canada (79)
  • Chile (217)
  • China (1)
  • Colombia (237)
  • Czech Republic (75)
  • Denmark (168)
  • Ecma (76)
  • Ecuador (1)
  • Finland (15)
  • France (592)
  • Germany (162)
  • Ghana (12)
  • Greece (113)
  • India (82)
  • Iran (58)
  • Ireland (12)
  • Israel (33)
  • Italy (2)
  • Japan (82)
  • Jordan (1)
  • Kenya (81)
  • Malaysia (23)
  • Malta (5)
  • Mexico (7)
  • New Zealand (54)
  • Norway (12)
  • Peru (10)
  • Philippines (7)
  • Poland (4)
  • Portugal (118)
  • Singapore (2)
  • South Africa (17)
  • South Korea (25)
  • Spain (1)
  • Switzerland (19)
  • Thailand (1)
  • Tunisia (3)
  • Turkey (1)
  • UK (635)
  • Uruguay (18)
  • USA (288)
  • Venezuela (73)