HTTP/2 200 date: Sat, 11 Oct 2025 01:10:28 GMT content-type: text/html; charset=iso-8859-1 content-encoding: gzip last-modified: Tue, 10 Jul 2001 19:11:18 GMT cache-control: max-age=21600 expires: Sat, 11 Oct 2025 07:10:28 GMT vary: Accept-Encoding x-backend: www-mirrors x-request-id: 98ca7a5a6da0999b strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: BYPASS set-cookie: __cf_bm=pwJusbnYfrWz1ootFfeOyWaElg86H6kiU_yrVSGSKhk-1760145028-1.0.1.1-.pAcVLlsUxdIuWUp0PIjasSQi7L9SVKuTXhAMPI91Kq3JLtU_PTHgaOJLuUnns2Ljkls49D_KBaYzT7YP8iczXFn00nE6WSnhykKXItc1WU; path=/; expires=Sat, 11-Oct-25 01:40:28 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 98ca7a5a6da0999b-BLR alt-svc: h3=":443"; ma=86400

XML
 

This schedule is subject to adjustment.

Time	Thursday 12 July	Friday 13 July
9:00	Introductory session: C. M. Sperberg-McQueen, welcome to workshop and introductory overview of problem area	Report back from breakouts
		Presentations: Philippe Le Hégaret (see position paper) Steve Zilles (see position paper and cover note)
	Round-table introductions and discussion what do you want from this workshop? what do you think the community needs to do about the XML processing model?
		Discussion of application-specific requirements (preparation for breakouts)
10:30	Break	Break
11:00	Presentations: Paul Grosso (see position paper) Jonathan Marsh (see position paper)	Breakout discussions on application-specific requirements (list of breakout groups to be generated during previous discussion)
11:45	Discussion: generic / universal requirements for XML processing (all applications) Do you want a specified order for XML processing? Is there an ideal order? If so, is it a total order or a partial order? What's your ideal order for XML processing (if you have one)? Do you know whether your ideal order conflicts with anyone else's? If the order of actions in XML processing is constrained, are the constraints univeral (applicable to all XML documents)? data-specific (different for different documents, but always the same for a particular document)? application-specific (different depending on what you are trying to do)?
12:00		Discussion: application-specific requirements for XML processing (all applications)
12:30	Lunch	Lunch
2:00	Presentations: Daniel Veillard (see position paper) Angel Diaz, (see IBM position paper) Mary Holstege (see position paper) Norm Walsh and Eve Maler, (see Sun position paper)	Discussion: next steps
3:30	Break
4:00	Break-out groups, discussion What use cases / usage scenarios should be supported? Describe 2-4. What outcomes or deliverables would constitute successful solution of the problems relating to the XML processing model? Is there any specific ordering (total or partial) of XML processing which applies to all documents? Or is it impossible to identify any ordering constraints which apply to all XML documents? Is there any specific ordering (total or partial) of XML processing which always applies to a particular document? Or is it impossible to identify any such ordering constraints which always apply to a given XML document? Is it necessary / desirable for users to specify an ordering for XML processing? Which users? how? Do they just need to specify sequence of processing, or do they need to be able to describe more details than sequence (and if so which)?	Workshop adjourned.

---

$Id: xmlpm-program.html,v 1.6 2001/07/10 19:11:14 cmsmcq Exp $