Generating reuse components
Post here questions and problems related to editing and publishing DITA content.
Generating reuse components
Post by anonymous1 »
Hello,
I am trying to generate reuse components for our migration to Oxygen and I have the following questions:
I am trying to generate reuse components for our migration to Oxygen and I have the following questions:
- What is the most generic DTD declaration for my reusable components? I do not know what I will generate a priori, so I'd rather be permissive.
- Is it possible to create a conref linking to the ComponentDefinition element, so that I can automatically get the whole content of my reusable component directly or do I have to create a range attribute and assign an id to each child of ComponentDefinition?]
Last edited by anonymous1 on Tue May 31, 2016 5:06 pm, edited 1 time in total.
-
- Posts: 9446
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Generating reuse components
Hi Arthur,
Please see some answers below:
Also I would suggest using content key references instead of key references.
My DITA Reuse Strategies blog post should have more details about how to best reuse:
http://blog.oxygenxml.com/2015/11/dita- ... orial.html
Regards,
Radu
Please see some answers below:
Our special "Create Reusable Component" action (which I think you are using) creates a small DTD specialization directly in the DITA content which refers to the original DOCTYPE of the topic from which the element came from. Usually reusable elements should be placed in plain topics (with the topic DTD public IDs).What is the most generic DTD declaration for my reusable components? I do not know what I will generate a priori, so I'd rather be permissive.
Our specific "Create Reusable Component" action can only save one component per file. It's mostly indented for beginners. Usually when reusing content in a DITA project you can create your own DITA topic which has inside it various elements which can be reused. You can have a table which on the first column contains in each cell a reused element and on the second column has a small description for that element, description which is used by the tech writer to find out more about where the element should be used (like some kind of metadata).[*]Is it possible to create a conref linking to the ComponentDefinition element, so that I can automatically get the whole content of my reusable component directly or do I have to create a range attribute and assign an id to each child of ComponentDefinition?
Also I would suggest using content key references instead of key references.
My DITA Reuse Strategies blog post should have more details about how to best reuse:
http://blog.oxygenxml.com/2015/11/dita- ... orial.html
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Re: Generating reuse components
Post by anonymous1 »
Hi Radu,
Thank you for your answer. I didn't clearly specify that I'm generating these reusable component on my own, not using Oxygen.
I guess I'll create basic topics instead to hold my reusable contents though. Thank you for the pointer.
Thank you for your answer. I didn't clearly specify that I'm generating these reusable component on my own, not using Oxygen.
I guess I'll create basic topics instead to hold my reusable contents though. Thank you for the pointer.
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ 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