Thursday, 31 May 2007
Wednesday, 30 May 2007
- Re: Low hanging fruit?
- Re: Low hanging fruit?
- Re: Low hanging fruit?
- Re: Low hanging fruit?
- Re: Low hanging fruit?
- Re: Low hanging fruit?
- XProc meeting CANCELLED 31 May 2007
- Re: Low hanging fruit?
- Low hanging fruit?
- Re: Option syntax
- Re: Option syntax
- Re: Composability
Tuesday, 29 May 2007
Monday, 28 May 2007
- Composability
- Re: Option syntax
- Re: Making progress
- Re: Option syntax
- Re: Option syntax
- Re: Making progress
- Re: Option syntax
- Re: Option syntax
- Re: Option syntax
Sunday, 27 May 2007
Saturday, 26 May 2007
- Re: can we have last() having a consistent value ?
- Re: can we have last() having a consistent value ?
- Re: p:equals proposal
- Re: !result in components
- Re: can we have last() having a consistent value ?
- Re: can we have last() having a consistent value ?
- p:equals proposal
- !result in components
Friday, 25 May 2007
- Re: Another ('nother) parameters proposal
- Re: Alternate "parameters" draft
- Re: Allow unknown steps?
- Re: Making progress
- Re: Allow unknown steps?
- Re: Allow unknown steps?
- Allow unknown steps?
- Replace p:episode with p:system-property
- Re: Making progress
- Another ('nother) parameters proposal
Thursday, 24 May 2007
- Re: Radical Parameters Proposal
- Re: Radical Parameters Proposal
- Radical Parameters Proposal
- Re: Making progress
- RE: Making progress
- Making progress
- Re: can we have last() having a consistent value ?
- Re: can we have last() having a consistent value ?
- Re: p:head and p:tail
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: can we have last() having a consistent value ?
- Re: can we have last() having a consistent value ?
- p:head and p:tail
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: can we have last() having a consistent value ?
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- XProc Meeting Minutes 24 May 2007
- Re: 'Protection' from parameter 'polution'
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: 'Protection' from parameter 'polution'
- can we have last() having a consistent value ?
- 'Protection' from parameter 'polution'
- Re: Alternate "parameters" draft
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Alternate "parameters" draft
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Alternate "parameters" draft
- Re: position vs index
- Re: position vs index
- Re: Alternate "parameters" draft
- Re: Error codes
- Error codes
- Re: position vs index
- Re: Alternate "parameters" draft
- Re: Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Alternate "parameters" draft
- Re: New draft with the decisions of 3 May 2007
- Order of input/output/.../iteration-source/viewport-source/xpath-context
- Re: Types for Option Values
- Re: Extension functions
- Re: Parameters redux
- Re: Types for Option Values
- Re: Extension functions
- Re: Test Suite
- Re: Alternate "parameters" draft
- Re: Parsing HTML
- Re: Types for Option Values
- Propose to add 'group-by' option to p:wrap and p:wrap-sequence
- Re: Alternate "parameters" draft
- Test Suite
Wednesday, 23 May 2007
- Re: Alternate "parameters" draft
- Re: Alternate "parameters" draft
- Re: Alternate "parameters" draft
- Re: Extension functions
- Re: Extension functions
- Re: Extension functions
- Extension functions
- Re: Parsing HTML
- Re: Parsing HTML
- Re: Parsing HTML
- Re: position vs index
- Re: XProc Agenda 24 May 2007
- position vs index
- Re: XProc Agenda 24 May 2007
- Re: Default Option Values
- Re: Spec Changes Implemented
- Re: Parsing HTML
- Re: Spec Changes Implemented
- Re: Serialization and Escape Markup
- Re: Default Option Values
- XProc Agenda 24 May 2007
- Re: Spec Changes Implemented
- Re: Is this valid ?
- Re: Parsing HTML
- Re: Base uri of the documents on the 'current' port
- Re: Is this valid ?
- Re: Cardinality of inputs & outputs
- Re: Types for Option Values
- Re: Cardinality of inputs & outputs
- Is this valid ? (was: Cardinality of inputs & outputs)
- Re: Cardinality of inputs & outputs
- Re: Types for Option Values
- Re: New static error: options in the XProc namespace
- Re: Version attribute on pipeline
- Re: Cardinality of inputs & outputs
- Re: Parameters redux
- Re: Base uri of the documents on the 'current' port
- Re: Serialization and Escape Markup
- Re: Parsing HTML
- Re: New static error: options in the XProc namespace
- Re: p:count
- Re: Types for Option Values
- Re: Types for Option Values
- Re: Default Option Values
- Re: Types for Option Values
- Re: Types for Option Values
- Re: Default Option Values
- Re: unescaping markup
- Re: What can a step implementation ask the pipeline processor?
- Re: Types for Option Values
- Re: Default Option Values
- p:count
- Re: Spec Changes Implemented
Tuesday, 22 May 2007
- Re: Version attribute on pipeline
- Re: Base uri of the documents on the 'current' port
- Re: Base uri of the documents on the 'current' port
- Open Step Library Issues as of 5/22/2007
- Spec Changes Implemented
- Types for Option Values
- Default Option Values
- Version attribute on pipeline
- Re: Cardinality of inputs & outputs
- Re: Parameters redux
- Re: New static error: options in the XProc namespace
- Re: Cardinality of inputs & outputs
- Re: Cardinality of inputs & outputs
- Re: Cardinality of inputs & outputs
- Re: Cardinality of inputs & outputs
- Re: Cardinality of inputs & outputs
- Re: What can a step implementation ask the pipeline processor?
- Re: Cardinality of inputs & outputs
- Cardinality of inputs & outputs
- Re: Parameters redux
- Re: Parameters redux
- Alternate "parameters" draft
- Re: What can a step implementation ask the pipeline processor?
- Re: What can a step implementation ask the pipeline processor?
- Re: One or more...
- Re: What can a step implementation ask the pipeline processor?
- Re: Parameters redux
- Re: Parameters redux
- Re: What can a step implementation ask the pipeline processor?
- Re: One or more...
- Re: One or more...
- Re: Base uri of the documents on the 'current' port
Monday, 21 May 2007
- One or more...
- Re: unescaping markup
- Re: Serialization Analysis and Proposal
- Re: Parameters redux
- Re: Parameters redux
- Re: Parameters redux
- Re: What can a step implementation ask the pipeline processor?
- Re: What can a step implementation ask the pipeline processor?
- Re: Base uri of the documents on the 'current' port
Sunday, 20 May 2007
- Re: Base uri of the documents on the 'current' port
- Re: Base uri of the documents on the 'current' port
- Re: Base uri of the documents on the 'current' port
- Re: Base uri of the documents on the 'current' port
- Re: Base uri of the documents on the 'current' port
- select in for-each and iteration-source
- Re: State variable test
Saturday, 19 May 2007
- Re: Parameters redux
- Base uri of the documents on the 'current' port
- Re: p:load and p:document
- Re: State variable test
Friday, 18 May 2007
Thursday, 17 May 2007
- XProc Minutes 17 May 2007
- Re: Minutes for XML Proc WG telcon of 2007 May 17
- Minutes for XML Proc WG telcon of 2007 May 17
- Re: Parameters redux
- Re: What can a step implementation ask the pipeline processor?
- Re: Wrapping a sequence
- Re: p:load and p:document
- Re: p:http-request
- Re: Wrapping a sequence
Wednesday, 16 May 2007
- Re: Access to base URIs
- Access to base URIs
- Re: unescaping markup
- Re: Serialization Analysis and Proposal
- Re: Parsing HTML
- Re: Serialization Analysis and Proposal
- Re: Serialization Analysis and Proposal
- Re: unescaping markup
- Re: Serialization Analysis and Proposal
- Re: Serialization Analysis and Proposal
- Re: unescaping markup
- Re: Parsing HTML
- Re: Parameters redux
- Re: Serialization and Escape Markup
- Re: Serialization and Escape Markup
- Re: Serialization Analysis and Proposal
- Serialization and Escape Markup
- Parsing HTML
- Re: What can a step implementation ask the pipeline processor?
- Re: Serialization Analysis and Proposal
- Re: unescaping markup
- Re: Open Step Library Issues
- Re: unescaping markup
- Re: Serialization Analysis and Proposal
- XProc Agenda 17 May 2007
- Re: Serialization Analysis and Proposal
- Re: p:http-request
- Re: Renaming p:xslt ?
- p:http-request
- Re: Parameters redux
- What can a step implementation ask the pipeline processor?
- Re: State variable test
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
Tuesday, 15 May 2007
- Re: Serialization Analysis and Proposal
- Re: State variable test
- Re: Serialization Analysis and Proposal
- Re: State variable test
- Re: Serialization Analysis and Proposal
- Serialization Analysis and Proposal
- Re: Default pipeline filename
- Re: Renaming p:xslt ?
- Re: Default pipeline filename
- Re: Default pipeline filename
- Re: State variable test
- Re: References
- Re: Default pipeline filename
- Re: Default pipeline filename
- Default pipeline filename
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
- Re: Here's a tricky one
- Re: Renaming p:xslt ?
- Re: Here's a tricky one
- Re: Renaming p:xslt ?
- Re: Optional options
- Re: Parameters redux
- Re: Here's a tricky one
- Re: unescaping markup
- Re: Renaming p:xslt ?
- Open Step Library Issues
Monday, 14 May 2007
- Renaming p:xslt ?
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: unescaping markup
- Re: unescaping markup
- Re: unescaping markup
- Re: Options or parameters
- Re: unescaping markup
- Re: Here's a tricky one
- Re: Optional options
- Re: Here's a tricky one
- Parameters redux
- Re: Optional options
- Re: unescaping markup
- Re: Here's a tricky one
- Re: Syntactic sugar for options: a failed experiment?
- Re: Syntactic sugar for options: a failed experiment?
- Re: New static error: options in the XProc namespace
- Re: Here's a tricky one
Sunday, 13 May 2007
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
Saturday, 12 May 2007
Friday, 11 May 2007
- Re: Syntactic sugar for options: a failed experiment?
- Re: Syntactic sugar for options: a failed experiment?
- Re: Here's a tricky one
- Re: Here's a tricky one
- Re: Here's a tricky one
- Re: Wrapping a sequence
- Re: New static error: options in the XProc namespace
- Re: Here's a tricky one
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: Here's a tricky one
- Re: Here's a tricky one
- State variable test
- Re: Here's a tricky one
- Re: Here's a tricky one
- Re: New static error: options in the XProc namespace
- Re: New static error: options in the XProc namespace
- Re: Here's a tricky one
- Here's a tricky one
- New static error: options in the XProc namespace
- RE: Syntactic sugar for options: a failed experiment?
- Re: Syntactic sugar for options: a failed experiment?
- Re: Syntactic sugar for options: a failed experiment?
- Re: Wrapping a sequence
- Syntactic sugar for options: a failed experiment?
- Wrapping a sequence
Thursday, 10 May 2007
- New draft with 10 May decisions
- Re: XProc Minutes 10 May 2007
- XProc Minutes 10 May 2007
- Re: Spec Updated - http-request & vocabulary
- Re: Spec Updated - http-request & vocabulary
- Spec Updated - http-request & vocabulary
Wednesday, 9 May 2007
- Re: Make p:http-request required?
- Re: Make p:http-request required?
- Re: p:load and p:document
- Re: XProc Agenda 10 May 2007
- Re: XProc Agenda 10 May 2007
- Re: References
- Re: p:load and p:document
- XProc Agenda 10 May 2007
Tuesday, 8 May 2007
- Re: Multiple c:body elements in c:entity
- Re: Make p:http-request required?
- Re: Make p:http-request required?
- Re: Make p:http-request required?
- Re: Fixed Windows use case
- Re: Make p:http-request required?
- Re: unescaping markup
- Re: Make p:http-request required?
- Empty compound steps
- Updated color coding
- Re: Make p:http-request required?
- Re: Make p:http-request required?
- Re: Fixed Windows use case
- Re: Fixed Windows use case
- Re: Make p:http-request required?
Monday, 7 May 2007
- Re: Make p:http-request required?
- Re: Make p:http-request required?
- Fixed Windows use case
- Re: Make p:http-request required?
- Re: Optional options
- Re: Optional options
- Optional options
- Re: Make p:http-request required?
- unescaping markup
- Re: Make p:http-request required?
- Re: The 'secondary' output on the XSLT 1.0 step
Sunday, 6 May 2007
- Re: The 'secondary' output on the XSLT 1.0 step
- http-request
- Multiple c:body elements in c:entity
- The 'secondary' output on the XSLT 1.0 step
Saturday, 5 May 2007
- Re: Label and ID stuff
- Re: What do an empty document mean ?
- Pipelines that change attributes
- Re: Label and ID stuff
- Re: New draft with the decisions of 3 May 2007
- Re: New draft with the decisions of 3 May 2007
- Re: Label and ID stuff
- Re: p:load and p:document
- Re: What do an empty document mean ?
- References
- Re: What do an empty document mean ?
- Label and ID stuff
- p:load and p:document
- Re: Case where well formed ness could fly away
- Re: New draft with the decisions of 3 May 2007
- What do an empty document mean ?
Friday, 4 May 2007
- Re: Options or parameters
- Re: Options or parameters
- Re: Dealing with sequences on p:journal
- Re: non-matched output port
- Dealing with sequences on p:journal
Thursday, 3 May 2007
- Re: Options or parameters
- Re: Options or parameters
- Re: non-matched output port
- Overview pages in the test suite
- New draft with the decisions of 3 May 2007
- Re: Pipeline state variables to expose
- XProc Minutes 3 May 2007
- XProc Agenda 3 May 2007
- Pipeline state variables to expose
- Re: Example in 4.2 For-each
- Re: Example in 4.2 For-each
- Re: Options or parameters
- Re: Example in 4.2 For-each
- Re: Binding outputs
- Re: Example in 4.2 For-each
- Re: Options or parameters
- Re: Options or parameters
- Providing for journalling of intermediate document (streams)
- Example in 4.2 For-each
Wednesday, 2 May 2007
- Re: Options or parameters
- Re: XProc Agenda 3 May 2007
- Re: Options or parameters
- Re: Options or parameters
- XProc Agenda 3 May 2007
- Re: Options or parameters
- Re: Options or parameters
- Re: $p:position available everywhere
- Re: non-matched output port
- Re: Options or parameters
- Re: Options or parameters
- Re: $p:position available everywhere
- Re: non-matched output port
- Re: Options or parameters
Tuesday, 1 May 2007
- Re: Behaviour of non availability of Optional Step
- Re: Optional FO Formatter --> add SVG and MathML serializer
- Re: Behaviour of non availability of Optional Step
- Re: $p:position available everywhere
- Re: base uri
- Re: Behaviour of non availability of Optional Step
- Re: Optional FO Formatter --> add SVG and MathML serializer
- Re: $p:position available everywhere
- base uri
- Re: Optional FO Formatter --> add SVG and MathML serializer
- Behaviour of non availability of Optional Step
- Re: Optional FO Formatter --> add SVG and MathML serializer
- Optional FO Formatter --> add SVG and MathML serializer
- Re: Case where well formed ness could fly away
- $p:position available everywhere
- Re: Case where well formed ness could fly away
- Re: Case where well formed ness could fly away
- Re: Case where well formed ness could fly away
- Re: Escaped markup
- Re: non-matched output port
- Re: Escaped markup
- Options or parameters
- Case where well formed ness could fly away
- Re: non-matched output port
- Re: non-matched output port
- Re: Escaped markup
- Re: Escaped markup
- Re: Comparing p:delete and p:viewport
- Re: Comparing p:delete and p:viewport
- Re: non-matched output port
- Re: Escaped markup
- Re: Comparing p:delete and p:viewport
- Re: non-matched output port
- Re: Escaped markup
- Re: Comparing p:delete and p:viewport
- Re: Comparing p:delete and p:viewport
- Escaped markup
- Re: Error Inconsistencies
- Comparing p:delete and p:viewport
- Error Inconsistencies
- Re: non-matched output port
- Re: Other steps
- Re: non-matched output port
- Re: Other steps
- Re: Make p:http-request required?