Re: Unserializable documents

/ Richard Tobin <richard@inf.ed.ac.uk> was heard to say:
| I think we agree that we should allow implementations that don't check
| serializability at every step (because it would be expensive) and
| implementations that do, and generate an error (because they really do
| serialize at every step).

I suggest we replace the first paragraph of 2.2 with:

  Although some steps can read and write non-XML resources, what flows
  between steps through input ports and output ports are exclusively
  XML documents or sequences of XML documents. The inputs and outputs
  can be implemented as sequences of characters, events, or object
  models, or any other representation the implementation chooses.

  Some steps can produce XML documents which have no direct
  serialization (because they produce nodes with conflicting or
  missing namespace declarations, for example). Implementors are
  encouraged to perform namespace fixup and other necessary
  adjustments before passing documents between steps, but they are not
  required to do so. Conversely, an implementation which /does/
  serialize betweens steps and therefore must perform such fixups or
  reject documents that cannot be serialized, is also conformant.

Does that work for anyone?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Through space the universe grasps me
http://nwalsh.com/            | and swallows me up like a speck;
                              | through thought I grasp it.-- Pascal