Re: [bdbxml] Developing a local (Swing) front-end
"Mark R. Diggory" <mdiggory-Mahy8Y1M33PaZwrp7/[email protected]>
| Newsgroups | gmane.comp.db.dbxml.general |
|---|---|
| Message-ID | <[email protected]> |
SF account: mdiggory I have no allegiance as I've never attended classes here (however, my wife does). Hey at least they have a great benefits package ;-) I'm employed by Harvard as a software developer on a digital library project that is built on open source technology. (Thus my interest in BDBXML) We have allot of "large" XML instances to manage. Just to give you an idea, I have several current projects I work on 1.) Harvard MIT Data Center: http://www.thedata.org 2.) World Bank: http://www.internationalsurveynetwork.org/home/ 3.) Apache Commons: http://jakarta.apache.org/commons/math 4.) eXist (contributor): http://exist.sf.net Cheers, Mark Tom McCubbin wrote: > Just a small note. I'm looking fwd to working w/ you all...the comments > and insights have been great. I can guarantee quality server side code, > and look forward to a good schooling on the practical XML side of > things. Make sure you send your sf acct info to webhiker if interested... > > -tom > > ps - Mark, i studied finance at Wharton, and we typically belittled > Harvard guys...but that's just because we were jealous! And that was a > long time ago... > > Mark R. Diggory wrote: > >> >> >> Philipp Suter wrote: >> >>> Here is a quote from an email of the abovely mentioned discussion: >>> "One thing you might want to ponder on before you get started, and >>> which a quick perusal of the spec might not make immediately >>> apparent, is that Xml:DB is based on nestable Collections. >>> At fiest glance, the XmlContainer maps quite nicely onto Xml:DB >>> Collections, however, unlike Sleepycat, in which all containers are >>> flat, Xml:DB allows Collections to contain other Collections as well >>> as XML documents. >> >> >> >> The nice thing here is that Collections are optional in XMLDB Core 0. >> You can get away without them initially and just treat the container >> as one common collection. >> >>> This might make translating the XQUery or XPath statements a bit more >>> tricky, since one needs to traverse child collections when evaluating >>> the expressions. >> >> >> >> An initial implementation as one common collection avoids this until a >> collection strategy can be designed/developed. >> >>> But perhaps you can use the metadata storage capabilities of Sleepcat >>> to store this info about relationships between Collections. " >>> >> >> Yes, and later, if further collection information can be aggregated in >> the metadata of a Resource, theres possibly a means to approach the >> idea of the collection through some sort of merging of XQueries >> against that metadata information. However, if there were a means to >> reorganize the structure of BDBXML so that it supported Collection >> hierarchies intrinsically in the organization of its datastore, then >> that would be a very powerful feature thats already present in many >> Native XML databases, sounds like something that I would want in >> BDBXML as a feature even at the level of the BDBXML api. >> >> ... >> >>>> I'll get the server done by weeks end i hope... >>>> >>>> My last ? is what platform people would want a pkg for. I'm doing >>>> the dev work on linux x86, but also have a sparc solaris >>>> workstation, and windoze machines...feedback from those interested >>>> in testing... >>> >>> >>> >>> >>> I could test on windows and os x if anybody is interested in os x. >>> packaging is only possible for os x, I do not have any packaging >>> tools for windows. >>> >> >> RHEL, Fedora, rpm packaging would be great to have on these systems. >> >> -Mark >> >> >> ------------------------------------------ >> To remove yourself from this list, send an >> email to [email protected] > > > > > > ------------------------------------------ > To remove yourself from this list, send an > email to [email protected] > ------------------------------------------ To remove yourself from this list, send an email to [email protected]