How to know which schema file is declaring a global object in the documentation
This should cover W3C XML Schema, Relax NG and DTD related problems.
-
- Posts: 9
- Joined: Tue Mar 26, 2013 12:00 am
- Location: Paris, France
- Contact:
How to know which schema file is declaring a global object in the documentation
Hi,
In the schema documentation generated by Oxygen, I want to know, for each global object, in which schema file the object is documented.
Looking at the tmp documentation file generated, I don't see any possibilities for doing that.
Does any one found a solution for this question ? Are there some planes to provide the information ?
Regards, Pierre
In the schema documentation generated by Oxygen, I want to know, for each global object, in which schema file the object is documented.
Looking at the tmp documentation file generated, I don't see any possibilities for doing that.
Does any one found a solution for this question ? Are there some planes to provide the information ?
Regards, Pierre
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: How to know which schema file is declaring a global object in the documentation
Hello,
There is a setting that provides this information. In the XML Schema Documentation generation dialog look under the Settings tab in the subsection Included component details and enable the Location option.
Regards,
Adrian
There is a setting that provides this information. In the XML Schema Documentation generation dialog look under the Settings tab in the subsection Included component details and enable the Location option.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 9
- Joined: Tue Mar 26, 2013 12:00 am
- Location: Paris, France
- Contact:
Re: How to know which schema file is declaring a global object in the documentation
Adrian,
Thanks for the answer but this is not my use case.
What I want is a sole file but with each object, an indication of the file it comes from.
Looking at the tmp files it should be something like :
schemaFile and optionnally schemaFileId are the information I need.
Pierre
Thanks for the answer but this is not my use case.
What I want is a sole file but with each object, an indication of the file it comes from.
Looking at the tmp files it should be something like :
Code: Select all
...
<element id="metaCommunes">
<qname>metaCommunes</qname>
<namespace>http://modeles.fr/modeles/reference</namespace>
<schemaFile>whatever.xsd</schemaFile>
<schemaFileId>A0341</schemaFileId>
<diagram width="511" height="272">
<location>img/metaCommunes_xsd_Element_metaCommunes.jpeg</location>
<map name="metaCommunes_xsd_Element_metaCommunes">
...
Pierre
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: How to know which schema file is declaring a global object in the documentation
Well, a first step is to enable that option. Oxygen will then generate in the temporary file for each element an additional schemaLocation element that contains the absolute URL to that schema. e.g.
So you can then use the URL specified by schemaLocation. Unfortunately there is no schema file ID there.
Note that there is schema for this generated temporary file: Oxygen/frameworks/schema_documentation/xsdDocSchema.xsd
This could be helpful in better understanding the content of the temporary file.
I'm guessing you already know about the Custom output format which allows you to pick a Custom XSL under the Options button in the XML Schema Documentation dialog.
A copy of the stylesheets that Oxygen uses to publish the output is located in Oxygen/frameworks/schema_documentation/xsl: xsdDocDocbook.xsl and xsdDocHtml.xsl. For PDF the DocBook result is then processed with the regular DocBook transformation to PDF.
Regards,
Adrian
Code: Select all
<element id="personnel">
<qname>p:personnel</qname>
<namespace>http://www.oxygenxml.com/ns/samples/personal</namespace>
<schemaLocation>file:/D:/projects/eXml/samples/personal.xsd</schemaLocation>
<diagram width="425" height="521">
<location>img/personal_xsd_Element_p_personnel.png</location>
...
Note that there is schema for this generated temporary file: Oxygen/frameworks/schema_documentation/xsdDocSchema.xsd
This could be helpful in better understanding the content of the temporary file.
I'm guessing you already know about the Custom output format which allows you to pick a Custom XSL under the Options button in the XML Schema Documentation dialog.
A copy of the stylesheets that Oxygen uses to publish the output is located in Oxygen/frameworks/schema_documentation/xsl: xsdDocDocbook.xsl and xsdDocHtml.xsl. For PDF the DocBook result is then processed with the regular DocBook transformation to PDF.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 9
- Joined: Tue Mar 26, 2013 12:00 am
- Location: Paris, France
- Contact:
[SOLVED] How to know which schema file is declaring a global object in the documentation
Sorry for everything, my problem is solved : I did not saw that by default the "location" setting parameter was the only one not selected.
In the same idea, I did not understood your first answer.
Thanks for taking time ...
In the same idea, I did not understood your first answer.
Thanks for taking time ...
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service