- From: Innovimax SARL <innovimax@gmail.com>
- Date: Tue, 22 May 2007 21:24:56 +0200
- To: "Jeni Tennison" <jeni@jenitennison.com>
- Cc: public-xml-processing-model-wg@w3.org
Ok let's be extreme ! I would go for "exactly one" for "no" and "zero or more" for "yes" If it turns otherwise, then I think sequence=yes/no is useless Regards, Mohamed On 5/22/07, Jeni Tennison <jeni@jenitennison.com> wrote: > > We currently say: > > On compound steps and p:declare-step, an input declaration can > indicate if a sequence of documents is allowed to appear on the port. > If sequence is specified with the value "yes", then a sequence is > allowed. If sequence is not specified on p:input, or has the value > "no", then it is a dynamic error (err:XD0006) for a sequence of more > than one document to appear on the declared port. > > Does that mean that given: > > <p:input port="preprocess" sequence="no" /> > > I can bind the preprocess input port to zero documents? > > I wonder whether we should have the capability to constrain ports to say > they expect/produce zero-or-one, exactly-one, zero-or-more and one-or-more. > > If we don't, I think we need a note or something just to make explicit > that input ports with sequence="no" can accept zero documents. > > Cheers, > > Jeni > -- > Jeni Tennison > http://www.jenitennison.com > > -- 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, 22 May 2007 19:25:06 UTC