http://erfurtwiki.sourceforge.net/draft-xmlplusrpc-pre00.txt

This is an initial version of a RFC for XML-RPC (or "XML+RPC"
here because of the trademark issue), and I really like to
get some early comments on it.

Initially it just was about registration of a MIME type for
XML-RPC, which by advise from IETF and w3c should become
"application/rpc+xml" somewhen (there is broad agreement that
the currently used "text/xml" is blatantly wrong). And I
guess that is what will likely come in the future, as this
is only a minor change.

I however wrote a complete RFC describing the whole protocol
(only over HTTP), which introduces some changes to the rpc
messages as well. There are no 'extensions' in this draft,
but a lot of clearifications and restrictions regarding the
message structure and syntax. And this is where I need help
and some comments. The whole thing is about allowing heavily
simplified XML-RPC implementations (without a real XML parser).

Changes to D.Winers "spec":
* clearly states charset (UTF-8, but Latin1 allowed)
* clearifies XML usage (Canonicalized XML, no namespaces, no
  comments, no CDATA, no entities, no bonus XML tags)
* changes in the transport, namely recommending compression
  (highly optional)

So what I'm asking is, if such a stronger and restricted
standard would require changes to the various existing
implementations (other than the MIME type thingi). Personally
I hope, it was adoptable without any additional effort. And
asking the Apache developers first (haven't tried, but I guess
it's again one of the better implementations), would help me
to fill the missing parts.

Possible problems I see in the current draft:
* forbids XML entities, but "<" and ">" and "&"
* forbids empty tags like <string/>

But before anybody flames me for it: this is just an initial
version, and also just a draft, and there is no reason to
feel enforced to adopt it, even if it really became a RFC
someday (which also is questionable). Or as the title simply
suggests: "request for comments".

Regards,
mario

Reply via email to