XML-DEV Mailing List Archive by thread - February, 2002

• ANNOUNCE: Ruple (XML Spaces) Alpha Version 2, Andy Gray
• RE: HTTPEctomy considered bad (was RE: RE: MSthinks HTTP Needs Replacing???), Michael Brennan
• Check out the pipeline submission, Tim Bray
  • Re: Check out the pipeline submission, Simon St.Laurent
• RE: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Michael Brennan
• RE: Fwd: Linkage of GPLed GCC to Closed Source via XML or Perl, Michael Brennan
• xml/XSL and javascript form issue, rockie12
  • Re: xml/XSL and javascript form issue, Thomas B. Passin
• Call For Papers: ebXML track at XML Europe 2002, Karl F. Best
• updated xmlns media feature, Simon St.Laurent
• Use of CONOPS in Sharable Service Contracts (WAS RE: MS thinks HTTP Needs Replacing???), Bullard, Claude L (Len)
• Fwd: Linkage of GPLed GCC to Closed Source via XML or Perl, James Michael DuPont
• RE: Simple xpath software request, Joshua Allen
  • <Possible follow-ups>
  • RE: Simple xpath software request, Michael Brennan
  • RE: Simple xpath software request, Michael Brennan
• Either ... or ... in Schema, rajac
  • RE: Either ... or ... in Schema, Michael Fitzgerald
• Simple xpath software request, Kris Thompson
  • Re: Simple xpath software request, Daniel Veillard
    • Re: Simple xpath software request, Mike Thanos
      • Re: Simple xpath software request, Christian Nentwich
• RE: Image (bitmap) in XML document, Michael Brennan
  • XML Standards Library 1.0 : Updated 1 March 2002, MWS Tech Support
• Image (bitmap) in XML document, Handoko
• Re: Question about the sytax of namespace declarations, Wayne Steele
  • <Possible follow-ups>
  • RE: Question about the sytax of namespace declarations, Michael Brennan
• Question about the sytax of namespace declarations, Wayne Steele
  • Re: Question about the sytax of namespace declarations, Jason Diamond
    • Re: Question about the sytax of namespace declarations, Thomas B. Passin
      • RE: Question about the sytax of namespace declarations, Julian Reschke
      • Re: Question about the sytax of namespace declarations, Thomas B. Passin
  • Re: Question about the sytax of namespace declarations, Tim Bray
    • Re: Question about the sytax of namespace declarations, Daniel Veillard
    • RE: Question about the sytax of namespace declarations, Julian Reschke
      • Re: Question about the sytax of namespace declarations, Jason Diamond
• ANN: Xalt Object Realizer version 1.0, Ramesh Gupta
• looking for existing XSL code, Wo Chang
• RE: REST as RPC done right, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: REST as RPC done right, Joshua Allen
    • Re: REST as RPC done right, Paul Prescod
  • RE: REST as RPC done right, Joshua Allen
• REST as RPC done right, Simon St.Laurent
  • Re: REST as RPC done right, Mike Champion
  • Re: REST as RPC done right, Mark Baker
    • Re: REST as RPC done right, Gavin Thomas Nicol
  • Re: REST as RPC done right, Paul Prescod
    • Re: REST as RPC done right, Simon St.Laurent
      • Re: REST as RPC done right, Paul Prescod
      • Re: REST as RPC done right, Simon St.Laurent
      • Re: REST as RPC done right, Jim Ancona
      • RE: REST as RPC done right, Bill de hÓra
  • Re: REST as RPC done right, Gavin Thomas Nicol
• RE: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Michael Brennan
    • Re: HTTPEctomy considered bad (was RE: RE: MSthinks HTTP Needs Replacing???), Paul Prescod
• Re: XML to object relational, Ronald Bourret
• repeating element names in single XML vocabulary, Lyndon J B Nixon
• [Announce] Apache Xindice XML database 1.0rc2 Released, Kimbro Staken
• HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Sean McGrath
  • Re: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), John Cowan
  • Re: HTTPEctomy considered bad (was RE: RE: MS thinksHTTP Needs Replacing???), Paul Prescod
  • RE: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Bill de hÓra
    • Re: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Paul Prescod
      • RE: HTTPEctomy considered bad (was RE: RE: MS thinks HTTP Needs Replacing???), Bill de hÓra
• RE: Namespaces best practices, Manos Batsis
• NEXTWARE Spring 2002 brochure available for download, Ken North
• Data Dictionary, Bullard, Claude L (Len)
• Namespaces best practices, Friedland, Zachary (TLP 2001)
• RE: New Patent Policy Draft, Bullard, Claude L (Len)
  • RE: New Patent Policy Draft, Rex Brooks
• RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: MS thinks HTTP Needs Replacing???, David LeBlanc
  • <Possible follow-ups>
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
    • Re: MS thinks HTTP Needs Replacing???, Mark Baker
    • Re: RE: MS thinks HTTP Needs Replacing???, Mike Champion
      • request to unsubscribe, chodge5
    • RE: MS thinks HTTP Needs Replacing???, Leigh Dodds
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
  • RE: MS thinks HTTP Needs Replacing???, Joshua Allen
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
    • Re: RE: RE: MS thinks HTTP Needs Replacing???, Mike Champion
      • Re: MS thinks HTTP Needs Replacing???, Francis Norton
    • RE: MS thinks HTTP Needs Replacing???, Andrzej Jan Taramina
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: RE: RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
    • Re: RE: RE: MS thinks HTTP Needs Replacing???, Thomas B. Passin
  • RE: RE: RE: MS thinks HTTP Needs Replacing???, Joshua Allen
  • RE: MS thinks HTTP Needs Replacing???, AManns
    • Re: MS thinks HTTP Needs Replacing???, Alaric Snell
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: RE: RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
    • RE: RE: RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
      • Re: MS thinks HTTP Needs Replacing???, Francis Norton
  • RE: RE: RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: MS thinks HTTP Needs Replacing???, Dare Obasanjo
  • RE: MS thinks HTTP Needs Replacing???, Dare Obasanjo
  • RE: MS thinks HTTP Needs Replacing???, Michael Brennan
    • Re: MS thinks HTTP Needs Replacing???, Thomas B. Passin
  • RE: MS thinks HTTP Needs Replacing???, Bullard, Claude L (Len)
  • RE: MS thinks HTTP Needs Replacing???, Michael Brennan
    • Re: MS thinks HTTP Needs Replacing???, Thomas B. Passin
• MS thinks HTTP Needs Replacing???, Mike Champion
  • RE: MS thinks HTTP Needs Replacing???, David LeBlanc
    • RE: MS thinks HTTP Needs Replacing???, Andrzej Jan Taramina
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
  • RE: MS thinks HTTP Needs Replacing???, Leigh Dodds
    • RE: MS thinks HTTP Needs Replacing???, Simon St.Laurent
      • Re: MS thinks HTTP Needs Replacing???, Alaric Snell
      • Re: MS thinks HTTP Needs Replacing???, Paul Prescod
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
      • Re: MS thinks HTTP Needs Replacing???, Alaric Snell
      • Re: MS thinks HTTP Needs Replacing???, Gavin Thomas Nicol
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
      • RE: MS thinks HTTP Needs Replacing???, Simon St.Laurent
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
      • Re: MS thinks HTTP Needs Replacing???, Paul Prescod
      • Re: MS thinks HTTP Needs Replacing???, Simon St.Laurent
      • Re: MS thinks HTTP Needs Replacing???, Mark Baker
      • RE: MS thinks HTTP Needs Replacing???, Bill de hÓra
  • Re: MS thinks HTTP Needs Replacing???, Paul Prescod
    • Re: MS thinks HTTP Needs Replacing???, Thomas B. Passin
• <OT> MaGIC, Bullard, Claude L (Len)
• 3: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, "Braumüller, Hans"
• RE: Evaluating RPC versus REST, Bullard, Claude L (Len)
  • RE: Evaluating RPC versus REST, Mike Champion
  • <Possible follow-ups>
  • RE: Evaluating RPC versus REST, Bullard, Claude L (Len)
  • RE: Evaluating RPC versus REST, Bullard, Claude L (Len)
  • RE: Evaluating RPC versus REST, Michael Brennan
• Evaluating RPC versus REST, Leigh Dodds
  • Re: Evaluating RPC versus REST, Mark Baker
  • Re: Evaluating RPC versus REST, Paul Prescod
• RE: Standards: innovation, evolution, and stasis, Bullard, Claude L (Len)
• Standards: innovation, evolution, and stasis, Mike Champion
  • Re: Standards: innovation, evolution, and stasis, Simon St.Laurent
• New Patent Policy Draft, Bullard, Claude L (Len)
  • Re: New Patent Policy Draft, Simon St.Laurent
• unsubscibe, Martin Lang
• RE: 2: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, Manos Batsis
• 2: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, =?utf-8?B?IkJyYXVtw7xsbGVyLCBIYW5zIg==?=
  • RE: 2: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, Priscilla Walmsley
• RE: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, Manos Batsis
• XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, Braumuller, Hans
  • Re: XML Schema - > XML Instance - > XSLT Transformation with MSXML 4 ?, TAN Kuan Hui
• XInclude & Document Function., aruns
  • Re: XInclude & Document Function., Jeni Tennison
• XPath and performance, Mark Nottingham
  • DOM L3 and Type info, Jeff Rafter
    • Re: DOM L3 and Type info, Eric van der Vlist
  • Re: XPath and performance, bob mcwhirter
• Test, CHIUSANO, Joseph
• Reminder: deadline for participation in new OASIS TCs, Karl F. Best
• Doubts relating to XML, seshu
• <redefine> and schema constraints, Nada_Reinprecht
  • Re: <redefine> and schema constraints, Rick Jelliffe
• <?P[SV]I?>, Eric van der Vlist
• RE: XML & government in general, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: XML & government in general, Hodder, Ed
  • RE: XML & government in general, Bullard, Claude L (Len)
• ANNOUNCE: SAX2 book from O'Reilly, David Brownell
  • Re: ANNOUNCE: SAX2 book from O'Reilly, Andrzej Jan Taramina
• XML & government in general, Tim Bray
  • Re: XML & government in general, John Wilson
  • RE: XML & government in general, Michael Kay
    • Re: XML & government in general, K. Ari Krupnikov
  • RE: XML & government in general, Paul Spencer
• RE: Two sides of SOAP (was RE: SOAP-RPC and REST and security), Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Two sides of SOAP (was RE: SOAP-RPC and REST and security), Michael Brennan
• Re: Simplified XPointer, jborden
• RE: The InfoApocalypse, Bullard, Claude L (Len)
• RE: Data-oriented XML [was: Scatter/gather pattern], Bullard, Claude L (Len)
• Simplified XPointer, jborden
  • Re: Simplified XPointer, Jonathan Robie
  • Re: Simplified XPointer, Jonathan Borden
• How do I use my own JavaClass???, Cyrill Zadra
  • RE: How do I use my own JavaClass???, Michael Kay
• The InfoApocalypse, Tim Bray
• RE: SOAP and Firewalls, Joshua Allen
  • <Possible follow-ups>
  • RE: SOAP and Firewalls, Joshua Allen
    • Re: SOAP and Firewalls, Paul Prescod
  • RE: SOAP and Firewalls, Michael Brennan
    • Re: SOAP and Firewalls, Paul Prescod
  • RE: SOAP and Firewalls, Michael Brennan
• RE: On the use of HTTP as a Substrate, Michael Brennan
• SOAP and Firewalls, Paul Prescod
  • Re: SOAP and Firewalls, Alaric Snell
    • Re: SOAP and Firewalls, Amy Lewis
      • RE: SOAP and Firewalls, Bill de hÓra
      • Re: SOAP and Firewalls, Ronald Bourret
  • Re: SOAP and Firewalls, Joe English
    • Re: SOAP and Firewalls, Paul Prescod
• ICE Authoring Group Releases Draft Requirements for Industry Comment, Elledge, Marion
• RE: What is SOAP?, Bullard, Claude L (Len)
  • RE: What is SOAP?, Zach Kenyon
  • <Possible follow-ups>
  • RE: What is SOAP?, Bullard, Claude L (Len)
• RE: Why make namespaces so complicated?, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Why make namespaces so complicated?, Anderson, John
  • RE: Why make namespaces so complicated?, Bullard, Claude L (Len)
  • RE: Why make namespaces so complicated?, Bullard, Claude L (Len)
  • RE: Why make namespaces so complicated?, Michael Brennan
• Prescod on REST, useful clear summary, Edd Dumbill
• RE: Two sides of SOAP (was RE: SOAP-RPC and R EST and security), Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Two sides of SOAP (was RE: SOAP-RPC and R EST and security), Michael Brennan
  • RE: Two sides of SOAP (was RE: SOAP-RPC and R EST and security), Bullard, Claude L (Len)
    • Re: Two sides of SOAP (was RE: SOAP-RPC and REST and security), Paul Prescod
• On the use of HTTP as a Substrate, Simon St.Laurent
• Scatter/gather pattern [was: New XPipe Presentation Available], Roger L. Costello
  • Re: Scatter/gather pattern [was: New XPipe Presentation Available], Sean McGrath
    • Re: Data-oriented XML [was: Scatter/gather pattern], Ronald Bourret
  • Re: Scatter/gather pattern [was: New XPipe PresentationAvailable], Thomas B. Passin
    • Re: Scatter/gather pattern [was: New XPipe Presentation Available], Sean McGrath
• even more tunneling, Simon St.Laurent
  • Re: even more tunneling, Thomas B. Passin
  • 3rd party tool, K.R.Vaidyanathan
    • Re: 3rd party tool, Eric van der Vlist
    • Re: 3rd party tool, XML Everywhere
• What is SOAP?, Amy Lewis
  • Re: What is SOAP?, Zach Kenyon
  • Re: What is SOAP?, Paul Prescod
• Why make namespaces so complicated?, Anderson, John
  • Re: Why make namespaces so complicated?, Patrick Stickler
• RE: Worse XML tools?, Anderson, John
  • <Possible follow-ups>
  • RE: Worse XML tools?, Bullard, Claude L (Len)
  • RE: Worse XML tools?, Koorn, Wilco
    • RE: Worse XML tools?, Handoko
  • RE: Worse XML tools?, Bullard, Claude L (Len)
  • RE: Worse XML tools?, Bullard, Claude L (Len)
    • Re: Worse XML tools?, John Cowan
      • Re: Worse XML tools?, Eric van der Vlist
  • RE: Worse XML tools?, Bullard, Claude L (Len)
  • RE: Worse XML tools?, Dare Obasanjo
  • RE: Worse XML tools?, Bullard, Claude L (Len)
    • Re: Worse XML tools?, John Cowan
  • RE: Worse XML tools?, Anderson, John
• Worse XML tools?, Eric van der Vlist
• New XPipe Presentation available, Sean McGrath
  • New XPipe Presentation available, Allan Doyle
    • Re: New XPipe Presentation available, Simon St.Laurent
    • Re: New XPipe Presentation available, Paul Prescod
• Problem with XML Schema, rajac
  • Re: Problem with XML Schema, Rick Jelliffe
• RE: Two sides of SOAP (was RE: SOAP-RPC and REST and security), Michael Brennan
• Architecture Description Markup Language, Michael Brennan
• RDDL: minor update, jborden
  • Re: RDDL: minor update, Tim Bray
• RE: Inclusion in XML versus SGML, Anderson, John
• Use of © in XML/XSLT, Ryan Fransen
  • Re: Use of © in XML/XSLT, Alaric Snell
  • RE: Use of © in XML/XSLT, Michael Kay
• Inclusion in XML versus SGML, Sevigny Benoît
  • Re: Inclusion in XML versus SGML, John Cowan
    • Re: Inclusion in XML versus SGML, Eve L. Maler
  • RE: Inclusion in XML versus SGML, Michael Fitzgerald
• Re: Namespace dispatching, Patrick Stickler
• Regarding Java code to XML, Ramur
• Xerces Parser Installation, rajac
• Xerces2.0.0 Parser, rajac
  • Re: Xerces2.0.0 Parser, Thomas B. Passin
    • simple xslt question, Wo Chang
      • Re: simple xslt question, Wo Chang
      • RE: simple xslt question, Michael Kay
• RE: SOAP-RPC and REST and security, Joshua Allen
  • Re: SOAP-RPC and REST and security, Paul Prescod
  • Re: RE: SOAP-RPC and REST and security, Mike Champion
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • <Possible follow-ups>
  • RE: SOAP-RPC and REST and security, Joshua Allen
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
  • RE: RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Joshua Allen
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
    • RE: SOAP-RPC and REST and security, Zach Kenyon
    • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Amy Lewis
      • Re: SOAP-RPC and REST and security, Zach Kenyon
      • Re: SOAP-RPC and REST and security, Amy Lewis
      • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Amy Lewis
      • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Paul Prescod
    • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Thomas B. Passin
  • RE: SOAP-RPC and REST and security, Michael Brennan
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
      • Re: SOAP-RPC and REST and security, John Cowan
      • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Michael Brennan
  • RE: SOAP-RPC and REST and security, Michael Brennan
  • RE: SOAP-RPC and REST and security, Joshua Allen
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
    • RE: SOAP-RPC and REST and security, Zach Kenyon
    • Re: SOAP-RPC and REST and security, Francis Norton
      • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Joshua Allen
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
    • RE: SOAP-RPC and REST and security, Zach Kenyon
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
    • agendas, Simon St.Laurent
    • Re: RE: SOAP-RPC and REST and security, Mike Champion
      • Re: RE: SOAP-RPC and REST and security, Al Snell
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Bullard, Claude L (Len)
    • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
  • RE: SOAP-RPC and REST and security, Michael Brennan
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Paul Prescod
    • Two sides of SOAP (was RE: SOAP-RPC and REST and security), Mike Champion
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Joshua Allen
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Uther, James
    • Re: SOAP-RPC and REST and security, Francis Norton
      • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Francis Norton
      • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Michael Brennan
    • Re: SOAP-RPC and REST and security, Paul Prescod
  • RE: SOAP-RPC and REST and security, Michael Brennan
  • RE: SOAP-RPC and REST and security, Dare Obasanjo
• RE: [xsl] [Ann - Zvon] Templatotron, Evan Lenz
  • RE: [xsl] [Ann - Zvon] Templatotron, Miloslav Nic
• REST made more concrete still, Paul Prescod
• RE: REST made more concrete, Michael Brennan
  • <Possible follow-ups>
  • RE: REST made more concrete, Leigh Dodds
    • Re: REST made more concrete, Paul Prescod
    • Re: REST made more concrete, Joe English
  • RE: REST made more concrete, Michael Brennan
  • RE: REST made more concrete, Michael Brennan
• REST made more concrete, Mike Champion
• RE: URIs are simply names was:Re:"Abstract"URIs, Manos Batsis
  • Re: URIs are simply names was:Re:"Abstract"URIs, Steven R. Newcomb
  • Re: URIs are simply names was:Re:"Abstract"URIs, Patrick Stickler
  • <Possible follow-ups>
  • RE: URIs are simply names was:Re:"Abstract"URIs, Manos Batsis
    • Re: URIs are simply names was:Re:"Abstract"URIs, Patrick Stickler
• RE: Re: [namespaceDocument-8] 14 Theses, Dare Obasanjo
  • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
    • Re: Re: [namespaceDocument-8] 14 Theses, Tim Bray
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
      • Re: Re: [namespaceDocument-8] 14 Theses, Tim Bray
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
      • Re: Re: [namespaceDocument-8] 14 Theses, Ronald Bourret
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
      • Re: Re: [namespaceDocument-8] 14 Theses, Thomas B. Passin
      • Re: Re: [namespaceDocument-8] 14 Theses, Ian Graham
  • <Possible follow-ups>
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
  • RE: Re: [namespaceDocument-8] 14 Theses, Michael Brennan
    • Re: Re: [namespaceDocument-8] 14 Theses, Paul Prescod
      • Re: Re: [namespaceDocument-8] 14 Theses, Simon St.Laurent
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
    • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
    • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
    • Re: Re: [namespaceDocument-8] 14 Theses, John Cowan
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
    • Re: Re: [namespaceDocument-8] 14 Theses, John Cowan
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
    • Re: Re: [namespaceDocument-8] 14 Theses, John Cowan
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
    • Re: Re: [namespaceDocument-8] 14 Theses, Joe English
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
    • RE: Re: [namespaceDocument-8] 14 Theses, Elliotte Rusty Harold
      • RE: Re: [namespaceDocument-8] 14 Theses, Sean McGrath
  • RE: Re: [namespaceDocument-8] 14 Theses, jborden
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
  • RE: Re: [namespaceDocument-8] 14 Theses, Bullard, Claude L (Len)
• Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
  • Re: Re: [namespaceDocument-8] 14 Theses, Ronald Bourret
    • Re: Re: [namespaceDocument-8] 14 Theses, Tim Bray
      • Re: Re: [namespaceDocument-8] 14 Theses, Ronald Bourret
      • Re: Re: [namespaceDocument-8] 14 Theses, Rick Jelliffe
      • Re: Re: [namespaceDocument-8] 14 Theses, Eric van der Vlist
      • Re: Re: [namespaceDocument-8] 14 Theses, Tim Bray
      • Re: Re: [namespaceDocument-8] 14 Theses, Ronald Bourret
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
      • Re: Re: [namespaceDocument-8] 14 Theses, Ronald Bourret
      • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
      • Re: Re: [namespaceDocument-8] 14 Theses, John Cowan
      • RE: Re: [namespaceDocument-8] 14 Theses, Jandia Cyril
    • Re: Re: [namespaceDocument-8] 14 Theses, Patrick Stickler
• XML for Corporate Sites, xpal
• Help XML Pattern Matching, Semana, Erwin
• ANN: XML database products list updated, Ronald Bourret
• regd security while transmitting XML Data, K.R.Vaidyanathan
  • RE: regd security while transmitting XML Data, John F Schlesinger
• XML API vs. Object API, Nicolas LEHUEN
• RE: Plumbing versus semantics..., Michael Brennan
• Plumbing versus semantics..., Andrzej Jan Taramina
• XML Parsing Using Expat in LIBWWW API, Sinha, Raj (Raj)
• How to get the attributes from the Document node, asd asd
  • Re: How to get the attributes from the Document node, asd asd
• RE: Traditional RPC, Bullard, Claude L (Len)
  • Re: Traditional RPC, Alaric Snell
    • Message not available
      • Re: Traditional RPC, Paul Prescod
      • SOAP-RPC and REST and security, Mike Champion
      • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
      • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
      • Re: SOAP-RPC and REST and security, Paul Prescod
      • Re: SOAP-RPC and REST and security, Gavin Thomas Nicol
      • Re: SOAP-RPC and REST and security, Paul Prescod
  • Re: RE: Traditional RPC, Mike Champion
    • Re: RE: Traditional RPC, Gavin Thomas Nicol
    • Message not available
      • Re: Traditional RPC, Paul Prescod
  • Re: Traditional RPC, Dave Winer
  • <Possible follow-ups>
  • RE: RE: Traditional RPC, Bullard, Claude L (Len)
    • RE: Traditional RPC, Mike Champion
      • Re: Traditional RPC, Gavin Thomas Nicol
    • Re: RE: Traditional RPC, Gavin Thomas Nicol
    • Message not available
      • Re: Traditional RPC, Paul Prescod
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Bullard, Claude L (Len)
    • Re: Traditional RPC, Dave Winer
  • RE: Traditional RPC, Dare Obasanjo
    • Re: Traditional RPC, Dave Winer
    • Re: Traditional RPC, Gavin Thomas Nicol
  • RE: Traditional RPC, Dare Obasanjo
    • Re: Traditional RPC, Paul Prescod
  • RE: Traditional RPC, Joshua Allen
    • Re: Traditional RPC, Paul Prescod
  • RE: Traditional RPC, Dare Obasanjo
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Bullard, Claude L (Len)
    • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Francis Norton
      • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Alaric Snell
      • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Alaric Snell
  • RE: Traditional RPC, Bullard, Claude L (Len)
    • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Simon St.Laurent
      • RE: Traditional RPC, Bill de hÓra
    • Re: Traditional RPC, Dave Winer
  • RE: Traditional RPC, Bullard, Claude L (Len)
    • Re: Traditional RPC, Steven R. Newcomb
    • Re: Traditional RPC, Paul Prescod
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Matthew Gertner
    • Re: Traditional RPC, Gavin Thomas Nicol
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Matthew Gertner
    • Re: Traditional RPC, Gavin Thomas Nicol
  • RE: Traditional RPC, Joshua Allen
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Bullard, Claude L (Len)
  • RE: Traditional RPC, Bullard, Claude L (Len)
• Javascript Search, Sebastian Denef
• Restriction of MIXED, Anderson, John
  • RE: Restriction of MIXED, Priscilla Walmsley
• RE: 14 Theses around "Namespace Documents", Manos Batsis
  • RE: 14 Theses around "Namespace Documents", Tim Bray
  • <Possible follow-ups>
  • RE: 14 Theses around "Namespace Documents", Bullard, Claude L (Len)
  • RE: 14 Theses around "Namespace Documents", Michael Brennan
• RE: Tower of Babbage, Manos Batsis
• 14 Theses around "Namespace Documents", Tim Bray
  • Re: 14 Theses around "Namespace Documents", Simon St.Laurent
  • RE: 14 Theses around "Namespace Documents", Jandia Cyril
    • RE: 14 Theses around "Namespace Documents", Jandia Cyril
      • RE: 14 Theses around "Namespace Documents", Jandia Cyril
• Tower of Babbage, Jonathan Borden
• reminder: call for papers, XTech/O'Reilly Open Source conference, Simon St.Laurent
• REST, SQL, Simon St.Laurent
  • Traditional RPC, Dave Winer
    • Re: Traditional RPC, Mike Champion
      • Re: Traditional RPC, Gavin Thomas Nicol
      • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Dave Winer
      • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Dave Winer
      • Re: Traditional RPC, Alaric Snell
      • Re: Traditional RPC, Elliotte Rusty Harold
      • Message not available
      • Re: Traditional RPC, Paul Prescod
    • Re: Traditional RPC, Paul Prescod
      • Re: Traditional RPC, Dave Winer
• RE: Re: Why REST was Re: URIs are simply names, Joshua Allen
  • <Possible follow-ups>
  • RE: Re: Why REST was Re: URIs are simply names, Dare Obasanjo
    • Re: Re: Why REST was Re: URIs are simply names, Paul Prescod
    • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • namespaces and resources was :Re: Re: Why REST, Jonathan Borden
      • Re: namespaces and resources was :Re: Re: Why REST, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Joe English
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, David Carlisle
      • Message not available
      • Re: Re: Why REST was Re: URIs are simply names, Paul Prescod
  • RE: Re: Why REST was Re: URIs are simply names, Dare Obasanjo
  • RE: Re: Why REST was Re: URIs are simply names, Dare Obasanjo
  • RE: Re: Why REST was Re: URIs are simply names, Bullard, Claude L (Len)
• Translating RELAX NG to XSD, James Clark
  • Message not available
    • Re: Translating RELAX NG to XSD, Jeni Tennison
• creating a URI class, Simon St.Laurent
  • Re: creating a URI class, Elliotte Rusty Harold
    • Re: creating a URI class, Simon St.Laurent
• URI confusions, clarifications, Simon St.Laurent
• RE: [OT] "Blackbird" not "Blackberry" Re: WSIO vs. Semantic Web- Setting the Record Straight, Bullard, Claude L (Len)
  • Re: [OT] "Blackbird" not "Blackberry" Re: WSIO vs. Semantic Web- Setting the Record Straight, Paul Prescod
• RE: [OT] "Blackbird" not "Blackberry" Re: WSIO vs. Semantic Web- Setting the Record Straight, Joshua Allen
  • Re: [OT] "Blackbird" not "Blackberry" Re: WSIO vs. Semantic Web- Setting the Record Straight, Paul Prescod
• Using XML for data transfer between B2B applications, Jeffrey I Condon
• RE: Table in DTD, Dudley, Mark
• Validating against schema a file with another schema in it., Yuriy
• RE: WSIO vs. Semantic Web - Setting the Record Straight, Joshua Allen
  • <Possible follow-ups>
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
    • Re: RE: WSIO vs. Semantic Web - Setting the Record Straight, Mike Champion
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
      • [OT] "Blackbird" not "Blackberry" Re: WSIO vs. Semantic Web- Setting the Record Straight, Mike Champion
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Jonathan Borden
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Joshua Allen
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
  • RE: RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Joshua Allen
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Jonathan Borden
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
      • schema & polymorphism - resolving duplicate element definitions, Chris Hoehn
      • Re: schema & polymorphism - resolving duplicate element definitions, Henry S. Thompson
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Jonathan Borden
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Phil Fuhlman
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, John Cowan
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Mike Champion
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Atchley, John
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Joshua Allen
    • Re: WSIO vs. Semantic Web - Setting the Record Straight, Paul Prescod
  • RE: WSIO vs. Semantic Web - Setting the Record Straight, Bullard, Claude L (Len)
• Table in DTD, hongbin Liu
• [Announcement] First version of W3C DOM Level 1 Core Conformance Test Suite released, Dimitris Dimitriadis
• Web Service Specifications (Was: RE: URIs are simply names was: Re: "Abstract" URIs), Bullard, Claude L (Len)
• Can transformations add/change the DOCTYPE?, Caro, Samuel
• Is DOM parsing real-time?, asd asd
  • Re: Is DOM parsing real-time?, Mike Champion
• Redefining ComplexType, Jose Guillén Vázquez
• Layers and QNames, Eric van der Vlist
• Hook Stuff Together, Micah Dubinko
  • Re: Hook Stuff Together, Mike Champion
    • Re: Hook Stuff Together, Eric van der Vlist
  • Re: Hook Stuff Together, Paul Prescod
• Ecclesiastes 12:12, Tim Bray
  • Re: Ecclesiastes 12:12, Paul Prescod
    • RE: Ecclesiastes 12:12, Evan Lenz
      • Re: Ecclesiastes 12:12, Paul Prescod
  • Re: Ecclesiastes 12:12, Jeff Rafter
• Re: URIs are simply names was: Re: "Abstract" URIs, jborden
  • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
    • Re: URIs are simply names was: Re: "Abstract" URIs, Steven R. Newcomb
      • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
      • Re: URIs are simply names was: Re: "Abstract"URIs, Al Snell
• RE: Errors in Kendall Clark's xml.com article on QNames, Michael Brennan
• RE: Web Services Hype and Reality (was RE: WSIO vs. Semantic Web, Joshua Allen
• More Patent Lunacies, Bullard, Claude L (Len)
• Modular XHTML, M. Penney
• RE: Names and locations (WAS: Why REST?), Bullard, Claude L (Len)
  • Re: Names and locations (WAS: Why REST?), Patrick Stickler
• RE: Streaming Transformations for XML, Gert Baudoncq
  • <Possible follow-ups>
  • RE: Streaming Transformations for XML, Manos Batsis
  • RE: Streaming Transformations for XML, Jandia Cyril
  • RE: Streaming Transformations for XML, Michael Brennan
    • Re: Streaming Transformations for XML, Paul Prescod
    • Re: Streaming Transformations for XML, Petr Cimprich
  • RE: Streaming Transformations for XML, Michael Brennan
    • DONT REPLY..., Sven Ewert
      • Re: DONT REPLY..., Andrzej Jan Taramina
  • Fwd: Fwd: Streaming Transformations for XML, Jandia Cyril
  • RE: Streaming Transformations for XML, Manos Batsis
  • RE: Streaming Transformations for XML, Michael Brennan
    • Re: Streaming Transformations for XML, Petr Cimprich
• RE: Service discovery, Bullard, Claude L (Len)
  • Re: Service discovery, Paul Prescod
  • <Possible follow-ups>
  • RE: Service discovery, Bullard, Claude L (Len)
    • Re: Service discovery, Paul Prescod
  • RE: Service discovery, Jeff Lowery
    • Re: Service discovery, Paul Prescod
• Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
  • Re: Errors in Kendall Clark's xml.com article on QNames, Simon St.Laurent
  • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
    • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
      • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
      • Re: Errors in Kendall Clark's xml.com article on QNames, Simon St.Laurent
  • Re: Errors in Kendall Clark's xml.com article on QNames, Elliotte Rusty Harold
    • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
      • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
      • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
    • Re: Errors in Kendall Clark's xml.com article on QNames, Gavin Thomas Nicol
    • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
    • Re: Errors in Kendall Clark's xml.com article on QNames, Joe English
  • Re: Errors in Kendall Clark's xml.com article on QNames, Tim Bray
    • Re: Errors in Kendall Clark's xml.com article on QNames, Amy Lewis
    • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
      • Re: Errors in Kendall Clark's xml.com article on QNames, David Carlisle
      • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
      • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
      • Re: Errors in Kendall Clark's xml.com article on QNames, David Carlisle
      • Re: Errors in Kendall Clark's xml.com article on QNames, Norman Walsh
    • RE: Errors in Kendall Clark's xml.com article on QNames, Aaron Skonnard
      • Re: Errors in Kendall Clark's xml.com article on QNames, Eric van der Vlist
  • RE: Errors in Kendall Clark's xml.com article on QNames, Evan Lenz
    • Re: Errors in Kendall Clark's xml.com article on QNames, Henry S. Thompson
      • RE: Errors in Kendall Clark's xml.com article on QNames, Evan Lenz
• Streaming Transformations for XML, Petr Cimprich
  • RE: Streaming Transformations for XML, Leigh Dodds
    • Re: Streaming Transformations for XML, Petr Cimprich
  • Re: Streaming Transformations for XML, Simon St.Laurent
    • newbie question, XML Dude
    • Re: Streaming Transformations for XML, Petr Cimprich
      • Re: Streaming Transformations for XML, Simon St.Laurent
  • <Possible follow-ups>
  • Re: Streaming Transformations for XML, Petr Cimprich
• Names and locations (WAS: Why REST?), Miles Sabin
  • Re: Names and locations (WAS: Why REST?), Patrick Stickler
    • Re: Names and locations (WAS: Why REST?), Kal Ahmed
• Architectural Forms, A Summary, Leigh Dodds
  • Re: Architectural Forms, A Summary, Steven R. Newcomb
    • Re: Architectural Forms, A Summary, Rick Jelliffe
      • Re: Architectural Forms, A Summary, Steven R. Newcomb
• RE: WSIO vs. Semantic Web, Joshua Allen
  • Re: RE: WSIO vs. Semantic Web, Mike Champion
  • <Possible follow-ups>
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
    • RE: WSIO vs. Semantic Web, Simon St.Laurent
      • Re: WSIO vs. Semantic Web, Francis Norton
      • Re: WSIO vs. Semantic Web, Simon St.Laurent
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
    • RE: WSIO vs. Semantic Web, Mike Champion
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web, Mark Seaborne
    • Re: WSIO vs. Semantic Web, Alaric Snell
    • Re: WSIO vs. Semantic Web, Joe English
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
    • RE: WSIO vs. Semantic Web, Mike Champion
  • RE: RE: WSIO vs. Semantic Web, Joshua Allen
    • Web Services Hype and Reality (was RE: WSIO vs. Semantic Web, Mike Champion
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web, Joshua Allen
    • Re: RE: WSIO vs. Semantic Web, Mike Champion
  • Re: WSIO vs. Semantic Web, Alaric Snell
  • Re: WSIO vs. Semantic Web, Alaric Snell
  • RE: WSIO vs. Semantic Web, Joshua Allen
    • Re: WSIO vs. Semantic Web, Paul Prescod
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
  • RE: WSIO vs. Semantic Web, Joshua Allen
  • RE: WSIO vs. Semantic Web, Joshua Allen
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
    • Re: WSIO vs. Semantic Web, Paul Prescod
  • RE: WSIO vs. Semantic Web, Bullard, Claude L (Len)
• Type of an Element, rajac
• WSIO vs. Semantic Web, Joshua Allen
  • Re: WSIO vs. Semantic Web, Tim Bray
  • Re: WSIO vs. Semantic Web, Paul Prescod
    • Re: WSIO vs. Semantic Web, Mike Champion
      • Re: WSIO vs. Semantic Web, Paul Prescod
      • Re: WSIO vs. Semantic Web, Alaric Snell
      • Re: WSIO vs. Semantic Web, Paul Prescod
      • Re: WSIO vs. Semantic Web, Al B. Snell
      • Re: WSIO vs. Semantic Web, Gavin Thomas Nicol
      • Re: WSIO vs. Semantic Web, Mike Champion
      • Re: WSIO vs. Semantic Web, Gavin Thomas Nicol
      • Re: WSIO vs. Semantic Web, Mike Champion
• RE: "Abstract" URIs, Joshua Allen
  • <Possible follow-ups>
  • RE: "Abstract" URIs, Bullard, Claude L (Len)
• RE: REST and HTTP extensions (was Re: Re: Why REST? ), Joshua Allen
• [Fwd: Re: Schematron/Schema market share], Eddie Robertsson
• RE: Xerces error report... answered, Atchley, John
• Xerces error report "attribute 'foo' should be qualified", Atchley, John
  • Re: Xerces error report "attribute 'foo' should be qualified", Richard Tobin
• RE: Principle of Sustainable Complexity, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Principle of Sustainable Complexity, Joshua Allen
    • XML utilities (was RE: Principle of SustainableComplexity), Simon St.Laurent
    • Re: Principle of Sustainable Complexity, Henry S. Thompson
  • RE: Principle of Sustainable Complexity, Michael Brennan
    • Re: Principle of Sustainable Complexity, Gavin Thomas Nicol
  • RE: Principle of Sustainable Complexity, Michael Brennan
    • Re: Principle of Sustainable Complexity, Gavin Thomas Nicol
• Principle of Sustainable Complexity, Micah Dubinko
• Validation of xm document using a xml schema, K.R.Vaidyanathan
  • Re: Validation of xm document using a xml schema, Henry S. Thompson
• RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
  • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
  • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
    • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Gavin Thomas Nicol
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Gavin Thomas Nicol
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • OT: Arguments (was: a number of other threads), Leigh Dodds
      • Re: OT: Arguments (was: a number of other threads), Alaric Snell
      • Re: OT: Arguments (was: a number of other threads), Simon St.Laurent
      • Re: OT: Arguments (was: a number of other threads), Paul Prescod
      • OT: Re: OT: Arguments (was: a number of other threads), Rick Jelliffe
      • Re: OT: Re: OT: Arguments (was: a number of other threads), John Cowan
      • Re: Re: Why REST? (RE: WSIO- With Name), Mark Baker
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Mark Baker
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Mark Baker
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
      • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
      • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
      • "Abstract" URIs, Paul Prescod
      • Re: "Abstract" URIs, Simon St.Laurent
      • Re: "Abstract" URIs, Alaric Snell
      • URIs are simply names was: Re: "Abstract" URIs, Jonathan Borden
      • Re: URIs are simply names was: Re: "Abstract" URIs, Alaric Snell
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, Eric van der Vlist
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, Eric van der Vlist
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, Eric van der Vlist
      • Re: URIs are simply names was: Re: "Abstract" URIs, Jonathan Borden
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract"URIs, Jonathan Borden
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, Gavin Thomas Nicol
      • Re: URIs are simply names was: Re: "Abstract" URIs, Mark Baker
      • Re: URIs are simply names was: Re: "Abstract" URIs, Gavin Thomas Nicol
      • Re: URIs are simply names was: Re: "Abstract" URIs, Mark Baker
      • Re: URIs are simply names was: Re: "Abstract" URIs, Jonathan Borden
      • Re: URIs are simply names was: Re: "Abstract" URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract" URIs, Gavin Thomas Nicol
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
      • Re: URIs are simply names was: Re: "Abstract" URIs, Jonathan Borden
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names R, Jonathan Borden
      • Two Perspectives (was Re: URIs are simply names R), Steven R. Newcomb
      • Re: Two Perspectives (was Re: URIs are simply names R), Patrick Stickler
      • Re: Re: Two Perspectives (was Re: URIs are simply names R), Sean McGrath
      • Re: Re: Two Perspectives (was Re: URIs are simplynames R), John Cowan
      • Re: Re: Two Perspectives (was Re: URIs are simply names R), Sean McGrath
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Alaric Snell
      • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
      • Re: URIs are simply names was: Re: "Abstract" URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
      • Re: URIs are simply names was: Re: "Abstract" URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract" URIs, John Cowan
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract" URIs, Alaric Snell
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Patrick Stickler
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Simon St.Laurent
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Simon St.Laurent
      • Re: URIs are simply names was: Re: "Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was: Re: "Abstract"URIs, Simon St.Laurent
      • Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST, Mike Champion
      • Re: Re: Why REST, Simon St.Laurent
      • Re: Re: Why REST, Sean McGrath
      • Re: Re: Why REST, John Cowan
      • Re: Re: Why REST, Sean McGrath
      • Re: Re: Why REST, Paul Prescod
      • Re: Re: Why REST was Re: URIs are simply names, Joe English
      • Re: Re: Why REST was Re: URIs are simply names, Gary Stephenson
      • Re: Re: Why REST was Re: URIs are simply names, Mike Champion
      • Re: Re: Why REST was Re: URIs are simply names, Gary Stephenson
      • Re: Re: Why REST was Re: URIs are simply names, Mike Champion
      • Re: Re: Why REST was Re: URIs are simply names, Gary Stephenson
      • Re: Re: Why REST was Re: URIs are simply names, Paul Prescod
      • Re: Re: Why REST was Re: URIs are simply names, Elliotte Rusty Harold
      • Re: Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST was Re: URIs are simply names, Jonathan Borden
      • Re: Re: Why REST was Re: URIs are simply names, Paul Prescod
      • Re: Re: Why REST was Re: URIs are simply names, Joe English
      • Re: Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST was Re: URIs are simply names, Elliotte Rusty Harold
      • Re: Re: Why REST was Re: URIs are simply names, John Cowan
      • Re: Re: Why REST was Re: URIs are simply names, Simon St.Laurent
      • Re: Re: Why REST was Re: URIs are simply names, Joe English
      • standardization (was Re: URIs are simply names), Simon St.Laurent
      • Namespace and URIs, Paul Prescod
      • Re: Namespace and URIs, Jonathan Borden
      • Re: Namespace and URIs, Paul Prescod
      • Re: Namespace and URIs, Jonathan Borden
      • Crossposting: was Namespaces and URIs, Tim Bray
      • Re: Namespace and URIs, John Cowan
      • Re: Namespace and URIs, Patrick Stickler
      • Re: URIs are simply names was: Re:"Abstract"URIs, Patrick Stickler
      • Message not available
      • Re: URIs are simply names was: Re:"Abstract"URIs, Paul Prescod
      • Re: URIs are simply names was:Re:"Abstract"URIs, Patrick Stickler
      • Re: "Abstract" URIs, Patrick Stickler
      • Re: "Abstract" URIs, Simon St.Laurent
      • Re: Re: Why REST? (RE: WSIO- With Name), Gavin Thomas Nicol
      • RE: Re: Why REST? (RE: WSIO- With Name), Bill de hÓra
      • Re: Re: Why REST? (RE: WSIO- With Name), Gavin Thomas Nicol
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
      • Re: Re: Why REST? (RE: WSIO- With Name), Gavin Thomas Nicol
      • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
      • Re: Re: Why REST? (RE: WSIO- With Name), Mark Baker
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
      • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
      • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
      • Re: Re: Why REST? (RE: WSIO- With Name), Mark Baker
      • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
  • <Possible follow-ups>
  • RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
    • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
  • RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
    • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
    • Service discovery, Paul Prescod
  • RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
    • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
    • REST and HTTP extensions (was Re: Re: Why REST? ), Mike Champion
      • Re: REST and HTTP extensions (was Re: Re: Why REST? ), John Cowan
      • Re: REST and HTTP extensions (was Re: Re: Why REST? ), Paul Prescod
    • Re: Re: Why REST? (RE: WSIO- With Name), Alaric Snell
      • Re: Re: Why REST? (RE: WSIO- With Name), Paul Prescod
  • RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
  • RE: Re: Why REST? (RE: WSIO- With Name), Joshua Allen
    • Re: Re: Why REST? (RE: WSIO- With Name), John Cowan
  • RE: Re: Why REST? (RE: WSIO- With Name), Joshua Allen
    • Resource representations, Paul Prescod
      • Re: Resource representations, Mark Baker
  • RE: Re: Why REST? (RE: WSIO- With Name), Joshua Allen
  • RE: Re: Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
• Stylesheets for generating XML Schema documentation, Doyle, Michael J
  • Re: Stylesheets for generating XML Schema documentation, Christopher R. Maden
• RE: commodity web, Manos Batsis
  • RE: commodity web, Bill de hÓra
• Why REST? (RE: WSIO- With Name), Bullard, Claude L (Len)
  • Re: Why REST? (RE: WSIO- With Name), Paul Prescod
• SGML Parsers, Anderson, John
• DOM parsers & default values, Kevin Burges
• RE: Array of #PCDATA, Prashanth Rao
  • Re: Array of #PCDATA, rajac
• Array of #PCDATA, rajac
• RE: REST has too many verbs, Bullard, Claude L (Len)
  • Re: REST has too many verbs, Gavin Thomas Nicol
  • <Possible follow-ups>
  • RE: REST has too many verbs, Bullard, Claude L (Len)
    • Re: REST has too many verbs, Paul Prescod
    • Re: REST has too many verbs, Paul Prescod
  • Re: REST has too many verbs, Alaric Snell (by way of Alaric Snell <alaric@a...>)
  • RE: REST has too many verbs, Bullard, Claude L (Len)
  • RE: REST has too many verbs, Bullard, Claude L (Len)
    • Re: REST has too many verbs, Paul Prescod
  • RE: REST has too many verbs, Henrik Frystyk Nielsen
    • RE: REST has too many verbs, Simon St.Laurent
  • RE: REST has too many verbs, Henrik Frystyk Nielsen
    • RE: REST has too many verbs, Simon St.Laurent
  • RE: REST has too many verbs, Michael Brennan
  • RE: REST has too many verbs, Henrik Frystyk Nielsen
    • RE: REST has too many verbs, Simon St.Laurent
  • RE: REST has too many verbs, Henrik Frystyk Nielsen
  • RE: REST has too many verbs, Jeff Lowery
• posting an XML data, ZILBER,LEONID (HP-NewJersey,ex1)
  • Re: posting an XML data, Mike Brown
• [announce] XML Spy 4.3 Suite Released - adds SOAP debugger, XPath analyzer, SQLXML Support., Larry E. Kim
• REST has too many verbs, Simon St.Laurent
  • Re: REST has too many verbs, Gavin Thomas Nicol
    • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
  • Re: REST has too many verbs, Paul Prescod
    • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Joe English
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Amy Lewis
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Simon Fell
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Simon St.Laurent
      • RE: REST has too many verbs, Bill de hÓra
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • RE: REST has too many verbs, Bill de hÓra
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Mike Champion
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Mike Champion
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Alaric Snell
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Alaric Snell
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • RE: REST has too many verbs, Bill de hÓra
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Mark Baker
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Mark Baker
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Mark Baker
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Mark Baker
      • A priori agreement, Paul Prescod
      • Re: REST has too many verbs, Simon St.Laurent
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • RE: REST has too many verbs, Bill de hÓra
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Mark Baker
      • RE: REST has too many verbs, Leigh Dodds
      • Re: REST has too many verbs, Paul Prescod
      • RE: REST has too many verbs, Bill de hÓra
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Alaric Snell
      • Re: REST has too many verbs, Sean McGrath
      • commodity web, Bill de hÓra
    • Re: REST has too many verbs, W. E. Perry
      • Re: REST has too many verbs, Paul Prescod
    • Re: REST has too many verbs, Gavin Thomas Nicol
      • Re: REST has too many verbs, Paul Prescod
      • Re: REST has too many verbs, Gavin Thomas Nicol
• MathML to English, SHARPE, Ian
  • Re: MathML to English, David Carlisle
• RE: WSIO- With Name, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: WSIO- With Name, Bullard, Claude L (Len)
    • Re: WSIO- With Name, Paul Prescod
  • RE: WSIO- With Name, Bullard, Claude L (Len)
    • Re: WSIO- With Name, Paul Prescod
  • RE: WSIO- With Name, Bullard, Claude L (Len)
    • Re: WSIO- With Name, Paul Prescod
• conditions in xml schema, K.R.Vaidyanathan
  • Re: conditions in xml schema, John Cowan
• Solved: Default attribute values at a higher level element?, Andrzej Jan Taramina
• OASIS TC Call For Participation: XML Common Biometric Format TC, Karl F. Best
• WSIO- With Name, Bullard, Claude L (Len)
  • Re: WSIO- With Name, Mike Champion
    • Re: WSIO- With Name, Mark Baker
• [Ann - Zvon] Templatotron, Miloslav Nic
  • Re: [Ann - Zvon] Templatotron, james anderson
    • Re: [Ann - Zvon] Templatotron, Miloslav Nic
      • RE: [Ann - Zvon] Templatotron, Jose F. Osorio
• Compring two XML docs from Java, Toivo Lainevool
  • Re: Compring two XML docs from Java, Robin LaFontaine
    • RE: Compring two XML docs from Java, Toivo Lainevool
      • RE: Compring two XML docs from Java, Robin LaFontaine
• Happy birthday, Tim Bray
• One more time: Default attribute values at a higher level element?, Andrzej Jan Taramina
  • Re: One more time: Default attribute values at a higher level element?, Richard Tobin
• RE: Input and output routines for Unicode in C++, Michael Brennan
• RE: Web Services and REST: what is to be done?, Michael Brennan
  • Input and output routines for Unicode in C++, Trevor Croll
• creating links, Jeff S.
• Default values, SysGrad
• ANN: Oracle XDK 9.2.0.1 Production Release online, Jinyu.Wang
• RE: Doctypes again (was Re: Documents within documents), Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Doctypes again (was Re: Documents within documents), Bullard, Claude L (Len)
• [ANN]: DecisionSoft announce release of XPath for Xerces-C, Ian Stokes-Rees
• RE: Simple Schema, KRUMPOLEC Martin
  • <Possible follow-ups>
  • Re: Simple Schema, rajac
  • RE: Simple Schema, KRUMPOLEC Martin
    • Re: Simple Schema, rajac
      • RE: Simple Schema, Priscilla Walmsley
  • RE: Simple Schema, KRUMPOLEC Martin
• Simple Schema, rajac
  • Re: Simple Schema, Henry S. Thompson
• Re: XML Designing Problems., Rajesh AVRS
  • <Possible follow-ups>
  • Re: XML Designing Problems., Rajesh AVRS
    • Re: XML Designing Problems., Fredrik Lindgren
• How to map to desierd data types?., rajac
• XML Designing Problems., Rajesh AVRS
  • RE: XML Designing Problems., Michael Kay
    • XPath Sample Programs., Rajesh AVRS
    • Re: XML Designing Problems., Rajesh AVRS
• RE: Documents within documents, Michael Brennan
  • <Possible follow-ups>
  • RE: Documents within documents, Wayne Steele
    • Re: Documents within documents, Marcus Carr
  • RE: Documents within documents, Michael Brennan
    • Re: Documents within documents, Marcus Carr
    • Doctypes again (was Re: Documents within documents), Bill Lindsey
      • RE: Doctypes again (was Re: Documents within documents), Michael Kay
      • Re: Doctypes again (was Re: Documents within documents), Henry S. Thompson
      • RE: Doctypes again (was Re: Documents withindocuments), Robin Cover
      • RE: Doctypes again (was Re: Documents within documents), Michael Kay
    • Re: Documents within documents, David Carlisle
    • Re: Documents within documents, John Cowan
  • Re: Documents within documents, Wayne Steele
    • Re: Documents within documents, Marcus Carr
    • Re: Documents within documents, Sean McGrath
      • Re: Documents within documents, Rick Jelliffe
  • Re: Documents within documents, Robin LaFontaine
• RE: WSIO and Good is Better, Bullard, Claude L (Len)
  • Re: WSIO and Good is Better, Rick Jelliffe
    • Re: WSIO and Good is Better, Robin Cover
  • <Possible follow-ups>
  • RE: WSIO and Good is Better, Bullard, Claude L (Len)
  • RE: WSIO and Good is Better, Michael Brennan
  • RE: WSIO and Good is Better, Bullard, Claude L (Len)
  • RE: WSIO and Good is Better, Bullard, Claude L (Len)
  • RE: WSIO and Good is Better, Bullard, Claude L (Len)
• Displaying XML in IE window, Haque, Suraiya
• Re: XML Schema Simple Graphical User Interface, JOHN CANT /6183
• Schema tutorials (was RE: MODERATORIAL: Five years of XML-DEV), Manos Batsis
• Re: MODERATORIAL: Five years of XML-DEV, karen.bui
  • Re: MODERATORIAL: Five years of XML-DEV, Roger L. Costello
  • <Possible follow-ups>
  • RE: MODERATORIAL: Five years of XML-DEV, Eric Vermetten
  • RE: MODERATORIAL: Five years of XML-DEV, Michael Brennan
• RE: WSIO (was Re: Categories of Web Service messages), Bullard, Claude L (Len)
  • RE: WSIO and Good is Better, Mike Champion
  • <Possible follow-ups>
  • RE: WSIO (was Re: Categories of Web Service messages), Michael Brennan
    • Re: RE: WSIO (was Re: Categories of Web Service messages), Mike Champion
• RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
• XML Abstract Query anybody ?, raghavendra.ml
  • Re: XML Abstract Query anybody ?, Gavin Thomas Nicol
• ANN: STM-ML - a markup language for scientific publishing, Peter Murray-Rust
• RE: XML to UML, Nick Laqua
  • <Possible follow-ups>
  • RE: XML to UML, Nick Laqua
  • RE: XML to UML, Tom Gaven
  • RE: XML to UML, Koorn, Wilco
  • XML to UML, SHARPE, Ian
  • RE: XML to UML, Koorn, Wilco
• XML to UML, SHARPE, Ian
  • <Possible follow-ups>
  • Re: XML to UML, Pete Kirkham
• Documents within documents, Michael Kay
  • Re: Documents within documents, Paul Prescod
• RE: XML Schema Simple Type Definitions, CHIUSANO, Joseph
• XML Schema Simple Type Definitions, CHIUSANO, Joseph
  • Re: XML Schema Simple Type Definitions, Ramesh Gupta
  • Re: XML Schema Simple Type Definitions, Eddie Robertsson
  • RE: XML Schema Simple Type Definitions, Priscilla Walmsley
    • XML Schema Simple Graphical User Interface, Trevor Croll
      • Re: XML Schema Simple Graphical User Interface, Eddie Robertsson
      • MODERATORIAL: Five years of XML-DEV, Peter Murray-Rust
• Better is Still Better, Bullard, Claude L (Len)
  • Re: Better is Still Better, Ramesh Gupta
• RE: A heavier-weight proposal for character entity definition, Bullard, Claude L (Len)
• Re: living fossil?, Wayne Steele
  • <Possible follow-ups>
  • RE: FW: living fossil?, Joshua Allen
• [xmlstds] Release Announcement, MWS Tech Support
• RE: Using <choice> to enforce rules, Sean Zhang
  • Re: Using <choice> to enforce rules, Eddie Robertsson
  • <Possible follow-ups>
  • RE: Using <choice> to enforce rules, Michael Brennan
• Re: XML Schemas for X12 documents, K.R.Vaidyanathan
  • <Possible follow-ups>
  • RE: XML Schemas for X12 documents, John Evdemon
• XML Schemas for X12 documents, K.R.Vaidyanathan
  • Re: XML Schemas for X12 documents, Alaric Snell
• living fossil?, Francis Norton
• XMLNoteTree Latest release available for download - with smaller URL, Trevor Croll
• Re: A heavier-weight proposal for character entitydefinition, James Clark
  • Re: A heavier-weight proposal for character entity definition, Henry S. Thompson
  • Re: A heavier-weight proposal for character entity definition, Rick Jelliffe
    • Re: A heavier-weight proposal for character entity definition, David Carlisle
  • <Possible follow-ups>
  • Re: A heavier-weight proposal for character entitydefinition, James Clark
    • Re: A heavier-weight proposal for character entity definition, Tim Bray
    • Re: A heavier-weight proposal for character entity definition, Rick Jelliffe
    • Re: A heavier-weight proposal for character entitydefinition, David Carlisle
    • Re: A heavier-weight proposal for character entitydefinition, Simon St.Laurent
• FW: DTD validation without a DOCTYPE, Caro, Samuel
  • Re: FW: DTD validation without a DOCTYPE, Simon St.Laurent
  • <Possible follow-ups>
  • RE: DTD validation without a DOCTYPE, Michael Brennan
    • RE: DTD validation without a DOCTYPE, Michael Kay
• DTD validation without a DOCTYPE, Caro, Samuel
  • Re: DTD validation without a DOCTYPE, Joe English
  • Re: DTD validation without a DOCTYPE, G. Ken Holman
• Using <choice> to enforce rules, Sean Zhang
  • Re: Using <choice> to enforce rules, Eddie Robertsson
    • XMLNoteTree Latest release available for download, Trevor Croll
• Default attribute values at a higher level element?, Andrzej Jan Taramina
• Namespace terminology, Lars Marius Garshol
  • RE: Namespace terminology, Evan Lenz
    • Re: Namespace terminology, Lars Marius Garshol
      • RE: Namespace terminology, Michael Fitzgerald
  • Re: Namespace terminology, John Cowan
    • RE: Namespace terminology, Julian Reschke
      • Re: Namespace terminology, John Cowan
      • RE: Namespace terminology, Julian Reschke
  • RE: Namespace terminology, Michael Kay
  • Re: Namespace terminology, Ronald Bourret
  • Re: Namespace terminology, Richard Tobin
• _Lastworda betst_, John Cowan
• ANN: Ents 0.2, Simon St.Laurent
• SV: Categories of Web Service messages: data-oriented v saction-oriented, Jens Jakob Andersen, PDI
• RE: Categories of Web Service messages: data-oriented v, Michael Brennan
  • <Possible follow-ups>
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Mark Baker
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
      • Re: Categories of Web Service messages: data-oriented v, Gavin Thomas Nicol
      • Number of methods., Paul Prescod
      • Re: Number of methods., Gavin Thomas Nicol
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
      • Re: Categories of Web Service messages: data-oriented v, Mike Champion
      • Re: Categories of Web Service messages: data-oriented v, Gavin Thomas Nicol
      • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
      • Web Services and REST: what is to be done?, Mike Champion
      • Re: Web Services and REST: what is to be done?, Paul Prescod
    • RE: Categories of Web Service messages: data-oriented v, Michael Kay
      • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
      • RE: Categories of Web Service messages: data-oriented v, Michael Kay
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
  • RE: Categories of Web Service messages: data-oriented v, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Paul Prescod
      • Re: Categories of Web Service messages: data-oriented v, Gavin Thomas Nicol
• RE: looking for XML vendor in Santa Clara, Michael Brennan
• RE: Categories of Web Service messages: data-oriented v s action-oriented, Bullard, Claude L (Len)
• RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
  • <Possible follow-ups>
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Paul Prescod
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
      • WSIO (was Re: Categories of Web Service messages), Simon St.Laurent
      • Re: WSIO (was Re: Categories of Web Service messages), Tim Bray
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Paul Prescod
• RE: What am I overlooking...? (namespaces, validation, & xsv), Christopher R. Maden
  • <Possible follow-ups>
  • RE: What am I overlooking...? (namespaces, validation, & xsv), Atchley, John
• RE: Categories of Web Service messages: data-oriented v s action-oriented, Jeff Lowery
  • <Possible follow-ups>
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Michael Brennan
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Bullard, Claude L (Len)
    • RE: Categories of Web Service messages: data-oriented v s action-oriented, Bill de hÓra
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented v s action-oriented, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Mark Baker
      • Re: Categories of Web Service messages: data-oriented v, Andrzej Jan Taramina
• RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
  • <Possible follow-ups>
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
    • Re: Categories of Web Service messages: data-oriented v, Mark Baker
      • RE: Categories of Web Service messages: data-oriented v, Michael Kay
      • Re: Categories of Web Service messages: data-oriented v, Francis Norton
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
    • RE: Categories of Web Service messages: data-oriented v saction-oriented, Mike Champion
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, Jeff Greif
      • Re: Categories of Web Service messages: data-oriented v saction-oriented, Mike Champion
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, Francis Norton
    • RE: Categories of Web Service messages: data-oriented v s action-oriented, Andrzej Jan Taramina
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, John Cowan
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, Andrzej Jan Taramina
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, Jeff Greif
      • Re: Categories of Web Service messages: data-oriented v s action-oriented, W. E. Perry
    • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hÓra
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Sean McGrath
      • Re: Categories of Web Service messages: data-oriented vs action-oriented, Alaric Snell
      • Re: Categories of Web Service messages: data-oriented vs action-oriented, Sean McGrath
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hÓra
      • Re: Categories of Web Service messages: data-oriented vs action-oriented, Alaric Snell
  • Re: Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bullard, Claude L (Len)
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Brennan
  • Re: Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Christian Nentwich
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Rob Lugt
    • Re: Categories of Web Service messages: data-oriented vs, Mark Baker
  • Re: Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
    • RE: Categories of Web Service messages: data-oriented vs action-oriented, Miles Sabin
    • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hOra
• RE: SAF anyone?, Michael Brennan
  • RE: SAF anyone?, Jonathan Robie
  • Re: SAF anyone?, Rick Jelliffe
• Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
  • Re: Categories of Web Service messages: data-orientedvs action-oriented, Ramesh Gupta
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Kay
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Roger L. Costello
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Kay
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hOra
    • Re: Categories of Web Service messages: data-oriented vs action-oriented, Paul Prescod
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Michael Kay
      • Re: Categories of Web Service messages: data-oriented vs action-oriented, Paul Prescod
  • Re: Categories of Web Service messages: data-oriented vsaction-oriented, Mike Champion
  • Re: Categories of Web Service messages: data-oriented vs action-oriented, Mark Baker
  • Re: Categories of Web Service messages: data-oriented vs action-oriented, Andrzej Jan Taramina
    • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hOra
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hOra
  • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hOra
    • RE: Categories of Web Service messages: data-oriented vs action-oriented, Peter J. Gale
      • RE: Categories of Web Service messages: data-oriented vs action-oriented, Bill de hÓra
• Register for Open Publish 2002 today!, Elledge, Marion
• RE: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Bullard, Claude L (Len)
• RE: What am I overlooking...?, Atchley, John
  • <Possible follow-ups>
  • RE: What am I overlooking...?, Atchley, John
• RE: What am I overlooking...? (namespaces, validation, & xsv), Atchley, John
• Solving current schema problems with DSDs, Hugh Field-Richards
  • Re: Solving current schema problems with DSDs, James Clark
• SAF anyone?, Eric van der Vlist
  • Re: SAF anyone?, Jonathan Robie
• Garbage collection in DOM, Harmon, James D
• Re: misprocessing namespaces (was Re: Thereis a meaning, but it's not in the data alone), Elliotte Rusty Harold
  • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Tim Bray
    • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Rick Jelliffe
    • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Lars Marius Garshol
    • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Elliotte Rusty Harold
      • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Tim Bray
      • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), John Cowan
      • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Rick Jelliffe
      • Re: misprocessing namespaces (was Re: Thereis a meaning, but it's not in the data alone), John Cowan
      • Getting rid of entities (was: misprocessing namespaces), Lars Marius Garshol
      • Re: Getting rid of entities (was: misprocessing namespaces), Rob Lugt
      • Re: Getting rid of entities (was: misprocessing namespaces), John Cowan
      • Re: Getting rid of entities (was: misprocessing namespaces), Rick Jelliffe
      • Re: Getting rid of entities (was: misprocessing namespaces), John Cowan
      • Re: Getting rid of entities (was: misprocessing namespaces), Rick Jelliffe
      • RE: Getting rid of entities (was: misprocessing namespaces), Michael Kay
      • RE: Getting rid of entities (was: misprocessing namespaces), Sean McGrath
      • Re: Getting rid of entities (was: misprocessing namespaces), Rick Jelliffe
      • A heavier-weight proposal for character entity definition, Henry S. Thompson
      • Re: A heavier-weight proposal for character entitydefinition, Elliotte Rusty Harold
      • Re: A heavier-weight proposal for character entity definition, Henry S. Thompson
      • Re: A heavier-weight proposal for character entitydefinition, Elliotte Rusty Harold
      • Re: A heavier-weight proposal for character entity definition, John Cowan
      • Re: A heavier-weight proposal for character entity definition, Henry S. Thompson
      • Re: A heavier-weight proposal for character entity definition, Rick Jelliffe
      • Re: A heavier-weight proposal for character entitydefinition, Simon St.Laurent
      • Re: A heavier-weight proposal for character entity definition, David Carlisle
      • Re: Getting rid of entities (was: misprocessingnamespaces), Elliotte Rusty Harold
      • Re: Getting rid of entities (was: misprocessing namespaces), Rick Jelliffe
      • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Rick Jelliffe
      • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone), Marcus Carr
• looking for XML vendor in Santa Clara, Mike
• Architectural Forms: A New Generation (draft 2.1), John Cowan
  • Re: Architectural Forms: A New Generation (draft 2.1), Joe English
    • Re: Architectural Forms: A New Generation (draft 2.1), John Cowan
• "Smart ASCII" -> XML for authoring?, Mike Champion
  • RE: "Smart ASCII" -> XML for authoring?, William Rogers
  • Re: "Smart ASCII" -> XML for authoring?, Bill Lindsey
    • Re: "Smart ASCII" -> XML for authoring?, Ramesh Gupta
    • Re: "Smart ASCII" -> XML for authoring?, Rick Jelliffe
      • Re: "Smart ASCII" -> XML for authoring?, Simon St.Laurent
      • Re: "Smart ASCII" -> XML for authoring?, Trevor Croll
      • Re: "Smart ASCII" -> XML for authoring?, Mike Champion
      • Re: "Smart ASCII" -> XML for authoring?, Michael Smith
      • Re: "Smart ASCII" -> XML for authoring?, Ronald Bourret
  • Re: "Smart ASCII" -> XML for authoring?, Simon St.Laurent
  • Re: "Smart ASCII" -> XML for authoring?, Marcus Carr
  • RE: "Smart ASCII" -> XML for authoring?, Paul Brown
  • Re: "Smart ASCII" -> XML for authoring?, Michael Smith
    • Re: "Smart ASCII" -> XML for authoring?, John Cowan
      • RE: "Smart ASCII" -> XML for authoring?, Leigh Dodds
      • XML-based Wikis (was RE: "Smart ASCII" -> XML for authoring?, Mike Champion
      • RE: XML-based Wikis (was RE: "Smart ASCII" -> XML for authoring?, Bill de hÓra
      • RE: XML-based Wikis (was RE: "Smart ASCII" -> XML for authoring?, Leigh Dodds
      • Re: XML-based Wikis (was RE: "Smart ASCII" -> XML for authoring?, Eric van der Vlist
    • Re: "Smart ASCII" -> XML for authoring?, Marcus Carr
• RELAX NG, tariq abdur-rahim
  • Re: RELAX NG, Mike Champion
• Converting ASCII text to XML, Jeffrey I Condon
• RE: XML Catalog Resolvers 1.1 Released, Michael Brennan
• Architectural Forms: A New Generation (draft 2), John Cowan
• RE: PUBLIC id in notations - oops, Anderson, John
• RE: XPointer crisis, Ralph Ferris
  • <Possible follow-ups>
  • RE: XPointer crisis, Michael Brennan
  • RE: XPointer crisis, Michael Brennan
    • Re: XPointer crisis, John Cowan
  • RE: XPointer crisis, Michael Brennan
• RE: What is fast ?, Brod, Roman
  • Re: What is fast ?, Dare Obasanjo
• XML Catalog Resolvers 1.1 Released, Norman Walsh
• What is fast ?, raghavendra.ml
• RE: Press Releases, Bullard, Claude L (Len)
  • Re: Press Releases, Ronald Bourret
• What am I overlooking...?, Atchley, John
  • Re: What am I overlooking...?, Christopher R. Maden
  • RE: What am I overlooking...?, Priscilla Walmsley
  • Re: What am I overlooking...?, Richard Tobin
• XPointer crisis, David G. Durand
  • Re: XPointer crisis, Simon St.Laurent
    • Re: XPointer crisis, David G. Durand
      • Re: XPointer crisis, Christian Nentwich
      • Re: XPointer crisis, Simon St.Laurent
    • Re: XPointer crisis, Daniel Veillard
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Simon St.Laurent
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Jonathan Robie
      • Re: XPointer crisis, Simon St.Laurent
      • Re: XPointer crisis, Daniel Veillard
      • Re: XPointer crisis, Heikki Toivonen
      • Re: XPointer crisis, Daniel Veillard
      • Re: XPointer crisis, Jonathan Robie
      • Re: XPointer crisis, Daniel Veillard
      • text/xml (was Re: XPointer crisis), Simon St.Laurent
      • Re: XPointer crisis, Jonathan Robie
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Christian Nentwich
      • Re: XPointer crisis, Daniel Veillard
      • Re: XPointer crisis, Joe English
      • RE: XPointer crisis, Evan Lenz
      • Re: XPointer crisis, Joe English
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Jonathan Robie
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Joe English
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Christian Nentwich
      • Re: XPointer crisis, Joe English
      • Re: XPointer crisis, Christian Nentwich
      • Re: XPointer crisis, Joe English
  • Press Releases, Mehul Shah
    • Re: Press Releases, Mike Champion
    • Re: Press Releases, Andrzej Jan Taramina
  • Re: XPointer crisis, Mike Champion
    • Re: XPointer crisis, Simon St.Laurent
      • Re: XPointer crisis, David G. Durand
  • Re: XPointer crisis, John Cowan
    • Re: XPointer crisis, David G. Durand
  • Re: XPointer crisis, Jonathan Robie
  • RE: XPointer crisis, Michael Kay
    • Re: XPointer crisis, John Cowan
      • Re: XPointer crisis, Mike Champion
      • Re: XPointer crisis, Gavin Thomas Nicol
      • Re: XPointer crisis, Jonathan Robie
    • RE: XPointer crisis, Jonathan Robie
    • Re: XPointer crisis, Gavin Thomas Nicol
  • Re: XPointer crisis, Rick Jelliffe
    • Re: XPointer crisis, John Cowan
      • Re: XPointer crisis, Gavin Thomas Nicol
    • Re: XPointer crisis, Gavin Thomas Nicol
• what 'isa' piece of xml? was Re: Co-operating with Architectural Forms, Jonathan Borden
• RE: How to use XML and all its deratives as a tree data structure?, Nicolas LEHUEN
• Re: Namespaces in XML and schemas, Ronald Bourret
  • Re: Namespaces in XML and schemas, Jonathan Borden
  • <Possible follow-ups>
  • Re: Namespaces in XML and schemas, Laurent Therond
• Re: life support for DTDs? was RE: misprocessing namespaces), Rick Jelliffe
  • <Possible follow-ups>
  • Re: life support for DTDs? was RE: misprocessing namespaces), Ronald Bourret
    • Re: life support for DTDs? was RE: misprocessing namespaces), Rick Jelliffe
      • Re: life support for DTDs? was RE: misprocessing namespaces), Ronald Bourret
  • Re: life support for DTDs? was RE: misprocessing namespaces), Jonathan Borden
    • Re: life support for DTDs? was RE: misprocessing namespaces), james anderson
    • Re: life support for DTDs? was RE: misprocessing namespaces), Rick Jelliffe
      • Re: life support for DTDs? was RE: misprocessing namespaces), Jonathan Borden
      • XML-1.0 is dead! long live XML-1.0+Namespaced-DTD! [was Re: life support for DTDs?, james anderson
  • RE: life support for DTDs? was RE: misprocessing namespaces), Bullard, Claude L (Len)
    • Re: life support for DTDs? was RE: misprocessing namespaces), Rick Jelliffe
  • Re: life support for DTDs? was RE: misprocessing namespaces), Wayne Steele
    • Re: life support for DTDs? was RE: misprocessingnamespaces), Mike Champion
• Usage of Escape Character instead of CDATA, ReemaD
  • Re: Usage of Escape Character instead of CDATA, Paul Prescod
• RE: bioinformatics, XML, Joshua Allen
  • <Possible follow-ups>
  • Re: bioinformatics, XML, Christian Nentwich
• Re: Co-operating with Architectural Forms, Gavin Thomas Nicol
  • cooperating with XML was Re: Co-operating with Architectural Forms, Jonathan Borden
    • Re: cooperating with XML was Re: Co-operating with Architectural Forms, Jonathan Borden
    • Re: cooperating with XML was Re: Co-operating with Architectural Forms, Gavin Thomas Nicol
  • <Possible follow-ups>
  • RE: Co-operating with Architectural Forms, Sean McGrath
    • RE: Co-operating with Architectural Forms, Sean McGrath
      • Re: Co-operating with Architectural Forms, John Cowan
  • Re: Co-operating with Architectural Forms, Rick Jelliffe
  • Re: Co-operating with Architectural Forms, Ronald Bourret
  • Re: Co-operating with Architectural Forms, Ronald Bourret
  • Re: Co-operating with Architectural Forms, Ronald Bourret
    • Re: Co-operating with Architectural Forms, Sean McGrath
    • RE: Co-operating with Architectural Forms, Michael Kay
      • Re: Co-operating with Architectural Forms, Rick Jelliffe
  • Re: Co-operating with Architectural Forms, Pete Kirkham
  • Re: Co-operating with Architectural Forms, Norman Gray
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
    • RE: Co-operating with Architectural Forms, Leigh Dodds
    • RE: Co-operating with Architectural Forms, Frank Richards
      • Re: Co-operating with Architectural Forms, Rick Jelliffe
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
    • Re: Co-operating with Architectural Forms, Gavin Thomas Nicol
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
    • RE: Co-operating with Architectural Forms, Frank Richards
    • Re: RE: Co-operating with Architectural Forms, Mike Champion
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • Re: Co-operating with Architectural Forms, Bill Lindsey
    • Message not available
      • Message not available
      • Message not available
      • Re: Co-operating with Architectural Forms, Joe English
      • Re: Co-operating with Architectural Forms, Gavin Thomas Nicol
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Joshua Allen
    • RE: Co-operating with Architectural Forms, Michael Kay
  • RE: Co-operating with Architectural Forms, Joshua Allen
  • RE: Co-operating with Architectural Forms, Joshua Allen
  • Re: Co-operating with Architectural Forms, Lars Marius Garshol
  • Re: Co-operating with Architectural Forms, Lars Marius Garshol
    • Re: Co-operating with Architectural Forms, Steven R. Newcomb
      • RE: Co-operating with Architectural Forms, Michael Kay
      • Re: Co-operating with Architectural Forms, Lars Marius Garshol
    • Re: Co-operating with Architectural Forms, Joe English
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)
  • RE: Co-operating with Architectural Forms, Michael Brennan
    • RE: Co-operating with Architectural Forms, Michael Kay
  • RE: Co-operating with Architectural Forms, Bullard, Claude L (Len)