You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michael Bouschen <mb...@spree.de> on 2005/09/12 23:26:06 UTC
dtd and xsd files in api20
Hi Craig,
today the api20 project includes jdo.dtd, jdo.xsd, orm.dtd defining the
structure of metadata files.Should we add an orm.xsd?
The spec allows JDOQL queries to be defined in .jdoquery metadata files.
Their structure uses a subset of the metadata elements of the .jdo and
.orm files. Would it make sense to add a separate dtd for .jdoquery
files: jdoquery.dtd (and a .jdoquery.xsd)? I think it defines just a few
elements: a new root element jdoquery, package, class, interface and
query. Elements package, class and interface only define the name
attribute; class and interface only have query and extension subelements.
Regards Michael
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: dtd and xsd files in api20
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
thanks! I can forward the .jdoquery question to the JDO expert group.
Regards Michael
> Hi Michael,
>
> On Sep 12, 2005, at 2:26 PM, Michael Bouschen wrote:
>
>> Hi Craig,
>>
>> today the api20 project includes jdo.dtd, jdo.xsd, orm.dtd defining
>> the structure of metadata files.Should we add an orm.xsd?
>
>
> Yes, the omission was an oversight on my part.
>
>>
>> The spec allows JDOQL queries to be defined in .jdoquery metadata
>> files. Their structure uses a subset of the metadata elements of the
>> .jdo and .orm files. Would it make sense to add a separate dtd for
>> .jdoquery files: jdoquery.dtd (and a .jdoquery.xsd)? I think it
>> defines just a few elements: a new root element jdoquery, package,
>> class, interface and query. Elements package, class and interface
>> only define the name attribute; class and interface only have query
>> and extension subelements.
>
>
> Yes. I'll need to run this past the expert group. But I agree with the
> concept.
>
> Thanks,
>
> Craig
>
>>
>> Regards Michael
>>
>> --
>> Michael Bouschen Tech@Spree Engineering GmbH
>> mailto:mbo.tech@spree.de http://www.tech.spree.de/
>> Tel.:++49/30/235 520-33 Buelowstr. 66
>> Fax.:++49/30/2175 2012 D-10783 Berlin
>>
>>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: dtd and xsd files in api20
Posted by Craig Russell <Cr...@Sun.COM>.
Hi Michael,
On Sep 12, 2005, at 2:26 PM, Michael Bouschen wrote:
> Hi Craig,
>
> today the api20 project includes jdo.dtd, jdo.xsd, orm.dtd defining
> the structure of metadata files.Should we add an orm.xsd?
Yes, the omission was an oversight on my part.
>
> The spec allows JDOQL queries to be defined in .jdoquery metadata
> files. Their structure uses a subset of the metadata elements of
> the .jdo and .orm files. Would it make sense to add a separate dtd
> for .jdoquery files: jdoquery.dtd (and a .jdoquery.xsd)? I think it
> defines just a few elements: a new root element jdoquery, package,
> class, interface and query. Elements package, class and interface
> only define the name attribute; class and interface only have query
> and extension subelements.
Yes. I'll need to run this past the expert group. But I agree with
the concept.
Thanks,
Craig
>
> Regards Michael
>
> --
> Michael Bouschen Tech@Spree Engineering GmbH
> mailto:mbo.tech@spree.de http://www.tech.spree.de/
> Tel.:++49/30/235 520-33 Buelowstr. 66
> Fax.:++49/30/2175 2012 D-10783 Berlin
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!