
Dear oXygen developers, recently i got stuck with a namespace problem concerning those excellent oXygen project files. My idea was to create such files out of our authoring application. Therefore i need to know the correct namespace of those files and if available a schema to validate against. I just wonder if there is no doctype declared already. Perhaps someone can enlight me on this issue. Thanks in advance Eike -- Eike Jordan <jordan@fiz-chemie.de> | FIZ CHEMIE BERLIN | Franklin Str. 11 ------ ,__o | 10587 Berlin ------ _-\_<, | ------ (+)/'(+) | Tel. : 0049-30-39977 214

Dear Eike Jordan, The format of the <oXygen/> project files was not published. Such files are generated and parsed internally by <oXygen/>, like project files in other IDEs. We did not make a commitment for the current format so it is subject to change without notice. For example we are thinking about including in such a file also transformation scenarios, now defined only globally, at the application level. That implies changes in your authoring application that generates <oXygen/> project files. Would that be OK with you ? If you provide more details about your application and your needs related to such files we may decide to publish this format. Best regards, Sorin <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com/ Eike Jordan wrote:
Dear oXygen developers,
recently i got stuck with a namespace problem concerning those excellent oXygen project files. My idea was to create such files out of our authoring application. Therefore i need to know the correct namespace of those files and if available a schema to validate against. I just wonder if there is no doctype declared already. Perhaps someone can enlight me on this issue.
Thanks in advance Eike

Hello Sorin, Sorin Ristache wrote:
Dear Eike Jordan,
The format of the <oXygen/> project files was not published. Such files are generated and parsed internally by <oXygen/>, like project files in other IDEs. We did not make a commitment for the current format so it is subject to change without notice. For example we are thinking about including in such a file also transformation scenarios, now defined only globally, at the application level.
That sounds interesting. I've noticed such kind of feature in the XML Spy Suite an found it quite useful to be able to associate transformation scenarios to project files or project folders.
That implies changes in your authoring application that generates <oXygen/> project files. Would that be OK with you ? If you provide more details about your application and your needs related to such files we may decide to publish this format.
Our application mentioned above is based on the Apache Cocoon Publishing Framework. The content that is served by the framework is based on so called 'Valid Learning Units'; at least 4 to 10 single XML pages. If you are interested in chemical education you can find some static content at www.vs-c.de. Most of the content is in German (sorry) :-) Ok, back to the authoring part. We decided to take oXygen as our favorite XML Editor after evaluation nearly a dozen commercial and non-commercial programs. Our "first class" editors all work with oXygen. In order to make their live some more convenient we decided to offer an oXygen project download of all pages that are implied in one 'Valid Learning Unit'. In this regard it would be better to implement against a schema with an official namespace. Best regards, Eike -- Eike Jordan <jordan@fiz-chemie.de> | FIZ CHEMIE BERLIN | Franklin Str. 11 ------ ,__o | 10587 Berlin ------ _-\_<, | ------ (+)/'(+) | Tel. : 0049-30-39977 214

Dear Eike Jordan, I attached the XML Schema of the <oXygen/> project files. The sample project [oXygen-install-dir]/samples/sample.xpr is one instance document of the schema. Best regards, Sorin <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com/ Eike Jordan wrote:
Hello Sorin,
Sorin Ristache wrote:
Dear Eike Jordan,
The format of the <oXygen/> project files was not published. Such files are generated and parsed internally by <oXygen/>, like project files in other IDEs. We did not make a commitment for the current format so it is subject to change without notice. For example we are thinking about including in such a file also transformation scenarios, now defined only globally, at the application level.
That sounds interesting. I've noticed such kind of feature in the XML Spy Suite an found it quite useful to be able to associate transformation scenarios to project files or project folders.
That implies changes in your authoring application that generates <oXygen/> project files. Would that be OK with you ? If you provide more details about your application and your needs related to such files we may decide to publish this format.
Our application mentioned above is based on the Apache Cocoon Publishing Framework. The content that is served by the framework is based on so called 'Valid Learning Units'; at least 4 to 10 single XML pages. If you are interested in chemical education you can find some static content at www.vs-c.de. Most of the content is in German (sorry) :-)
Ok, back to the authoring part. We decided to take oXygen as our favorite XML Editor after evaluation nearly a dozen commercial and non-commercial programs. Our "first class" editors all work with oXygen. In order to make their live some more convenient we decided to offer an oXygen project download of all pages that are implied in one 'Valid Learning Unit'. In this regard it would be better to implement against a schema with an official namespace.
Best regards, Eike

Dear Sorin, many thanks for the grammar. I've already integrated it in our build logic. Could You also tell me which default namespace i shall use? Right now i take a self created one: 'xmlns="http://www.oxygenxml.com/schema/xpr"' which is certainly not the appropriate one :-) Sorin Ristache wrote:
Dear Eike Jordan,
I attached the XML Schema of the <oXygen/> project files. The sample project [oXygen-install-dir]/samples/sample.xpr is one instance document of the schema.
Best regards, Sorin
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com/
Best regards, Eike -- Eike Jordan <jordan@fiz-chemie.de> | FIZ CHEMIE BERLIN | Franklin Str. 11 ------ ,__o | 10587 Berlin ------ _-\_<, | ------ (+)/'(+) | Tel. : 0049-30-39977 214

Hi Eike,
Could You also tell me which default namespace i shall use? Right now i take a self created one: 'xmlns="http://www.oxygenxml.com/schema/xpr"' which is certainly not the appropriate one :-)
That is a no namespace schema so all the elements should be in no namespace. Best Regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

George Cristian Bina wrote:
Hi Eike,
Could You also tell me which default namespace i shall use? Right now i take a self created one: 'xmlns="http://www.oxygenxml.com/schema/xpr"' which is certainly not the appropriate one :-)
That is a no namespace schema so all the elements should be in no namespace.
All right, thank You George. Cheers, Eike -- Eike Jordan <jordan@fiz-chemie.de> | FIZ CHEMIE BERLIN | Franklin Str. 11 ------ ,__o | 10587 Berlin ------ _-\_<, | ------ (+)/'(+) | Tel. : 0049-30-39977 214
participants (3)
-
Eike Jordan
-
George Cristian Bina
-
Sorin Ristache