[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[
https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513216#comment-17513216
]
Andy Jefferson commented on JDO-806:
Just a question why we (currently) have XSD XMLNS for a jdo XML file as
{{http://xmlns.jcp.org/xml/ns/jdo/jdo"}}
{{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}}
{{ xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo
https://db.apache.org/jdo/xmlns/jdo_3_2.xsd; version="3.2">}}
and not
{{https://db.apache.org/jdo/xmlns/jdo"}}
{{ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"}}
{{ xsi:schemaLocation="https://db.apache.org/jdo/xmlns/jdo
https://db.apache.org/jdo/xmlns/jdo_3_2.xsd; version="3.2">}}
It seemingly makes no difference to XML validation in an IDE (e.g Eclipse), but
why burden the user with having to think where to put xmlns.jcp.org (that this
API doesn't use, nor is maintained) and where to put db.apache.org ?
For reference, Jakarta Persistence uses jakarta.ee for XMLNS as well as
xsi:schemaLocation
> Use apache URL for schemaLocation of JDO XSDs
> -
>
> Key: JDO-806
> URL: https://issues.apache.org/jira/browse/JDO-806
> Project: JDO
> Issue Type: Improvement
> Components: api
>Affects Versions: JDO 3.2
>Reporter: Michael Bouschen
>Priority: Major
> Fix For: JDO 3.3
>
>
> In JDO 3.2 the schemaLocation of JDO XSDs link to
> [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd,
> jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site
> [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that
> the 3.2 XSDs are available under this URL (see JDO-744).
> One idea ist might be to switch to an Apache URL, where we can control the
> download sites.
> This change requires corresponding changes to the specification, api, and
> tck. Here is a proposed plan to implement:
> # Update the xsds and dtds in the api/resources to change the headers.
> # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes.
> # Update the xsds and dtds in the tck with the changes. This step will fail
> without a corresponding change to the reference implementation.
> # Update the specification with the changes. A partial list of affected
> sections:
> ## 11.1.4 p. 122
> ## 18.24 p. 261
> ## 18.25 p. 265
> ## 18.26 p. 287, 298
> ## New C.23 Changes since 3.2 p. 404
> Open question: should we keep the version number of the xsd and dtd files as
> 3.2 even though the api, tck, and specification will be updated to 3.2.1? I
> would say yes, and only change the version number of the files if there is a
> change to the content of the xsd and/or dtd.
> My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version
> of the xsd and dtd.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512640#comment-17512640 ] Craig L Russell commented on JDO-806: - This question on stackoverflow seems to be relevant to our discussion: [https://stackoverflow.com/questions/8229740/xml-schema-header-namespace-config] Are we using the terminology correctly? > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512636#comment-17512636 ] Craig L Russell commented on JDO-806: - Should the headers in the xsd and dtd files change http to https? I cannot find a definitive answer to this question. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > [http://xmlns.jcp.org/xml/ns/jdo/] where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. > This change requires corresponding changes to the specification, api, and > tck. Here is a proposed plan to implement: > # Update the xsds and dtds in the api/resources to change the headers. > # Update the xsds and dtds in the db.apache.org/jdo/xmlns with the changes. > # Update the xsds and dtds in the tck with the changes. This step will fail > without a corresponding change to the reference implementation. > # Update the specification with the changes. A partial list of affected > sections: > ## 11.1.4 p. 122 > ## 18.24 p. 261 > ## 18.25 p. 265 > ## 18.26 p. 287, 298 > ## New C.23 Changes since 3.2 p. 404 > Open question: should we keep the version number of the xsd and dtd files as > 3.2 even though the api, tck, and specification will be updated to 3.2.1? I > would say yes, and only change the version number of the files if there is a > change to the content of the xsd and/or dtd. > My proposal is: the 3.2.1 version of JDO would still refer to the 3.2 version > of the xsd and dtd. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512445#comment-17512445 ] Andy Jefferson commented on JDO-806: Missing jdoconfig.xsd, jdoconfig.dtd ? > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512123#comment-17512123 ] Craig L Russell commented on JDO-806: - There is already a fairly extensive set of documentation on the jdo web site regarding metadata. The pages associated with [https://db.apache.org/jdo/metadata.html] should be updated with links to the metadata descriptions. The specification also contains many references to the dtd and xsd which need to be updated. I now think that we should update the web site, specification, api, and tck together in the next revision of jdo: 3.2.1. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512118#comment-17512118 ] Craig L Russell commented on JDO-806: - The location for the source xsd and dtd files is now in the git repository db-jdo-site/src/main/resources/other/xmlns the contents of the directory are published to [db.apache.org/jdo/xmlns|http://db.apache.org/jdo/xmlns] It would be cleaner if the source were in db-jdo-site/src/main/resources/xmlns The files also need their headers updated from: to: https://db.apache.org/jdo/xmlns/jdo_3_2.dtd;> --> > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497695#comment-17497695 ] Craig L Russell commented on JDO-806: - Proposal: use [https://db.apache.org/jdo/xmlns|https://db.apache.org/jdo/xmlns/jdo_3_2.xsd] as the location for both dtds and xsds. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.3 > > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491450#comment-17491450 ] Craig L Russell commented on JDO-806: - We could use something like [https://db.apache.org/jdo/xmlns/jdo_3_2.xsd] There is no default rendering of xsd or dtd files in browsers, but a program should be able to handle them and we should be able to figure out how to publish them. In any event, the JDO Implementation will cache the known files locally so it doesn't have to load them except possibly at workspace startup, if then. > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JDO-806) Use apache URL for schemaLocation of JDO XSDs
[ https://issues.apache.org/jira/browse/JDO-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491428#comment-17491428 ] Andy Jefferson commented on JDO-806: +1 on using an Apache URL; Jakarta specs use jakarta.ee URLs, and besides anything that removes dependencies on Oracle has always been a good thing ... > Use apache URL for schemaLocation of JDO XSDs > - > > Key: JDO-806 > URL: https://issues.apache.org/jira/browse/JDO-806 > Project: JDO > Issue Type: Improvement > Components: api >Affects Versions: JDO 3.2 >Reporter: Michael Bouschen >Priority: Major > > In JDO 3.2 the schemaLocation of JDO XSDs link to > http://xmlns.jcp.org/xml/ns/jdo/ where is one of jdo_3_2.xsd, > jdoconfig_3_2.xsd, jdoquery_3_2.xsd, orm_3_2.xsd. It seems that the site > [http://xmlns.jcp.org/xml/ns] is not updated anymore, so it is unlikely that > the 3.2 XSDs are available under this URL (see JDO-744). > One idea ist might be to switch to an Apache URL, where we can control the > download sites. -- This message was sent by Atlassian Jira (v8.20.1#820001)
