Working through my f2f action items

New Editors' draft will be with you soon.  This message is to record
my progress wrt the actions laid on me at the f2f [1] [2].

31 October:

  Action01 [2] (section 5) done

  Action03 [3] (Henri Sivonen vs. issue 9) awaiting publication of the
               Editors' draft, ref. name changes, changes in section 5

  Actions04--06 [4][5][6] (Issue 19) done, using Norm's prose as modified by 
                              Norm and Paul, following my own
                              suggestion for structure

  Action-07 [7] (New issue about validation) done

  Action-08 [8] ("read and process") done as best I can

  Action-09 [9] ("provided by profiles")

  Action-10 [10] (not steps) done

  Action-11 [11] (conformance)

  Action-12 [12] ("rigid") done

  Action-16 [13] ("data model" in abstract) done

  Various actions and discussions around conformance and the use of
  "data model":

    I'm exploring a route towards addressing all this, starting with
    the abstract, and the intro to section 2 and the description of
    the profiles themselves.  Here's how the first part of section 2
    now reads:

     2 XML processor profiles

     The profile definitions which follow all assume that the starting
     point is a well-formed and namespace well-formed XML
     document. This specification does not consider documents that are
     not namespace well-formed. Documents which are not well-formed
     are not XML.

     Each profile is defined in terms of comformance requirements on
     processors with respect to various XML-family specifications, and
     in terms of requirements on the information they provide to
     applications. Information provision requirements are specified by
     reference to classes of information items and properties, as
     further defined in 3 Classes of Information.

     2.1 The basic XML processor profile

     To conform to the basic profile an XML processor *must*

       1) Process the document as required of conformant
          non-validating XML processors without reading any external
          markup declarations;

       2) Maintain the base URI of each element in conformance with
          [XML Base];

       3) Accurately provide to the application the information in the
          document corresponding to information items and properties
          in classes A, S, P and X.

Does that seem like the right direction to go?  I think it all fits
together pretty well. . .

ht

[1] http://www.w3.org/XML/XProc/2011/10/31-minutes.html
[2] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action01
[3] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action03
[4] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action04
[5] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action05
[6] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action06
[7] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action07
[8] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action08
[9] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action09
[10] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action10
[11] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action11
[12] http://www.w3.org/XML/XProc/2011/10/31-minutes.html#action12
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

Received on Friday, 25 November 2011 12:21:43 UTC