xml-uri@w3.org from June 2000 by date

Friday, 30 June 2000

• Re: Local Context [was: Why I moved from Forbid to Literal] W. E. Perry
• Re: Local Context [was: Why I moved from Forbid to Literal] Jonathan Borden
• Re: Why I moved from Forbid to Literal Jonathan Borden
• Local Context [was: Why I moved from Forbid to Literal] W. E. Perry
• Re: Why I moved from Forbid to Literal Paul Grosso
• Re: Why I moved from Forbid to Literal Henrik Frystyk Nielsen
• Re: Database example was: The Kesselman/Connoly proposal David Carlisle
• Re: Why I moved from Forbid to Literal David Carlisle
• Re: Database example was: The Kesselman/Connoly proposal keshlam@us.ibm.com
• Re: Database example was: The Kesselman/Connoly proposal james anderson
• Re: Database example was: The Kesselman/Connoly proposal keshlam@us.ibm.com
• Re: Why I moved from Forbid to Literal Henrik Frystyk Nielsen
• Why I moved from Forbid to Literal Simon St.Laurent
• Database example was: The Kesselman/Connoly proposal Tim Berners-Lee
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) james anderson

Thursday, 29 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Dan Connolly
• Re: namespace usage as assertions Paul Grosso
• Re: namespace usage as assertions Paul W. Abrahams
• Re: namespace usage as assertions keshlam@us.ibm.com
• Re: namespace usage as assertions John Cowan
• Re: namespace usage as assertions keshlam@us.ibm.com
• Re: namespace usage as assertions Rick JELLIFFE

Tuesday, 27 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Dan Connolly
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Henry S. Thompson
• Re: The Kesselman/Connoly proposal (was Re: Re Deprecate/Undefined ) Michael Champion

Monday, 26 June 2000

• Re: The Kesselman/Connoly proposal (was Re: Re Deprecate /Undefined ) keshlam@us.ibm.com
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) keshlam@us.ibm.com
• Background material, belated keshlam@us.ibm.com
• Re: Deprecate/Undefined (was Request for status dump and issues check) Michael Champion

Sunday, 25 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• Re: The Kesselman/Connoly proposal (was Re: Re Deprecate/Undefined ) Simon St.Laurent
• The Kesselman/Connoly proposal (was Re: Re Deprecate/Undefined ) Michael Champion
• Re: relative URIs and local lexical scopes: "Unique Base"? John Cowan
• I have a dream Tim Bray
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Tim Bray
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Tim Bray

Saturday, 24 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• Re: Can everyone be happy? Tim Berners-Lee
• relative URIs and local lexical scopes: "Unique Base"? Larry Masinter
• Re: <a:b:c> and xlink Daniel Veillard
• <a:b:c> and xlink David Carlisle
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• Re: Collect Proposed wordings (Was: Can everyone be happy?) David Carlisle

Friday, 23 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Daniel Veillard

Saturday, 24 June 2000

• Re: Re Deprecate/Undefined (was Request for status dump and issues check) James Clark
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Noah_Mendelsohn@lotus.com

Friday, 23 June 2000

• Namespaces and infosets. David G. Durand
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David G. Durand
• Another endorsement of Dan Connolly's recent proposal David G. Durand
• Re: Re Deprecate/Undefined (was Request for status dump andissues check) John Cowan
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) John Cowan
• Re: Collect Proposed wordings (Was: Can everyone be happy?) John Cowan
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Paul Grosso
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) John Cowan
• Re: Can everyone be happy? David Carlisle
• Re: Collect Proposed wordings (Was: Can everyone be happy?) David Carlisle
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Paul W. Abrahams
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) keshlam@us.ibm.com
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) keshlam@us.ibm.com
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David G. Durand
• RE: namespace usage as assertions David G. Durand
• Re: Collect Proposed wordings (Was: Can everyone be happy?) John Cowan
• RE: namespace usage as assertions keshlam@us.ibm.com
• RE: namespace usage as assertions Miles Sabin
• RE: namespace usage as assertions keshlam@us.ibm.com
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Paul W. Abrahams
• Re: Collect Proposed wordings (Was: Can everyone be happy?) David G. Durand
• Re: namespace usage as assertions james anderson
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Dan Connolly
• Re: Can everyone be happy? Tim Berners-Lee
• Re: vocabularies was: Re: Can everyone be happy? Simon St.Laurent
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Simon St.Laurent
• Re: vocabularies was: Re: Can everyone be happy? Simon St.Laurent
• Re: Can everyone be happy? Henrik Frystyk Nielsen
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Henrik Frystyk Nielsen
• Re: For literals: why I changed my mind keshlam@us.ibm.com
• Re: For literals: why I changed my mind Paul W. Abrahams
• Re: Can everyone be happy? keshlam@us.ibm.com
• Re: Can everyone be happy? keshlam@us.ibm.com

Thursday, 22 June 2000

• Re: Can everyone be happy? Henrik Frystyk Nielsen
• Re: Collect Proposed wordings (Was: Can everyone be happy?) keshlam@us.ibm.com
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Paul W. Abrahams
• Re: Can everyone be happy? Paul W. Abrahams
• Re: For literals: why I changed my mind keshlam@us.ibm.com
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Henrik Frystyk Nielsen
• Re: vocabularies was: Re: Can everyone be happy? Eric Bohlman
• Thank you Dan David G. Durand
• Re: Language = Namespace. was: How namespace names might be used David G. Durand
• Re: Can everyone be happy? David G. Durand
• Re: Collect Proposed wordings (Was: Can everyone be happy?) David G. Durand
• Re: Can everyone be happy? keshlam@us.ibm.com
• Re: vocabularies was: Re: Can everyone be happy? John Cowan
• Re: Can everyone be happy? John Cowan
• Re: vocabularies was: Re: Can everyone be happy? Simon St.Laurent
• vocabularies was: Re: Can everyone be happy? Jonathan Borden
• Re: We need some function f Paul Grosso
• Re: Can everyone be happy? Sam Hunting
• Re: what about XPath? was: Can everyone be happy? Al Gilman
• Re: Can everyone be happy? Dan Connolly
• Re: Can everyone be happy? Henrik Frystyk Nielsen
• Re: Fixed base keshlam@us.ibm.com
• Re: Collect Proposed wordings (Was: Can everyone be happy?) Simon St.Laurent
• Collect Proposed wordings (Was: Can everyone be happy?) Henrik Frystyk Nielsen
• Re: Language = Namespace. was: How namespace names might be used David G. Durand
• Re: namespace usage as assertions David G. Durand
• RE: namespace usage as assertions Larry Masinter
• Re: Can everyone be happy? Simon St.Laurent
• Re: Can everyone be happy? John Cowan
• Re: Can everyone be happy? keshlam@us.ibm.com
• RE: Fixed base Julian Reschke
• Re: Fixed base Liam Quin
• Re: Fixed base keshlam@us.ibm.com
• Re: Can everyone be happy? keshlam@us.ibm.com
• Re: Can everyone be happy? Paul W. Abrahams
• Re: what about XPath? was: Can everyone be happy? keshlam@us.ibm.com
• what about XPath? was: Can everyone be happy? Julian Reschke
• Re: Can everyone be happy? Jonathan Borden
• Re: Can everyone be happy? W. E. Perry
• Re: Can everyone be happy? Tim Berners-Lee
• Re: Fixed base Liam Quin
• Re: Can everyone be happy? David Carlisle
• Re: Language = Namespace. was: How namespace names might be used Simon St.Laurent
• Re: Infererence by scheme (Re: namespace usage as assertions) Simon St.Laurent

Wednesday, 21 June 2000

• Tar and feathers for me Simon St.Laurent
• Can everyone be happy? Paul W. Abrahams
• Re: Language = Namespace. was: How namespace names might be used David Carlisle
• Re: Infererence by scheme (Re: namespace usage as assertions) David Carlisle
• We need some function f David Carlisle
• Re: Infererence by scheme (Re: namespace usage as assertions) Dan Connolly
• Does every URI identify a resource? (Was:Re: namespace usage as assertions) Paul W. Abrahams
• Re: namespace usage as assertions Tim Berners-Lee
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: Language = Namespace. was: How namespace names might be used Paul Grosso
• Re: namespace usage as assertions Dan Connolly
• Re: Language = Namespace. was: How namespace names might be used John Cowan
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: namespace usage as assertions John Cowan
• Re: namespace usage as assertions Eve L. Maler
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: namespace usage as assertions John Cowan
• Re: namespace usage as assertions John Cowan
• Re: namespace usage as assertions David Carlisle
• Re: Language = Namespace. was: How namespace names might be used David Carlisle
• Re: namespace usage as assertions Eve L. Maler
• Decentralization (was Re: Choose your namespace (Was : Personal view)) Simon St.Laurent
• Re: namespace usage as assertions Rick JELLIFFE
• Re: namespace usage as assertions Tim Bray
• Re: namespace usage as assertions Dan Connolly
• Re: namespace usage as assertions Eve L. Maler
• Infererence by scheme (Re: namespace usage as assertions) Simon St.Laurent
• Re: namespace usage as assertions Dan Connolly
• Re: Language = Namespace. was: How namespace names might be used Graham Klyne
• RE: namespace usage as assertions Miles Sabin
• namespace usage as assertions Manola,Frank A.
• RE: The tail shouldn't wag the dog Stefan Eissing
• Re: Language = Namespace. was: How namespace names might be used John Aldridge
• no flexibility in using looser comparison in RFC 2557 Larry Masinter
• Re: Fixed base James Clark
• Re: Fixed base James Clark
• The tail shouldn't wag the dog Paul W. Abrahams

Tuesday, 20 June 2000

• RE: Choose your namespace (Was : Personal view) Andrew Layman
• Re: Fixed base David Carlisle
• Re: Choose your namespace (Was : Personal view) David Carlisle
• Re: Fixed base David Carlisle
• Re: Language = Namespace. was: How namespace names might be used Simon St.Laurent
• Re: Fixed base John Cowan
• Re: Fixed base David G. Durand
• Re: Choose your namespace (Was : Personal view) John Cowan
• Re: Fixed base John Cowan
• RE: Choose your namespace (Was : Personal view) David G. Durand
• Re: Rehash of literal-vs-relative argument status David G. Durand
• Re: Fixed base John Cowan
• Re: Fixed base Dan Connolly
• Re: Rehash of literal-vs-relative argument status John Cowan
• Re: Choose your namespace (Was : Personal view) David G. Durand
• Re: Choose your namespace (Was : Personal view) John Aldridge
• Re: Fixed base David G. Durand
• Re: Language = Namespace. was: How namespace names might be used Graham Klyne
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• RE: Choose your namespace (Was : Personal view) Andrew Layman
• Re: Rehash of literal-vs-relative argument status David G. Durand
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• Re: Language = Namespace. was: How namespace names might be used Dan Connolly
• Re: Language = Namespace. was: How namespace names might be used Henrik Frystyk Nielsen
• Re: Choose your namespace (Was : Personal view) Paul W. Abrahams
• Re: Language = Namespace. was: How namespace names might be used Paul W. Abrahams
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: Language = Namespace. was: How namespace names might be used Dan Connolly
• Re: Choose your namespace (Was : Personal view) Graham Klyne
• Re: Choose your namespace (Was : Personal view) Liam Quin
• Re: Language = Namespace. was: How namespace names might be used John Aldridge
• Re: Fixed base Daniel Veillard
• Re: Choose your namespace (Was : Personal view) Daniel Veillard
• RE: Language = Namespace. was: How namespace names might be used Julian Reschke
• Re: A proposed solution Daniel Veillard
• Re: A proposed solution Simon St.Laurent
• Fixed base James Clark
• Re: Language = Namespace. was: How namespace names might be used Dan Connolly
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• Re: Choose your namespace (Was : Personal view) Paul W. Abrahams
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen

Monday, 19 June 2000

• Re: Language = Namespace. was: How namespace names might be used Tim Bray
• Re: Choose your namespace (Was : Personal view) David Carlisle
• Worth repeating Tim Bray
• Re: Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• Rehash of literal-vs-relative argument status Tim Berners-Lee
• Re: Language = Namespace. was: How namespace names might be used Paul W. Abrahams
• Re: A proposed solution Henrik Frystyk Nielsen
• RE: Language = Namespace. was: How namespace names might be used Julian Reschke
• Re: For literals: why I changed my mind Paul W. Abrahams
• Re: Choose your namespace (Was : Personal view) Paul W. Abrahams
• Re: For literals: why I changed my mind David Carlisle
• Re: Language = Namespace. was: How namespace names might be used David Carlisle
• Re: Choose your namespace (Was : Personal view) David G. Durand
• Re: Language = Namespace. was: How namespace names might be used David G. Durand
• RE: Language = Namespace. was: How namespace names might be used Eric Bohlman
• Re: Language = Namespace. was: How namespace names might be used Paul W. Abrahams
• For literals: why I changed my mind Paul W. Abrahams
• Re: Choose your namespace (Was : Personal view) David Carlisle
• (no subject) David G. Durand
• Choose your namespace (Was : Personal view) Henrik Frystyk Nielsen
• RE: Language = Namespace. was: How namespace names might be used Julian Reschke
• Language = Namespace. was: How namespace names might be used Tim Berners-Lee
• Re: David Carlisle
• Re: A proposed solution David Carlisle
• Re: Tim Berners-Lee
• Re: How namespace names might be used Paul W. Abrahams
• Re: How namespace names might be used John Cowan
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: 1343 messages later Tim Berners-Lee

Sunday, 18 June 2000

• Re: Personal view David Carlisle
• Re: A proposed solution David Carlisle
• RE: Personal view Larry Masinter
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: Personal view Daniel Veillard
• Re: Personal view Daniel Veillard
• Re: A proposed solution David Carlisle
• Re: Personal view David Carlisle
• Re: A proposed solution Henrik Frystyk Nielsen
• RE: Personal view Larry Masinter
• Re: 1343 messages later Henrik Frystyk Nielsen

Saturday, 17 June 2000

• Differentiating literal and forbid (Re: Personal view) Simon St.Laurent
• Re: Personal view David Carlisle
• RE: essential test cases? Don Park
• Re: How namespace names might be used Paul W. Abrahams
• Re: Personal view Tim Bray
• Re: How namespace names might be used Simon St.Laurent
• Re: How namespace names might be used Al Gilman
• Re: How namespace names might be used Al Gilman
• Re: Personal view Simon St.Laurent
• Personal view Daniel Veillard

Friday, 16 June 2000

• Re: How namespace names might be used Paul W. Abrahams
• Private address spaces and URIs Simon St.Laurent
• Re: How namespace names might be used Simon St.Laurent
• Fwd: Re: How namespace names might be used John Aldridge
• Re: How namespace names might be used Al Gilman
• Re: How namespace names might be used John Aldridge

Thursday, 15 June 2000

• Re: No more tangents (Was: A proposed solution) David Carlisle
• (no subject) keshlam@us.ibm.com
• No more tangents (Was: A proposed solution) Clark C. Evans
• Re: A proposed solution Tim Berners-Lee
• RE: Is file:///foo a URI? Larry Masinter
• RE: A proposed solution Simon St.Laurent
• RE: A proposed solution Larry Masinter
• Re: Context and... Re: the case of two bats Simon St.Laurent
• Re: Context and... Re: the case of two bats Tim Berners-Lee
• Oops (was RE: A proposed solution) Simon St.Laurent
• RE: A proposed solution Simon St.Laurent
• Re: essential test cases? Ray Whitmer
• Re: Layering XPath/XSLT namespaces is unacceptable Clark C. Evans
• RE: A proposed solution Larry Masinter
• Re: 1343 messages later keshlam@us.ibm.com
• Re: Is file:///foo a URI? keshlam@us.ibm.com
• Re: Layering XPath/XSLT namespaces is unacceptable Michael Champion
• Re: A proposed solution Paul W. Abrahams
• Re: Layering XPath/XSLT namespaces is unacceptable keshlam@us.ibm.com
• Re: some uses of relative URI as namespace names keshlam@us.ibm.com
• Re: 1343 messages later Al Gilman
• Re: A proposed solution Simon St.Laurent
• Re: Context and... Re: the case of two bats keshlam@us.ibm.com
• Re: 1343 messages later Daniel Veillard
• Re: 1343 messages later Paul W. Abrahams
• Re: Layering XPath/XSLT namespaces is unacceptable Al Gilman
• Re: A proposed solution Paul W. Abrahams
• Is file:///foo a URI? Graham Klyne
• Re: essential test cases? Paul W. Abrahams
• Re: 1343 messages later keshlam@us.ibm.com
• Re: Tim Berners-Lee
• Re: Layering XPath/XSLT namespaces is unacceptable keshlam@us.ibm.com
• Re: essential test cases? keshlam@us.ibm.com
• Documents, Anchors, Nodes and Context was: RE: Context and... Re: the case of two bats Jonathan Borden
• Re: essential test cases? Simon St.Laurent
• Re: essential test cases? keshlam@us.ibm.com
• Re: jettisoning baggage Simon St.Laurent
• Re: 1343 messages later John Cowan
• Personal view John Aldridge
• Re: 1343 messages later James Clark
• Re: A proposed solution James Clark
• Re: A proposed solution James Clark
• Re: essential test cases? James Clark
• Re: Layering XPath/XSLT namespaces is unacceptable James Clark
• Re: essential test cases? James Clark
• Re: Context and... Re: the case of two bats Paul W. Abrahams
• Re: jettisoning baggage Al Gilman
• Re: Layering XPath/XSLT namespaces is unacceptable Al Gilman
• Re: Context and... Re: the case of two bats Al Gilman
• Re: Context and... Re: the case of two bats Paul W. Abrahams
• Re: jettisoning baggage Paul W. Abrahams
• jettisoning baggage Simon St.Laurent

Wednesday, 14 June 2000

• Re: Context and... Re: the case of two bats David Carlisle
• Re: Context and... Re: the case of two bats Jonathan Borden
• RE: Banning relative - No real damage? Michael Rys
• Re: Context and... Re: the case of two bats Paul W. Abrahams
• Re: essential test cases? Paul W. Abrahams
• Re: The "deprecate/fixed-base" option David G. Durand
• Re: Layering XPath/XSLT namespaces is unacceptable Michael Champion
• In praise of fixed base was: Layering XPath/XSLT namespaces is unacceptable David Carlisle
• Re: Layering XPath/XSLT namespaces is unacceptable David G. Durand
• Re: The "deprecate/fixed-base" option David Carlisle
• Re: Context and... Re: the case of two bats Tim Berners-Lee
• Re: Layering XPath/XSLT namespaces is unacceptable Tim Berners-Lee
• Re: 1343 messages later Dan Brickley
• Re: Banning relative - No real damage? Tim Berners-Lee
• Re: Layering XPath/XSLT namespaces is unacceptable Al Gilman
• Re: Attribute uniqueness test: a radical proposal Simon St.Laurent
• Re: Attribute uniqueness test: a radical proposal keshlam@us.ibm.com
• Re: 1343 messages later John Cowan
• Re: 1343 messages later Tim Berners-Lee
• RE: essential test cases? keshlam@us.ibm.com
• Re: Attribute uniqueness test: a radical proposal Sam Hunting
• Re: Layering XPath/XSLT namespaces is unacceptable Michael Champion
• RE: essential test cases? Julian Reschke
• Re: Attribute uniqueness test: a radical proposal Tim Berners-Lee
• Re: Layering XPath/XSLT namespaces is unacceptable Al Gilman
• Re: 1343 messages later Paul W. Abrahams
• Re: 1343 messages later Al Gilman
• Re: 1343 messages later keshlam@us.ibm.com
• RE: essential test cases? Al Gilman
• Re: The "deprecate/fixed-base" option Tim Berners-Lee
• Re: essential test cases? keshlam@us.ibm.com
• Re: essential test cases? keshlam@us.ibm.com
• RE: essential test cases? Julian Reschke
• Layering XPath/XSLT namespaces is unacceptable Michael Champion
• Re: essential test cases? Simon St.Laurent
• Re: essential test cases? Dan Connolly
• Re: 1343 messages later Graham Klyne
• Re: 1343 messages later Al Gilman
• Context and... Re: the case of two bats Jonathan Borden
• Re: 1343 messages later Jonathan Borden
• Re: How namespace names might be used David Carlisle
• Re: 1343 messages later David Carlisle
• Re: 1343 messages later John Cowan

Tuesday, 13 June 2000

• Re: 1343 messages later Simon St.Laurent
• Re: 1343 messages later Simon St.Laurent
• Re: 1343 messages later Tim Berners-Lee
• Re: How namespace names might be used Dan Connolly
• Re: Minimum required of a system called "Namespaces in XML" Paul W. Abrahams
• Re: A proposed solution Paul W. Abrahams
• Re: How namespace names might be used David Carlisle
• Re: essential test cases? David Carlisle
• some uses of relative URI as namespace names David Carlisle
• Re: essential test cases? Simon St.Laurent
• Re: How namespace names might be used Al Gilman
• RE: essential test cases? Julian Reschke
• essential test cases? Dan Connolly
• Re: How namespace names might be used W. E. Perry
• Re: PUBLIC/SYSTEM distinction (was Re: typo/bug in the namespace spec) keshlam@us.ibm.com
• Re: How namespace names might be used Al Gilman
• Re: How namespace names might be used Simon St.Laurent
• Re: How namespace names might be used Al Gilman
• Re: How namespace names might be used W. E. Perry
• Implied best practices (was Re: How namespace names might be used) Simon St.Laurent
• Re: How namespace names might be used Dan Connolly
• Re: Is a namesapce a resource? - was: duck keshlam@us.ibm.com
• Re: How namespace names might be used Graham Klyne
• Re: Annotation protocols [was: How namespace names might be used] Tim Bray

Monday, 12 June 2000

• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: XML Base and XPath absolutizing of URIs David Carlisle
• Re: Is a namesapce a resource? - was: duck David Carlisle
• 1343 messages later Simon St.Laurent
• RE: How namespace names might be used Simon St.Laurent
• RE: How namespace names might be used keshlam@us.ibm.com
• RE: How namespace names might be used Jelks Cabaniss
• Spinning off interesting heresies (was Re: How are semantics named?) Simon St.Laurent
• Re: How are semantics named? keshlam@us.ibm.com
• Re: Annotation protocols [was: How namespace names might be used] Tim Berners-Lee
• Re: Annotation protocols [was: How namespace names might be used] Simon St.Laurent
• Annotation protocols [was: How namespace names might be used] Tim Berners-Lee
• Re: How are semantics named? Simon St.Laurent
• How are semantics named? Tim Bray
• Re: Minimum required of a system called "Namespaces in XML" Tim Bray
• Re: Minimum required of a system called "Namespaces in XML" keshlam@us.ibm.com
• Re: Is a namesapce a resource? - was: duck james anderson
• Re: Michael Mealling
• Re: Minimum required of a system called "Namespaces in XML" Simon St.Laurent
• Re: Minimum required of a system called "Namespaces in XML" Michael Mealling
• Re: Minimum required of a system called "Namespaces in XML" keshlam@us.ibm.com
• (no subject) keshlam@us.ibm.com
• (no subject) keshlam@us.ibm.com
• Re: Is a namesapce a resource? - was: duck keshlam@us.ibm.com

Sunday, 11 June 2000

• Re: PUBLIC/SYSTEM distinction (was Re: typo/bug in the namespace spec) Simon St.Laurent
• Re: How namespace names might be used Tim Bray
• What would be cool... (CONNEG vs. discovery) Simon St.Laurent
• Re: How namespace names might be used Clark C. Evans
• PUBLIC/SYSTEM distinction (was Re: typo/bug in the namespace spec) Simon St.Laurent
• Re: How namespace names might be used Michael Mealling
• Re: typo/bug in the namespace spec Michael Mealling
• Re: How namespace names might be used Simon St.Laurent
• Re: typo/bug in the namespace spec Simon St.Laurent
• Re: How namespace names might be used David Carlisle
• Re: How namespace names might be used Eric Bohlman
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: How namespace names might be used John Cowan
• Re: How namespace names might be used Michael Mealling
• Re: A proposed solution John Cowan
• Re: How namespace names might be used Eric Bohlman
• Closure (was Re: typo/bug in the namespace spec) Michael Champion

Saturday, 10 June 2000

• Re: typo/bug in the namespace spec Henrik Frystyk Nielsen
• Re: typo/bug in the namespace spec David Carlisle
• Re: How namespace names might be used Henrik Frystyk Nielsen
• How namespace names might be used Tim Bray
• More nervousness about NS Names bearing semantics Tim Bray
• Re: typo/bug in the namespace spec Tim Bray
• Re: A proposed solution David Carlisle
• RE: A proposed solution Larry Masinter
• Re: A proposed solution David Carlisle
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution Clark C. Evans
• Re: A proposed solution David Carlisle
• Re: A proposed solution James Clark
• Re: A proposed solution Simon St.Laurent
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution John Cowan
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: A proposed solution Henrik Frystyk Nielsen

Friday, 9 June 2000

• Re: A proposed solution David Carlisle
• RE: Is a namesapce a resource? - was: duck Michael Rys
• Re: A proposed solution John Cowan
• Re: A proposed solution (base edge cases) Dan Connolly
• FW: D. Carlisle lone user (was : Microsoft tools) James O. Luke
• Re: Uncertainty on xml-dev David Carlisle
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: A proposed solution Simon St.Laurent
• Re: Is a namesapce a resource? - was: duck John Cowan
• Re: A proposed solution John Cowan
• Re: A proposed solution Jonathan Borden
• Re: A proposed solution Simon St.Laurent
• Re: Is a namesapce a resource? - was: duck keshlam@us.ibm.com
• Re: A proposed solution Al Gilman
• Re: A proposed solution David Carlisle
• Re: Literal Approach + Locality Warning (Was: A proposed solution Henrik Frystyk Nielsen
• Literal Approach + Locality Warning (Was: A proposed solution Clark C. Evans
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: A proposed solution Henrik Frystyk Nielsen
• Re: Divide the problem John Cowan
• Re: Is a namespace [always] a [shared] resource? Clark C. Evans
• Re: Divide the problem David G. Durand
• Re: A proposed solution Henrik Frystyk Nielsen
• OID URN namespace.... Michael Mealling
• Re: Divide the problem John Cowan
• Re: Divide the problem David G. Durand
• Re: On, and on, and on... Al Gilman
• Re: Is a namespace [always] a [shared] resource? Al Gilman
• Re: Compromise?: absolutize but require xml:base keshlam@us.ibm.com
• Re: Is a namespace [always] a [shared] resource? keshlam@us.ibm.com
• Re: Is a namespace [always] a [shared] resource? Al Gilman
• RE: Divide the problem Julian Reschke
• Re: Uncertainty on xml-dev james anderson

Thursday, 8 June 2000

• Re: On, and on, and on... Graham Klyne

Friday, 9 June 2000

• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Compromise?: absolutize but require xml:base Simon St.Laurent
• Compromise?: absolutize but require xml:base Jonathan Borden
• Re: Uncertainty on xml-dev Al Gilman
• RE: XML Base and XPath absolutizing of URIs John Boyer
• RE: Banning relative - No real damage? Michael Rys
• Re: A proposed solution Jonathan Borden

Thursday, 8 June 2000

• Re: XML Base and XPath absolutizing of URIs Jonathan Borden
• Re: A proposed solution Paul Grosso
• RE: XML Base and XPath absolutizing of URIs John Boyer
• Re: A proposed solution Jonathan Borden
• Re: XML Base and XPath absolutizing of URIs Donald E. Eastlake 3rd
• Re: A proposed solution Paul Grosso
• Re: A proposed solution Frystyk
• Re: Divide the problem Dan Connolly
• Re: XML Base and XPath absolutizing of URIs Paul Grosso
• Re: rel:foo for those who can't do without 'relative' URIs Jonathan Borden
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: A proposed solution Jonathan Borden
• Re: Is a namesapce a resource? - was: duck keshlam@us.ibm.com
• XML Base and XPath absolutizing of URIs John Boyer
• Re: A proposed solution Dan Connolly
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: A proposed solution David Carlisle
• Microsoft tools David Carlisle
• Re: Standards vs. Recs (was RE: Divide the problem) Eric Bohlman
• Standards vs. Recs (was RE: Divide the problem) Simon St.Laurent
• Re: Is a namesapce a resource? - was: duck keshlam@us.ibm.com
• RE: Making the namespace resource "real" Julian Reschke
• RE: Divide the problem Julian Reschke
• RE: Divide the problem keshlam@us.ibm.com
• RE: Making the namespace resource "real" keshlam@us.ibm.com
• Re: On, and on, and on... David Carlisle
• Re: Making the namespace resource "real" David Carlisle
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• Re: Uncertainty on xml-dev David Carlisle
• RE: Making the namespace resource "real" Julian Reschke
• RE: Divide the problem Julian Reschke
• A proposed solution David Turner
• Making the namespace resource "real" Clark C. Evans
• Re: Uncertainty on xml-dev keshlam@us.ibm.com
• Re: On, and on, and on... Simon St.Laurent
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) keshlam@us.ibm.com
• Re: Uncertainty on xml-dev John Aldridge
• RE: Mechanism, not policy [was: Attribute uniqueness...] keshlam@us.ibm.com
• Re: On, and on, and on... was: Mechanism, not policy [was: Attribute uniqueness...] Dan Connolly
• Re: The "deprecate/fixed-base" option David Carlisle
• Re: Uncertainty on xml-dev David Carlisle
• Re: Reasons to use namespaces David Carlisle
• Re: typo/bug in the namespace spec? [was: Mechanism, not policy...] David Carlisle
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) David Carlisle
• RE: Mechanism, not policy [was: Attribute uniqueness...] David Hunter
• Re: Re Deprecate/Undefined (was Request for status dump and issues check) Paul Grosso
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Divide the problem David Carlisle
• Re: Uncertainty on xml-dev james anderson
• RE: Mechanism, not policy [was: Attribute uniqueness...] Simon St.Laurent
• RE: Mechanism, not policy [was: Attribute uniqueness...] keshlam@us.ibm.com
• Re: On, and on, and on... was: Mechanism, not policy [was: Attribute uniqueness...] John Cowan
• Re: Is a namesapce a resource? - was: duck Graham Klyne
• Reasons to use namespaces Graham Klyne
• Re: Request for status dump and issues check keshlam@us.ibm.com
• Re: On, and on, and on... was: Mechanism, not policy [was: Attribute uniqueness...] keshlam@us.ibm.com
• typo/bug in the namespace spec? [was: Mechanism, not policy...] Dan Connolly
• Re: Uncertainty on xml-dev Al Gilman
• Re Deprecate/Undefined (was Request for status dump and issues check) keshlam@us.ibm.com
• Re: The "deprecate/fixed-base" option Clark C. Evans
• On, and on, and on... was: Mechanism, not policy [was: Attribute uniqueness...] David G. Durand
• Re: Uncertainty on xml-dev keshlam@us.ibm.com
• Re: The "deprecate/fixed-base" option keshlam@us.ibm.com
• Re: Is a namesapce a resource? - was: duck Dan Connolly
• Re: Divide the problem Simon St.Laurent
• RE: Mechanism, not policy [was: Attribute uniqueness...] David Hunter
• RE: Divide the problem David Hunter
• Re: Divide the problem Dan Connolly
• RE: Is a namesapce a resource? - was: duck Bill dehOra
• RE: Mechanism, not policy [was: Attribute uniqueness...] Julian Reschke
• Uncertainty on xml-dev John Cowan
• RE: Divide the problem Julian Reschke
• Re: Divide the problem Dan Connolly
• RE: Mechanism, not policy [was: Attribute uniqueness...] Julian Reschke
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Is a namesapce a resource? - was: duck Graham Klyne
• Re: The "deprecate/fixed-base" option David Carlisle
• Divide the problem Julian Reschke
• Re: The "deprecate/fixed-base" option David Carlisle
• RE: Mechanism, not policy [was: Attribute uniqueness...] Julian Reschke
• Re: Request for status dump and issues check David Carlisle
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• General concerns (was Re: Request for status dump...) Simon St.Laurent
• Re: Mechanism, not policy [was: Attribute uniqueness...] Tim Berners-Lee
• Re: Mechanism, not policy [was: Attribute uniqueness...] Tim Berners-Lee
• Re: rel:foo for those who can't do without 'relative' URIs Tim Berners-Lee
• Re: Request for status dump and issues check Tim Berners-Lee
• Re: rel:foo for those who can't do without 'relative' URIs Tim Berners-Lee
• Re: The "deprecate/fixed-base" option Michael Mealling

Wednesday, 7 June 2000

• The "deprecate/fixed-base" option John Cowan
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• href="foo" David Carlisle
• Re: Mechanism, not policy [was: Attribute uniqueness...] Dan Connolly
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Mechanism, not policy [was: Attribute uniqueness...] Dan Connolly
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• Re: Attribute uniqueness test: a radical proposal keshlam@us.ibm.com
• Re: Mechanism, not policy [was: Attribute uniqueness...] keshlam@us.ibm.com
• Re: Mechanism, not policy [was: Attribute uniqueness...] Dan Connolly
• RE: The 'resource' identified by a namespace name URI should be the namespace Julian Reschke
• Re: Is a namesapce a resource? - was: duck Rick JELLIFFE
• Re: Attribute uniqueness test: a radical proposal Tim Berners-Lee
• Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans
• Re: Banning relative - No real damage? David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: Mechanism, not policy [was: Attribute uniqueness...] David Carlisle
• Re: Banning relative - No real damage? Al Gilman
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee
• Mechanism, not policy [was: Attribute uniqueness...] Dan Connolly
• Re: Moving on (was Re: URIs quack like a duck) Rick JELLIFFE
• Re: Banning relative - No real damage? keshlam@us.ibm.com
• Re: Banning relative - No real damage? David Carlisle
• Re: Banning relative - No real damage? David Carlisle
• Re: Banning relative - No real damage? Simon St.Laurent
• Re: Banning relative - No real damage? keshlam@us.ibm.com
• Re: Banning relative - No real damage? John Cowan
• RE: rel:foo for those who can't do without 'relative' URIs Jonathan Borden
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: on relative URI references David Carlisle
• Re: Attribute uniqueness test: a radical proposal Al Gilman
• Re: The 'resource' identified by a namespace name URI should be the namespace keshlam@us.ibm.com
• Re: Banning relative - No real damage? keshlam@us.ibm.com
• Re: rel:foo for those who can't do without 'relative' URIs keshlam@us.ibm.com
• Re: A new proposal (was: Re: which layer for URI processing?) keshlam@us.ibm.com
• Re: Attribute uniqueness test: a radical proposal keshlam@us.ibm.com
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Re: The 'resource' identified by a namespace name URI should be the namespace Graham Klyne
• Re: Banning relative - No real damage? David Carlisle
• well-structured? was: RE: what "huge problem" with XML Base? [was: red/green XML] Jonathan Borden
• rel:foo for those who can't do without 'relative' URIs Jonathan Borden
• Re: Banning relative - No real damage? John Cowan
• Re: Banning relative - No real damage? Tim Bray

Tuesday, 6 June 2000

• Re: The 'resource' identified by a namespace name URI should be the namespace Paul W. Abrahams
• Re: Banning relative - No real damage? David Carlisle
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• RE: The 'resource' identified by a namespace name URI should be the namespace Julian Reschke
• New text for Namespaces 2.0 Paul W. Abrahams
• Re: The 'resource' identified by a namespace name URI should be the namespace Paul W. Abrahams
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: Is a namesapce a resource? - was: duck John Cowan
• Re: on relative URI references David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace Paul W. Abrahams
• Re: what "huge problem" with XML Base? [was: red/green XML] Jonathan Borden
• Re: how does XML Base affects well-formedness? [was: red/green XML] Paul Grosso
• Re: Minimum required of a system called "Namespaces in XML" David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: what "huge problem" with XML Base? [was: red/green XML] John Cowan
• Re: what "huge problem" with XML Base? [was: red/green XML] Jonathan Borden
• Re: what "huge problem" with XML Base? [was: red/green XML] Jonathan Borden
• Re: Is a namesapce a resource? - was: duck David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) keshlam@us.ibm.com
• Re: how does XML Base affects well-formedness? [was: red/green XML] keshlam@us.ibm.com
• Re: The 'resource' identified by a namespace name URI should be the namespace Paul W. Abrahams
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Simon St.Laurent
• Re: Minimum required of a system called "Namespaces in XML" Paul W. Abrahams
• Re: what "huge problem" with XML Base? [was: red/green XML] Paul Grosso
• Re: Moving on (was Re: URIs quack like a duck) Simon St.Laurent
• Re: what "huge problem" with XML Base? [was: red/green XML] Eric van der Vlist
• how does XML Base affects well-formedness? [was: red/green XML] Paul Grosso
• what "huge problem" with XML Base? [was: red/green XML] Paul Grosso
• RE: Philosphy 101 Larry Masinter
• Re: Is a namespace a resource? - was: duck John Cowan
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee
• Re: on relative URI references Tim Berners-Lee
• Re: Is a namespace a resource? - was: duck Al Gilman
• Re: red/green XML keshlam@us.ibm.com
• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Is a namesapce a resource? - was: duck Tim Berners-Lee
• Re: red/green XML Tim Berners-Lee
• RE: Banning relative - No real damage? Julian Reschke
• Re: Banning relative - No real damage? David Carlisle
• RE: Philosphy 101 Bill dehOra
• Re: RFC 2557 (MHTML) uses byte-equality after absolutizing Simon St.Laurent
• RFC 2557 (MHTML) uses byte-equality after absolutizing Larry Masinter
• Re: Banning relative - No real damage? Sam Hunting
• Yet Another Modest Proposal: [was] Minimum required of a system called "Namespaces in XML" Sam Hunting

Monday, 5 June 2000

• Re: Banning relative - No real damage? David Carlisle
• Re: Request for status dump and issues check David Carlisle
• Re: Request for status dump and issues check David Carlisle
• Re: Minimum required of a system called "Namespaces in XML" David Carlisle
• Re: Minimum required of a system called "Namespaces in XML" David Carlisle
• Banning relative - No real damage? Tim Berners-Lee
• Re: Philosphy 101 Al Gilman
• Re: Request for status dump and issues check Michael Mealling
• Re: Request for status dump and issues check John Cowan
• Re: Request for status dump and issues check keshlam@us.ibm.com
• Re: Request for status dump and issues check Simon St.Laurent
• Re: Request for status dump and issues check keshlam@us.ibm.com
• Re: Request for status dump and issues check Michael Mealling
• Re: Minimum required of a system called "Namespaces in XML" John Cowan
• Re: Request for status dump and issues check John Cowan
• RE: Request for status dump and issues check Larry Masinter
• Re: Minimum required of a system called "Namespaces in XML" Graham Klyne
• Re: Minimum required of a system called "Namespaces in XML" Michael Mealling
• Request for status dump and issues check keshlam@us.ibm.com
• Re: Philosphy 101 Liam Quin
• Re: The 'resource' identified by a namespace name URI should be the namespace Dan Brickley
• Re: Philosphy 101 John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Re: Minimum required of a system called "Namespaces in XML" David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace Dan Brickley
• Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Philosphy 101 Larry Masinter
• Re: URIs quack like a duck Michael Mealling
• Re: URIs quack like a duck John Cowan
• Re: stepping backward (one more step) John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: Minimum required of a system called "Namespaces in XML" Michael Mealling
• Re: stepping backward (one more step) Graham Klyne
• Re: URIs quack like a duck Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: URIs quack like a duck Michael Mealling
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: URIs quack like a duck Michael Mealling
• Re: URIs quack like a duck Michael Mealling
• Re: stepping backward (one more step) John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge
• Re: stepping backward (one more step) Graham Klyne
• Re: URIs quack like a duck Graham Klyne
• Re: The 'resource' identified by a namespace name URI should be the namespace Graham Klyne
• RE: The 'resource' identified by a namespace name URI should be the namespace Graham Klyne
• Re: The 'resource' identified by a namespace name URI should be the namespace John Aldridge

Sunday, 4 June 2000

• Re: URIs quack like a duck Paul W. Abrahams
• Minimum required of a system called "Namespaces in XML" David Carlisle
• Re: Namespaces aside, absolutizing is none of _X_Path's business Simon St.Laurent
• Re: Namespaces aside, absolutizing is none of _X_Path's business Clark C. Evans
• Re: URIs quack like a duck Clark C. Evans
• Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans

Friday, 4 June 100

• Re: URIs quack like a duck John Cowan

Sunday, 4 June 2000

• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans
• Re: URIs quack like a duck Clark C. Evans
• Re: URIs quack like a duck Dan Brickley

Friday, 4 June 100

• Re: Namespaces aside, absolutizing is none of _X_Path's business John Cowan

Sunday, 4 June 2000

• Re: URIs quack like a duck Michael Mealling
• Namespaces aside, absolutizing is none of _X_Path's business Al Gilman

Friday, 4 June 100

• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: URIs quack like a duck John Cowan

Saturday, 3 June 2000

• Re: URIs quack like a duck David Carlisle
• Re: fundamental difference? W. E. Perry
• Re: a clarification? David Carlisle
• Re: URIs quack like a duck David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: on relative URI references David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• red/green XML Jonathan Borden
• Re: layering is consistent and coherent Clark C. Evans
• Re: Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Al Gilman
• Re: stepping backward (one more step) Al Gilman
• Re: Chaos, Process Sam Hunting
• Re: URIs quack like a duck Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace Dan Brickley

Thursday, 3 June 100

• Re: URIs quack like a duck John Cowan

Saturday, 3 June 2000

• Re: layering is consistent and coherent Al Gilman

Thursday, 3 June 100

• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan

Saturday, 3 June 2000

• Namespaces and XML 2.0 (Was: XML 1.0 in flux) Paul W. Abrahams
• Re: layering is consistent and coherent Clark C. Evans
• Re: XML 1.0 in flux Sam Hunting
• layering is consistent and coherent Al Gilman
• Common Sense! Was: Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans
• Re: stepping backward Sam Hunting
• Who cares if URI1=URI2 (Was: URIs quack like a duck) Paul W. Abrahams
• Re: a clarification? Tim Berners-Lee
• Re: fundamental difference? Simon St.Laurent
• RE: The 'resource' identified by a namespace name URI should be the namespace Larry Masinter
• Re: The 'resource' identified by a namespace name URI should be the namespace Liam Quin
• Re: namespaces include their name => 1-1 Tim Berners-Lee
• Re: URIs quack like a duck Tim Berners-Lee
• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee

Thursday, 3 June 100

• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan

Saturday, 3 June 2000

• Re: fundamental difference? Tim Berners-Lee
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee

Thursday, 3 June 100

• Re: Injective Quality (Was: Re: URIs quack like a duck) John Cowan

Saturday, 3 June 2000

• Re: on relative URI references Tim Berners-Lee

Thursday, 3 June 100

• Re: Moving on (was Re: URIs quack like a duck) John Cowan
• Re: Moving on (was Re: URIs quack like a duck) John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: URIs quack like a duck John Cowan

Saturday, 3 June 2000

• Re: Injective Quality (Was: Re: URIs quack like a duck) Tim Berners-Lee

Thursday, 3 June 100

• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan

Saturday, 3 June 2000

• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Re: URIs quack like a duck Paul W. Abrahams
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee
• Re: XML 1.0 in flux Simon St.Laurent
• fundamental differences? (again) (was The 'resource') Simon St.Laurent
• fundamental difference? Simon St.Laurent
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee
• Re: XML 1.0 in flux Paul W. Abrahams
• Re: The 'resource' identified by a namespace name URI should be the namespace Tim Berners-Lee
• RE: The 'resource' identified by a namespace name URI should be the namespace Larry Masinter
• Re: Namespace-by-retrieval is consistent and coherent Tim Berners-Lee
• Re: Chaos, Process Tim Berners-Lee
• Re: Base-less fears (was Moving On...) Tim Berners-Lee

Thursday, 3 June 100

• Re: URIs quack like a duck John Cowan

Friday, 2 June 2000

• Re: URIs quack like a duck Paul W. Abrahams
• Re: URIs quack like a duck Paul W. Abrahams
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: Moving on (was Re: URIs quack like a duck) John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Can we get past these @#X! axioms? Simon St.Laurent
• Re: a personal conclusion..... Simon St.Laurent
• Re: a personal conclusion..... Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: a personal conclusion..... Simon St.Laurent
• a personal conclusion..... Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: Terminology John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: stepping backward John Cowan
• Re: stepping backward John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Terminology Clark C. Evans
• Re: defaulting namespace attributes with relative URI references Simon St.Laurent
• Re: stepping backward Simon St.Laurent
• Re: namespaces include their name => 1-1 David Carlisle
• Re: defaulting namespace attributes with relative URI references David Carlisle
• Re: stepping backward Sam Hunting
• Re: stepping backward Simon St.Laurent
• Re: stepping backward Sam Hunting
• XML 1.0 in flux Simon St.Laurent
• stepping backward Simon St.Laurent
• Re: Chaos, Process Sam Hunting
• on relative URI references David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Chaos, Process Sam Hunting
• Re: "data:,<name>" proposal adds an extra level John Cowan
• Re: Moving on (was Re: URIs quack like a duck) Simon St.Laurent
• Re: namespaces include their name => 1-1 John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: Moving on (was Re: URIs quack like a duck) John Cowan
• Re: Injective Quality (Was: Re: URIs quack like a duck) John Cowan
• "data:,<name>" proposal adds an extra level Larry Masinter
• namespaces include their name => 1-1 Larry Masinter
• defaulting namespace attributes with relative URI references Simon St.Laurent
• Re: Moving on (was Re: URIs quack like a duck) Simon St.Laurent
• Re: Chaos, Process Simon St.Laurent
• Re: Moving on (was Re: URIs quack like a duck) John Cowan
• Re: Chaos, Process Dan Connolly
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: Chaos, Process Sam Hunting
• Re: Ray Whitmer
• Re: Moving on (was Re: URIs quack like a duck) Al Gilman
• Re: Injective Quality (Was: Re: URIs quack like a duck) Tim Berners-Lee
• RE: Moving on (was Re: URIs quack like a duck) Jonathan Borden
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) Simon St.Laurent
• Re: Chaos, Process Simon St.Laurent
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• YAMP: ns-attr is a _mark_, not a _name_ for the namespace Al Gilman

Wednesday, 2 June 100

• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the John Cowan

Friday, 2 June 2000

• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans

Thursday, 1 June 2000

• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans
• Base-less fears (was Moving On...) Jonathan Marsh
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: Injective Quality (Was: Re: URIs quack like a duck) David Carlisle
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: The 'resource' identified by a namespace name URI should be the namespace Al Gilman
• Re: The 'resource' identified by a namespace name URI should be the namespace John Cowan
• Re: John Cowan
• Re: Namespace names: a modification of a semi-serious proposal John Cowan
• Re: The 'resource' identified by a namespace name URI should be the namespace Michael Mealling
• Re: Tim Berners-Lee
• Re: Chaos, Process Tim Berners-Lee
• Re: Moving on (was Re: URIs quack like a duck) Tim Berners-Lee
• Re: Namespace names: a modification of a semi-serious proposal Tim Berners-Lee
• Re: The 'resource' identified by a namespace name URI should be the namespace Clark C. Evans
• Re: The 'resource' identified by a namespace name URI should be the namespace Simon St.Laurent
• Re: The 'resource' identified by a namespace name URI should be the namespace David Carlisle
• Re: Injective Quality (Was: Re: URIs quack like a duck) Tim Berners-Lee
• The 'resource' identified by a namespace name URI should be the namespace Larry Masinter
• Re: URIs quack like a duck Simon St.Laurent
• RE: URIs quack like a duck Arnold, Curt
• Re: URIs quack like a duck David Carlisle
• Re: URIs quack like a duck John Cowan
• Re: Namespace names: a modification of a semi-serious proposal Paul W. Abrahams
• Re: URIs quack like a duck Paul W. Abrahams
• Re: Namespace names: a modification of a semi-serious proposal Tim Berners-Lee
• Re: a clarification? David Carlisle
• Re: URIs quack like a duck David Carlisle
• Re: URIs quack like a duck Paul W. Abrahams
• Re: URIs quack like a duck W. E. Perry
• Re: URIs quack like a duck John Cowan
• Re: URIs quack like a duck Paul W. Abrahams
• Re: Moving on (was Re: URIs quack like a duck) Paul W. Abrahams
• Re: a clarification? Paul W. Abrahams
• Re: URIs quack like a duck Paul W. Abrahams
• Re: a clarification? John Cowan
• Re: a clarification? David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) Michael Mealling
• Re: URIs quack like a duck David Carlisle
• a clarification? Michael Mealling
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: URIs quack like a duck John Cowan
• Re: Moving on (was Re: URIs quack like a duck) Paul W. Abrahams
• Re: Moving on (was Re: URIs quack like a duck) Michael Mealling
• Re: URIs quack like a duck Paul W. Abrahams
• Re: Moving on (was Re: URIs quack like a duck) Michael Mealling
• Re: URIs quack like a duck Michael Mealling
• Re: URIs quack like a duck Michael Mealling
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) Paul W. Abrahams
• Re: URIs quack like a duck David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) Michael Mealling
• Re: Moving on (was Re: URIs quack like a duck) Paul W. Abrahams
• Re: Moving on (was Re: URIs quack like a duck) Michael Mealling
• Re: URIs quack like a duck Paul W. Abrahams
• Comparing URI references as strings David Carlisle

Wednesday, 31 May 2000

• Re: Injective Quality (Was: Re: URIs quack like a duck) Graham Klyne

Thursday, 1 June 2000

• Re: RDF/XML/Internet Collisons, Process (was Moving on) Graham Klyne
• RE: Moving on (was Re: URIs quack like a duck) Julian Reschke
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: Moving on (was Re: URIs quack like a duck) David Carlisle
• Re: URIs quack like a duck David Carlisle
• Re: URIs quack like a duck David Carlisle
• Re: Attribute uniqueness test: a radical proposal David Carlisle
• Re: Namespace-by-retrieval is consistent and coherent David Carlisle

Last message date: Friday, 30 June 2000 19:18:59 UTC