W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > January 2008

XProc Minutes 20 Dec 2007

From: Norman Walsh <ndw@nwalsh.com>
Date: Wed, 02 Jan 2008 10:23:36 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2odc42qvb.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2007/12/20-minutes


                                   - DRAFT -

                            XML Processing Model WG

20 Dec 2007


   See also: IRC log[3]


           Norm, Paul, Alessandro, Mohamed, Henry, Richard, Andrew





     * Topics
         1. Accept this agenda?
         2. Accept minutes from the previous meeting?
         3. Next meeting: telcon 3 January 2008?
         4. Last call comments
         5. 77. An unfulfilled requirement maybe?
         6. 78. normalization-form serialization option
         7. 82. Security considerations: p:exec et al.
         8. 84. Handling of system IDs
         9. 85. Please add Implementation and Test Suite info to the W3C
            XProc page
        10. 86. A really important question
        11. 87. p:function
        12. 88. xpath-version=2 and XSLTMatchPatterns
        13. Any other business
     * Summary of Action Items


  Accept this agenda?

   -> http://www.w3.org/XML/XProc/2007/12/20-agenda


  Accept minutes from the previous meeting?

   -> http://www.w3.org/XML/XProc/2007/12/13-minutes


  Next meeting: telcon 3 January 2008?

   Alessandro gives regrets.

  Last call comments

   -> http://www.w3.org/XML/XProc/2007/09/lastcall/comments

  77. An unfulfilled requirement maybe?

   Norm: This is Vasil asking about environment variables.

   Henry: Something needs to be said about environment variables. At the very
   least, that it's impl defined what environment variables are passed

   Richard: I don't think so. It seems to me it depends on the OS how it
   works and it's a QoI issue.
   ... Environment variables are an OS-specific concept.

   Henry: Can we say that the "environment" (lower case e) is implementation

   Richard: I assume that lots of things are implementation defined, like
   shell expansion in commands.

   Norm: I'd have thought not.

   Richard: For example, 'C' specifies that the command is passed to a
   command processor.
   ... which in Unix is a shell where expansion does take place.
   ... we probably should say something about that.

   Henry: I think the answer there is 'no', or impl defined.

   Richard: We've separated out the arguments from the command.
   ... If you want some sort of shell expansion, then you can make the
   command you run /bin/sh
   ... or whatever is appropriate.

   Norm: I'm tempted to go back to Henry's suggestion and say that the
   "e"nvironment is OS and implementation defined.

   Some discussion of parameters

   Accepted. Implementation defined.

   Norm: But we're not providing support for envars.


  78. normalization-form serialization option

   Norm: I think we resolved this last week, all the steps that have
   normalization parameters are supposed tohave them all. Any variance was a

  82. Security considerations: p:exec et al.

   Norm: I think this is resolved by the changes in 2.9 Security

   Mohamed: We have to also have a warning about user-defined steps.

   Norm: So we need to say that p:exec can be inside user-defined pipelines
   ... I suppose we could also say something about user-defined steps that
   are defined using Java code or something.

   Richard: Rui mentions explicitly the case that the p:exec is in an
   external library.

   <scribe> ACTION: Norm to expand 2.9 a bit more to cover these cases.
   [recorded in http://www.w3.org/2007/12/20-xproc-minutes.html#action01[7]]

  84. Handling of system IDs

   Norm: I think this is really about base URIs, which I'd thought we'd
   worked through, but now I'm not so sure.
   ... It might make sense to augment p:store so that it uses the xml:base
   value of the document element if it has one.

   Some discussion of how doctype declarations established by the
   serialization in XSLT might come into play.

   Henry: I was chasing this the other day and discovering that Saxon does
   better than most other processors about changing the base URI if you add
   an xml:base attribute.
   ... We did say that preserving base URI properties was something you
   should do, but we didn't directly address this point.

   Norm: Toman wants to change the base URI in a specific way.

   Richard: What's more, he probably wants it in unabsolutized form.

   Norm: Maybe we need to think about this some more...

   Richard: The clunky way to fix this is to start with a document that lists
   the documents rather than directly with the list of documents.

   Norm: Should we leave this one open a bit and see what progress we make.

   Let's take this one to email.

   Richard: The p:for-each step already does some things to the XPath
   environment, it could put something in which was the URI of the document
   in question.

   Some more discussion of the examples

   Richard observes that the select in p:store could access the extension

  85. Please add Implementation and Test Suite info to the W3C XProc page

   <scribe> ACTION: Norm to fix the XProc home page [recorded in

  86. A really important question

   Norm: This what extension to use...

   Henry: Whatever convention we establish, people will follow.
   ... We ought to give a little thought to the extension
   ... We could just expose them as .xml
   ... Since we're toying with a media type, web server administrators will
   be unhappy if we don't pick a suffix.

   <ht> allinurl: xpl filetype:xpl

   Henry: There are about 8000 pages that end in .xpl
   ... Orbeon uses .xpl

   Alessandro: works for me!

   Henry: So is this the way we're going

   Norm: I'm not really fond of the idea of making a statement directly about
   it in the spec, but I'm happy to use .xpl in examples and the test suite,

   Henry: We have an issue about the media type stuff and fragment
   identifiers. We'll get back to this, indirectly, when we cover that issue.

   Norm: I'm happy that we have an informal consensus to use .xpl, but I
   don't feel like we need to add it to the spec just yet.

   Alessandro: The XSLT spec says that most of the stylesheets use the
   extension .xsl

   Norm: Right, in the media type spec, I'm happy to do that too.

  87. p:function

   Not in V1

  88. xpath-version=2 and XSLTMatchPatterns

   Norm: So we get XSLT 2.0 match patterns if xpath-version=2?
   ... Anyone disagree and it's just the editor's job to work that out

   Richard: What's the difference?

   Norm: XSLT 2.0 match patterns can include variable references

   Henry: And can have functions in places other than predicates

   Some discussion of the features of XSLT 1.0 and XSLT 2.0

   <scribe> ACTION: Editor to make it so. [recorded in

  Any other business


   Happy holidays to all!

Summary of Action Items

   [NEW] ACTION: Editor to make it so. [recorded in
   [NEW] ACTION: Norm to expand 2.9 a bit more to cover these cases.
   [recorded in http://www.w3.org/2007/12/20-xproc-minutes.html#action01[11]]
   [NEW] ACTION: Norm to fix the XProc home page [recorded in
   [End of minutes]


   [1] http://www.w3.org/
   [2] http://www.w3.org/XML/XProc/2007/12/20-agenda
   [3] http://www.w3.org/2007/12/20-xproc-irc
   [7] http://www.w3.org/2007/12/20-xproc-minutes.html#action01
   [8] http://www.w3.org/2007/12/20-xproc-minutes.html#action02
   [9] http://www.w3.org/2007/12/20-xproc-minutes.html#action03
   [10] http://www.w3.org/2007/12/20-xproc-minutes.html#action03
   [11] http://www.w3.org/2007/12/20-xproc-minutes.html#action01
   [12] http://www.w3.org/2007/12/20-xproc-minutes.html#action02
   [13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
   [14] http://dev.w3.org/cvsweb/2002/scribe/

    Minutes formatted by David Booth's scribe.perl[13] version 1.128 (CVS
    $Date: 2008/01/02 15:16:46 $

Received on Wednesday, 2 January 2008 15:20:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:45 UTC