1
|
- Noah Mendelsohn
- IBM Research
- March 3, 2003
|
2
|
- Goal of this talk: alert non
XML-core WGs to need to start building an interoperable stack in an XML
1.1 world.
- Non-goals:
- Promote or deprecate use of XML 1.1 in particular situations or
recommendations
- Debate W3C process: did right
reviews happen prior to 1.1 rec?
|
3
|
|
4
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
12
|
|
13
|
|
14
|
|
15
|
|
16
|
- How do you know which Infosets allow new names/chars?
- application/xml (RFC 3203) needs clarification
(informal discussions started)
- SOAP is based on RFC 3203…did not explicitly anticipate new
content…affects interoperation
- Even old-style content may be labeled as
<?xml version=“1.1”?>.
- Streaming large documents complicates early generation of <?xml
version=“1.x”?>
- Not clear whether query can easily check for new content when
serializing
- XML interop story compromised:
already deployed software can’t read even old-style content
- WSDL?, RDF? Probably others?
- I may not have the list right, but there clearly are a lot of
interrelated issues to consider.
|
17
|
- XML 1.1 seems to affect many Recommendations, RFC’s, etc.
- We need to get busy figuring out the implications
- My opinion: we need a stack that is consistent and that preserves the
nearly universal interoperability that has made XML compelling for
users.
|