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

For-each

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 5 Jun 2007 12:27:42 +0200
Message-ID: <546c6c1c0706050327y4ecd5397q8c1a5bf75ef0ee31@mail.gmail.com>
To: "XProc WG" <public-xml-processing-model-wg@w3.org>

<p:viewport
  name? = NCName
  match = xpath expression
  p:ignore-prefixes? = prefix list>
   (p:viewport-source?,
    p:output,
    p:journal,
    (p:option |
    p:parameter)*,
    subpipeline)
</p:viewport>

it is read
@name is optional (OK)
@match is required (OK)
@p:ignore-prefixes is optional (OK)
p:viewport is optional as a first child (OK)
p:output is required (OK since we have only one output)
p:journal is required (WHY ??[1])
(p:option or p:parameter) zero or more (ok for p:option but what is
the aim of p:parameter here ? [2])
and a subpipeline

shouldn't it better be

<p:viewport
  name? = NCName
  match = xpath expression
  p:ignore-prefixes? = prefix list>
   (p:viewport-source?,
    p:output,
    p:journal?,
    p:option*,
    subpipeline)
</p:viewport>

Since we mandate a perticular order for p:viewport, I propose to do
the same for the other component

Mohamed

-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Tuesday, 5 June 2007 10:27:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:52 GMT