software elements in machinery task
Oxygen general issues.
-
- Posts: 1
- Joined: Wed Mar 26, 2025 5:17 pm
software elements in machinery task
Hello,
How can I use Software elements (cmdname, filepath, etc.) in a machinery task? I tried adding the SW domains in the machineryTask.dtd template, but it doesn't work, please see below and thanks fo answer:
These parts were added into the machineryTask.dtd:
How can I use Software elements (cmdname, filepath, etc.) in a machinery task? I tried adding the SW domains in the machineryTask.dtd template, but it doesn't work, please see below and thanks fo answer:
These parts were added into the machineryTask.dtd:
Code: Select all
<!ENTITY % taskreq-d-dec
PUBLIC "-//OASIS//ENTITIES DITA 1.3 Task Requirements Domain//EN"
"../../technicalContent/dtd/softwareDomain.ent"
>%taskreq-d-dec;
DOMAIN EXTENSIONS
<!ENTITY % ph "ph |
%sw-d-ph; |
<!ENTITY % keyword "keyword |
%sw-d-keyword; |
DOMAINS ATTRIBUTE OVERRIDE
<!ENTITY included-domains
&sw-d-att;
DOMAIN ELEMENT INTEGRATION
<!ENTITY % taskreq-d-def
PUBLIC "-//OASIS//ENTITIES DITA 1.3 Task Requirements Domain//EN"
"../../technicalContent/dtd/softwareDomain.mod"
>%taskreq-d-def;
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: software elements in machinery task
Hi,
The machinery task as per the base DITA 1.3 specification does not allow these elements inside it.
So ideally you would need to build a DITA DTD specialization probably to accomplish what you want:
https://www.oxygenxml.com/doc/versions/ ... ation.html
Your specialization DTDs would have their own DOCTYPE public and system IDs to differentiate between the base DTDs and the specialized ones.
About the specifics of building this specialization, I'm not sure, one would need to try and probably as you attempted find some entities from the machinery task DTDs which need to be overwritten and made more lax.
Regards,
Radu
The machinery task as per the base DITA 1.3 specification does not allow these elements inside it.
So ideally you would need to build a DITA DTD specialization probably to accomplish what you want:
https://www.oxygenxml.com/doc/versions/ ... ation.html
Your specialization DTDs would have their own DOCTYPE public and system IDs to differentiate between the base DTDs and the specialized ones.
About the specifics of building this specialization, I'm not sure, one would need to try and probably as you attempted find some entities from the machinery task DTDs which need to be overwritten and made more lax.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
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