From owner-incits-v1@incits-v1.org Wed May 30 03:35:46 2007 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Date: Wed, 30 May 2007 06:34:08 -0400 From: Patrick Durusau Subject: INCITS-V1: Clean, normative, non-duplicative version? Sender: owner-incits-v1@incits-v1.org To: incits-v1@incits-v1.org Reply-to: incits-v1@incits-v1.org X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 X-ASG-Debug-ID: 1180521290-404e004a0000-E618Iy X-Barracuda-URL: http://10.10.100.8:8000/cgi-bin/mark.cgi X-Barracuda-Connect: unknown[66.110.197.207] X-Barracuda-Start-Time: 1180521290 X-ASG-Whitelist: Client X-ASG-Orig-Subj: Clean, normative, non-duplicative version? X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at insimail.com Greetings! Just in case my last message on this topic got lost in the holiday backlog. I am requesting the production of a plain text of DIS 29500 that: 1. Includes only normative text (excludes examples, rationales, etc.) 2. Includes section numbers (but no TOCs) 3. Excludes all reference tables such as parent, child, referenced by 4. Eliminates duplicate definitions of attributes by substituting a reference to the section where an attribute is defined 5. Excludes all image I understand the text is generated from a database or similar application so it should simply be a matter of setting up another view of the documents. This would be very useful as I could use the resulting text to build concordances of only the normative portions of DIS 29500. Which would help: 1. Insure consistent use of control vocabulary terms like shall, should, must, etc. 2. Insure uniform use of elements and attributes 3. Improve the readability of the proposal from those of us already familiar with markup 4. Uncover places where elements or attributes are treated inconsistently I routinely use concordances with 700+ page standard drafts and have found them to be very useful. Can we get an estimate on when we can see such a version of DIS 29500? Thanks! Hope everyone is having a great day! Patrick PS: I would suggest 80 column line breaks. Would make the ASCII view of the text more readable. -- Patrick Durusau Patrick@Durusau.net Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Member, Text Encoding Initiative Board of Directors, 2003-2005 Topic Maps: Human, not artificial, intelligence at work!