On 4/4/06, Matt Price <[EMAIL PROTECTED]> wrote: > > > Or would it have to be approved by a central committee or even OASIS > > > first? > > > > No, because it has little to do with the file format. That said, I am > > designing it with mapping to/from RDF in mind, which is the likely > > technology ODF will be using for enhanced metadata support in ODF. We > > have tentatively scheduled that for inclusion in an interim release of > > ODF early next year. > > hmm. but as I understand it a xml-ized version of a .odt document's > "library" would be saved as part of that document. Are such add-ons > permitted under the .odt spec?
Part of the reason to discuss using RDF to offer extended metadata support in ODF is precisely because it provides a predictable model for extension. So the idea is tthat by creating this new framework, we make it easy for domain-specific solutions to be plugged in, without the ODF TC having to constantly approve every little extension. I am hoping we can put enough standard structures in places so that what we add is just modest extensions to that. > I mainly ask because it seems important that .odt's be openable and > usable by Koffice & whatever other compatible suites exist. But perhaps > this is a misplaced concern. We're hoping that this framework will solve exactly these sorts of problems. In fact, if you look at the use case I wrote, it is all about facilitatiing much better interoperability. <http://wiki.oasis-open.org/office/Bibliographies_and_Citations> So I think once we solve all these problems, it ought to be easier for developers on other projects (like KOffice) to pick up and to ensure pretty decent interoperability. > > No, it's not done yet. It seems, however, in our case we can't assume > > multi-user systems, and the more common case will be single-user. > > absolutely. But if multi-user cases are possible, perhaps that shold be > worked into the data model? Yes, I meant to say that. > what do you think about trying to set some road maps for this? So that > for instance if there's a Summer of Code 2006 we can be in a position to > benefit from it? Sounds like a great idea. I'll be out of touch for much of May, so would be happy to try to finish a draft of the schema before then, and then go from there. > your rdf looks excellent. I suppose the trick now would be to translate > your ruby script into python or some otherl anguage that OOo > understands, and/or create a schema to translate from rdf to sql. BUt I > suppose also that the db definition really ought to be finalized > first... Yes. I'm playing with Rails to just understand how things would work. The Python equivalent Django might even work better, since it creates the tables from the class defintiions. I have a feeling doing the coding in OOo is quite a bit more difficult! In any case, the focus is really on expressing the model in SQL. Bruce --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
