Thank you so much David! I know enough to continue on with my work. Now I'm going to ask 8 questions that I see myself asking in the future. But first, clarification on something David said.
> >* I notice that jabber:iq:auth has more than 1 colon (:). Is this only > >possible for namespaces, or can tag elements have that too (namespace > >declared like xmlns:a:b:c="name:space")? If so, how do you separate the > >element from the namespace? Is an actual element name not allowed to have > > any colons (:) in them? > > Namespaces can have more than one colon, as they are URIs. A qualified > element or attribute name can only be qualified indirectly by a prefix, > not directly by a namespace. Can there be a tag like <a:b:c xmlns:a:b="x:y"> where <c/> would inherit the namespace x:y? (From what I understood in this reply, no, but I'm just making sure.) > Yep. Well, there is some debate over whether c="" is in a namespace at > all. the names recommendation does not clarify on this point until the > appendix, which is non-normative. Long discussion. This brings up something: I noticed that jabber added <html/> in version 1.4 of the protocol (a draft protocol, according to the "Jabber Protocol Overview"). I'm guessing older clients should just have the behavior of ignoring elements they don't understand if they have enough information to do something. Does this apply to attributes as well? If <iq/> spontaneously one day gained the attribute box="", does a client ignore it or return an error? And on an error, the 500 series drops the service involved, while the 400 series merely warns and ignores? Does the stream:error ensure a complete close of the connection, no matter what? Is stream:error always followed by </stream:stream>? Can stream:error only be used for errors related with stream:stream? Other than stream:error, is there any other way of raising an error that will bring up an end to a connection? Is there ever a case where the server will send a </stream:stream> before the client? Thank you, -Kriggs RBJab _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
