On Wed, 2005-05-18 at 23:07 +0200, Jochen Wiedmann wrote: > Daniel Barclay wrote:
<snip> > > The representation must be documented. Otherwise, how can users know > > what the representation means (e.g., how would a user know that > > null represented the content model of xs:anyType) or know what to expect > > for a given input? > > > > (That's why I have complained about the documentation--some of it is > > simply wrong, and some important behavior isn't documented.) > > > > Whatever you choose, make sure the user of your API can know what's > > supposed to happen. > > A point, that I have to admit. However, you've got to understand, that > the emphasis of all current committers is in the JaxMe core. JaxMeXS is > simply used. If you'd like to jump in, you are really welcome. But, > believe me, if I should actually find the time for writing docs again, > I'd write docs on the JaxMe core. +1 daniel - you seem knowledgeable and have an itch: why not try the apache way? you have the itch: scratch it! the API needs documenting. creating documentation is the best way to learn the API. you need to learn the API (in order to use it in your application). we're willing to check, correct and commit documentation patches if you're willing to produce them. in the usual apache fashion, if you produce good quality patches faster than the committers can review and consume them then maybe we'll have to think seriously about adding you to the team. so what's stopping you? if you really are having problems building from HEAD and that's what stopping you contributing then that's something that we're happy to help with. if it's an issue with the actual build, of course we'll fix it but we need more details of your problems. i'm surprised to hear you're having problems with JIRA. i've used JIRA on several platforms without any real issues. if we had more details we could try to replicate and then raise any issues we couldn't fix with infrastructure. but we need more details. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
