docstring-checkins

[David G. <go...@us...>]

Update of /cvsroot/docstring/dps/spec
In directory usw-pr-cvs1:/tmp/cvs-serv2145/dps/spec

Modified Files:
	dps-notes.txt 
Log Message:
updated

Index: dps-notes.txt
===================================================================
RCS file: /cvsroot/docstring/dps/spec/dps-notes.txt,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** dps-notes.txt	1 Mar 2002 03:15:42 -0000	1.28
--- dps-notes.txt	8 Mar 2002 04:32:03 -0000	1.29
***************
*** 90,93 ****
--- 90,95 ----
      that case?
  
+     - Perhaps combine name mangling with sequential ids?
+ 
    - ID everything?  Or only named elements?
  
***************
*** 101,106 ****
  
    - Boolean attributes. ``<element boolean>`` is good, ``<element
!     boolean="boolean">`` is bad.  Use a special value in attributes
!     mapping, such as ``None``?
  
    - Escape double-dashes inside comments.
--- 103,108 ----
  
    - Boolean attributes. ``<element boolean>`` is good, ``<element
!     boolean="boolean">`` is bad.  Use a special value in attribute
!     mappings, such as ``None``?
  
    - Escape double-dashes inside comments.
***************
*** 177,181 ****
  be adjusted.
  
! (HTML only? See Deployment_ below.)
  
  
--- 179,183 ----
  be adjusted.
  
! (HTML only? See Distributors_ below.)
  
  
***************
*** 304,308 ****
      2     //     4  \               7          /     9  \
      +--------+   +------------+     +------------+   +--------------+
!     | PARSER |...| reader     |     | writer     |...| deployment   |
      +--------+   | transforms |     | transforms |   |              |
                   |            |     |            |   | - one file   |
--- 306,310 ----
      2     //     4  \               7          /     9  \
      +--------+   +------------+     +------------+   +--------------+
!     | PARSER |...| reader     |     | writer     |...| DISTRIBUTOR  |
      +--------+   | transforms |     | transforms |   |              |
                   |            |     |            |   | - one file   |
***************
*** 334,348 ****
  ------
  
! - Naming. Use "director"/"builder" instead of "reader"/"writer"? Then
!   "deployment" could be replaced by "writer".
! 
! - Transforms. How to specify which transforms (and in what order)
    apply to each combination of reader, parser/syntax, writer, and
!   deployment?  Even if we restrict ourselves to one parser, there will
!   eventually be a multitude of readers, writers, and deployment
    options.
  
!   Or are readers & writers independent? Then we have reader/parser and
!   writer/deployment combinations to consider.
  
  
--- 336,347 ----
  ------
  
! - Transforms.  How to specify which transforms (and in what order)
    apply to each combination of reader, parser/syntax, writer, and
!   distributor?  Even if we restrict ourselves to one parser, there
!   will eventually be a multitude of readers, writers, and distributor
    options.
  
!   Or are readers & writers independent?  Then we have reader/parser
!   and writer/distributor combinations to consider.
  
  
***************
*** 350,353 ****
--- 349,357 ----
  ----------
  
+ Production -> Publication -> Distribution
+ 
+ Producer -> Publisher -> Distributor
+ 
+ 
  Parsers
  ```````
***************
*** 407,412 ****
  ```````
  
- ("Writers" may be renamed to "Builders".)
- 
  Responsibilities:
  
--- 411,414 ----
***************
*** 423,437 ****
  
  
! Deployment
! ``````````
  
- ("Deployment" may be renamed to "Writers" or "Publishers", and current
- writer/deployment [renamed to builder/writer] components may change
- places. After renaming, the model would look like this::
  
             1,3,5                               6,8
!            +--------+                          +---------+ formerly
!            | READER | =======================> | BUILDER | writer
!            +--------+ (purely presentational)  +---------+
              //    \                              /    \
             //      \                            /      \
--- 425,439 ----
  
  
! Distributors
! ````````````
! 
! (Writer/distributor components may change places. After rearranging,
! the model would look like this::
  
  
             1,3,5                               6,8
!            +--------+                          +-------------+
!            | READER | =======================> | DISTRIBUTOR |
!            +--------+ (purely presentational)  +-------------+
              //    \                              /    \
             //      \                            /      \
***************
*** 440,472 ****
      | PARSER |...| reader     |     | writer     |...| WRITER |
      +--------+   | transforms |     | transforms |   +--------+
!                  | ...        |     | ...        |    formerly
!                                                       deployment
! 
! After renaming *and* rearrangement, the model would look like this::
! 
!            1,3,5                               6,8
!            +--------+                          +--------+ formerly
!            | READER | =======================> | WRITER | deployment
!            +--------+ (purely presentational)  +--------+
!             //    \                              /    \
!            //      \                            /      \
!     2     //     4  \               7          /     9  \
!     +--------+   +------------+     +------------+   +---------+
!     | PARSER |...| reader     |     | writer     |...| BUILDER |
!     +--------+   | transforms |     | transforms |   +---------+
!                  | ...        |     | ...        |    formerly writer
  
! We'll wait and see which arrangement works out best. Is it better for
! the writer/builder to control the deployment/writer, or vice versa? Or
! should they be equals?
  
  Looking at the list of writers, it seems that only HTML would require
! anything other than monolithic output. Perhaps merge the "deployment"
! into the "writer"?)
  
  Responsibilities:
  
  - Do raw output to the destination.
! - Transform references per incarnation.
  
  Examples:
--- 442,459 ----
      | PARSER |...| reader     |     | writer     |...| WRITER |
      +--------+   | transforms |     | transforms |   +--------+
!                  | ...        |     | ...        |
  
! We'll wait and see which arrangement works out best.  Is it better for
! the writer to control the distributor, or vice versa?  Or should they
! be equals?
  
  Looking at the list of writers, it seems that only HTML would require
! anything other than monolithic output.  Perhaps merge the HTML
! "distributor" into "writer" variants?)
  
  Responsibilities:
  
  - Do raw output to the destination.
! - Transform references per incarnation (type of distribution).
  
  Examples: