David,
David Faure wrote:
> Indeed the presence of db-java-classpath in the standard is problematic.
>
> Michael, can you add this item to the "Proposals under discussion" in the wiki?
Sure.
If have discussed this with Frank, and we actually believe it would be
best to remove the entire attribute, because it is application if not
even system specific. Instead, and application setting should be used.
Michael
>
> On Tuesday 24 June 2008, you wrote:
>> Hello, again.
>> As you can see below I am referring to (very old) Frank's post. In 2005 we've
>> worked on adding connection-data related elements to ODF 1.2 and the effect
>> was very positive to me.
>> At the time I criticized inclusion of java-dependent elements in the database
>> parts of the ODF specs, that is now at the 1.2 draft 7 stage.
>>
>> Please take a look:
>>
>> Frank Schönheit - Sun Microsystems Germany said the following, On 2005-06-29
>> 16:30:
>>> For instance, the java-driver-class is a driver-setting (which to me
>>> also seemed to be a misunderstanding in [1]): The component which serves
>>> “jdbc:” URLs (basically translating JDBC interfaces to OOo's API), uses
>>> this setting to determine the Java class to load. For all other URI
>>> schemes, and thus all other external database types, the attribute is
>>> completely useless. Thus, it probably should have been in a
>>>