On Wed, 20 Aug 2008 16:02:01 -0700 "Collin Grady" <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 3:58 PM, Brendan Taylor <[EMAIL PROTECTED]> > wrote: > > XEP-0108 says: > > > > In addition, the *specific* activity element can be <other/> in > > order to handle activities not defined herein. Yep, *activities not defined herein* > > I read that to mean that you can do: > > > > <activity><eating><other/></eating></activity> This syntax without 'xmlns' means <eating/> is an element that *is* defined for this particular XML namespace. If it's not, you can't do that. > > but not: > > > > <activity><other><something-else-entirely/></other></activity> > > > > Is that incorrect? I'm not fluent in XML Schema. The <something-else-entirely/> shares the same problem. > > Hmm, that's how I read that section too, looking at it - that part > might need clarified if the latter is supposed to be allowed. > <something-else xmlns="some-other-namespace"/> is the only way foreign elements should be ever included. Note: I'm talking about the XML part and didn't read the XEP at all. Pavel -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
