[IMPORTANT] questions for xsd and dtd file changes
Hi, These questions need immediate answers: 1. Should we plan for a release 3.2.1 and create a new branch for 3.2.1 (both db-jdo and db-jdo-site) for issue JDO-806? 2. Should we use 3.2 as the xsd and dtd version numbers since there are no changes planned for them in 3.2.1? 3. Should we use https in the xsd and dtd headers? 4. Should we fix the typo in the date of the specification on the front page? My proposal is yes, yes, yes, and yes. Craig Craig L Russell javadog@gmail.com 1220 University Ave San Jose, CA 95126
[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] [Updated] (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:all-tabpanel ] Craig L Russell updated JDO-806: Description: 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. was: 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. > 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)
Re: xmlns does not include jdoconfig xsd and dtd
Hi Craig, no, I think this is an oversight. So both files jdoconfig_3_2.xsd and jdoconfig_3_2.dtd should be available in the xmlns directory Regards Michael Hi, Is there a reason to not include jdoconfig definitions in the xmlns directory? Regards, Craig Craig L Russell javadog@gmail.com 1220 University Ave San Jose, CA 95126