Custom Conditional Processing Attribute in DITAVAL #4510

saitejaseedella · 2024-09-11T08:49:52Z

saitejaseedella
Sep 11, 2024

I'm looking to create a custom conditional processing attribute that can be used within DITAVAL files. Currently, DITA offers predefined attributes such as product, platform, and audience, but I would like to introduce a new attribute called demo.

example_topic.dita

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "concept.dtd">
<topic id="example">
    <title>Example Topic with Phase-of-Moon Attribute</title>
    <body>
        <p demo="exampleContext">This paragraph uses the custom 'demo' attribute.</p>
    </body>
</topic>

custom.ditaval

<?xml version="1.0" encoding="UTF-8"?>
<val>
    <prop action="include" att="exampleContext"/>
</val>

Answered by raducoravu

Sep 11, 2024

@saitejaseedella your attached zip does not contain a full example + DITA OT plugin folder.
Can you pack in the zip something similar to my sample project, containing a samples folder and a complete DITA OT plugin folder?
https://github.com/oxygenxml-incubator/dita-ot-specialization-plugin-sample

View full answer

raducoravu · 2024-09-11T08:58:46Z

raducoravu
Sep 11, 2024
Collaborator

Adding a new profiling attribute means creating a DITA DTD specialization.
At some point I created a GitHub project containing a sample DITA OT specialization plugin which adds a profiling attribute, it also has links to the tutorials I followed:
https://github.com/oxygenxml-incubator/dita-ot-specialization-plugin-sample

0 replies

saitejaseedella · 2024-09-11T10:07:18Z

saitejaseedella
Sep 11, 2024
Author

@raducoravu
Thank you so much for your help! Your response and the GitHub project link were exactly what I needed. I really appreciate your support,it was exactly what I was looking for!

0 replies

saitejaseedella · 2024-09-11T11:42:09Z

saitejaseedella
Sep 11, 2024
Author

@raducoravu
Hi again, I’ve run into another issue while trying to implement the custom attributes. I was able to successfully create one attribute (demo-context), but when I try to add another attribute (demo-group), it’s not working as expected. Am I missing something?

demoContextPropsDomain.ent

<!ENTITY % demo-context-props-d-attribute 
   "demo-context 
     CDATA 
     #IMPLIED
   " 
>

<!ENTITY demo-context-props-d-att
  "a(props  demo-context)"
>

demoGroupPropsDomain.ent

<!ENTITY % demo-group-props-d-attribute 
   "demo-group 
     CDATA 
     #IMPLIED
   " 
>

<!ENTITY demo-group-props-d-att
  "a(props demo-group)"
>

topic.dita

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OXYGENXML//CUSTOM//TOPIC//EN" "topic.dtd">
<topic id="topic_odp_g1x_qj">
    <title>Topic title</title>
    <body>
        <p demo-context="123456">This is context!!!!!</p>
        <p demo-group="789">this is group!!</p>
    </body>
</topic>

topic.dtd

<?xml version="1.0" encoding="UTF-8"?>
<!-- ============================================================= -->
<!--                    HEADER                                     -->
<!-- ============================================================= -->
<!--  MODULE:    DITA Topic DTD                                    -->
<!--  VERSION:   1.2                                               -->
<!--  DATE:      November 2009                                     -->
<!--                                                               -->
<!-- ============================================================= -->

<!-- ============================================================= -->
<!--                    PUBLIC DOCUMENT TYPE DEFINITION            -->
<!--                    TYPICAL INVOCATION                         -->
<!--                                                               -->
<!--  Refer to this file by the following public identifier or an 
      appropriate system identifier 
PUBLIC "-//OASIS//DTD DITA Topic//EN"
      Delivered as file "topic.dtd"                                -->

<!-- The public ID above refers to the latest version of this DTD.
     To refer to this specific version, you may use this value:
PUBLIC "-//OASIS//DTD DITA 1.2 Topic//EN"                          -->

<!-- ============================================================= -->
<!-- SYSTEM:     Darwin Information Typing Architecture (DITA)     -->
<!--                                                               -->
<!-- PURPOSE:    DTD to describe DITA Topics                       -->
<!--                                                               -->
<!-- ORIGINAL CREATION DATE:                                       -->
<!--             March 2001                                        -->
<!--                                                               -->
<!--             (C) Copyright OASIS Open 2005, 2009.              -->
<!--             (C) Copyright IBM Corporation 2001, 2004.         -->
<!--             All Rights Reserved.                              -->
<!--                                                               -->
<!--  UPDATES:                                                     -->
<!--    2006.06.07 RDA: Added indexing domain                      -->
<!--    2006.06.21 RDA: Added props attribute extensions           -->
<!--    2007.12.01 EK:  Reformatted DTD modules for DITA 1.2       -->
<!--    2008.02.12 RDA: Modify imbeds to use specific 1.2 version  -->
<!--    2008.04.15 RDA: Added hazard domain                        -->
<!-- ============================================================= -->

<!-- ============================================================= -->
<!--                    TOPIC ENTITY DECLARATIONS                  -->
<!-- ============================================================= -->

<!-- ============================================================= -->
<!--                    DOMAIN ENTITY DECLARATIONS                 -->
<!-- ============================================================= -->


<!ENTITY % hi-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Highlight Domain//EN" 
         "../../base/dtd/highlightDomain.ent"
>%hi-d-dec;

<!ENTITY % ut-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Utilities Domain//EN" 
         "../../base/dtd/utilitiesDomain.ent"                                                
>%ut-d-dec;

<!ENTITY % indexing-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Indexing Domain//EN" 
         "../../base/dtd/indexingDomain.ent"                                                 
>%indexing-d-dec;

<!ENTITY % hazard-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Hazard Statement Domain//EN" 
         "../../base/dtd/hazardstatementDomain.ent"
>%hazard-d-dec;

<!ENTITY % abbrev-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Abbreviated Form Domain//EN" 
         "abbreviateDomain.ent"
>%abbrev-d-dec;

<!ENTITY % pr-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Programming Domain//EN" 
         "programmingDomain.ent"                                              
>%pr-d-dec;

<!ENTITY % sw-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 Software Domain//EN" 
         "softwareDomain.ent"                                                 
>%sw-d-dec;

<!ENTITY % ui-d-dec     
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 User Interface Domain//EN" 
         "uiDomain.ent"                                                       
>%ui-d-dec;

<!-- ============================================================= -->
<!--                    DOMAIN ATTRIBUTE DECLARATIONS              -->
<!-- ============================================================= -->


<!ENTITY % demo-context-props-d-dec     
  SYSTEM "demoContextPropsDomain.ent"                                                
>
%demo-context-props-d-dec;


<!ENTITY % demo-group-props-d-dec     
  SYSTEM "demoGroupPropsDomain.ent"                                                
>
%demo-group-props-d-dec;

<!-- ============================================================= -->
<!--                    DOMAIN EXTENSIONS                          -->
<!-- ============================================================= -->
<!--                    One for each extended base element, with
                        the name of the domain(s) in which the
                        extension was declared                     -->
                        

<!ENTITY % pre          "pre | 
                         %pr-d-pre; | 
                         %sw-d-pre; | 
                         %ui-d-pre;
                        ">
<!ENTITY % keyword      "keyword | 
                         %pr-d-keyword; | 
                         %sw-d-keyword; |
                         %ui-d-keyword;
                        ">
<!ENTITY % ph           "ph | 
                         %hi-d-ph; | 
                         %pr-d-ph; | 
                         %sw-d-ph; | 
                         %ui-d-ph;
                        ">
<!ENTITY % term         "term | 
                         %abbrev-d-term;
                        ">
<!ENTITY % fig          "fig |
                         %pr-d-fig; |
                         %ut-d-fig;
                        ">
<!ENTITY % dl           "dl | 
                         %pr-d-dl;
                        ">
<!ENTITY % index-base   "index-base | 
                         %indexing-d-index-base;
                        ">
<!ENTITY % note         "note | 
                         %hazard-d-note;
                        ">

<!-- ============================================================= -->
<!--                    DOMAIN ATTRIBUTE EXTENSIONS                -->
<!-- ============================================================= -->
<!ENTITY % props-attribute-extensions  
  "%demo-context-props-d-attribute;"
 >
  
<!ENTITY % props-attribute-extensions  
  "%demo-group-props-d-attribute;"
>
<!ENTITY % base-attribute-extensions   
  ""
>


<!-- ============================================================= -->
<!--                    TOPIC NESTING OVERRIDE                     -->
<!-- ============================================================= -->

<!--                    Redefine the infotype entity to exclude 
                        other topic types and disallow nesting     -->
<!ENTITY % topic-info-types 
  "topic
  "
>


<!-- ============================================================= -->
<!--                    DOMAINS ATTRIBUTE OVERRIDE                 -->
<!-- ============================================================= -->
<!--                    Must be declared ahead of the DTDs, which
                        puts @domains first in order               -->

<!ENTITY included-domains 
                          "&hi-d-att; 
                           &ut-d-att; 
                           &demo-context-props-d-att;
                           &demo-group-props-d-att;
                           &indexing-d-att;
                           &hazard-d-att;
                           &abbrev-d-att;
                           &pr-d-att; 
                           &sw-d-att;
                           &ui-d-att; 
  "
>


<!-- ============================================================= -->
<!--                    TOPIC ELEMENT INTEGRATION                  -->
<!-- ============================================================= -->

<!--                    Embed topic to get generic elements        -->
<!ENTITY % topic-type   
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Topic//EN" 
         "../../base/dtd/topic.mod"
>
%topic-type;


<!-- ============================================================= -->
<!--                    DOMAIN ELEMENT INTEGRATION                 -->
<!-- ============================================================= -->

<!ENTITY % hi-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Highlight Domain//EN" 
         "../../base/dtd/highlightDomain.mod"
>%hi-d-def;

<!ENTITY % ut-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Utilities Domain//EN" 
         "../../base/dtd/utilitiesDomain.mod"
>%ut-d-def;

<!ENTITY % indexing-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Indexing Domain//EN" 
         "../../base/dtd/indexingDomain.mod"
>%indexing-d-def;

<!ENTITY % hazard-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Hazard Statement Domain//EN" 
         "../../base/dtd/hazardstatementDomain.mod"
>%hazard-d-def;

<!ENTITY % abbrev-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Abbreviated Form Domain//EN" 
         "abbreviateDomain.mod"
>%abbrev-d-def;

<!ENTITY % ui-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 User Interface Domain//EN" 
         "uiDomain.mod"
>%ui-d-def;

<!ENTITY % pr-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Programming Domain//EN" 
         "programmingDomain.mod"
>%pr-d-def;

<!ENTITY % sw-d-def     
  PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Software Domain//EN" 
         "softwareDomain.mod"
>%sw-d-def;

<!-- ================== End DITA Topic DTD  ====================== -->

0 replies

raducoravu · 2024-09-11T11:44:47Z

raducoravu
Sep 11, 2024
Collaborator

@saitejaseedella what does "it’s not working as expected" mean? Do you have any kind of validation error reported by the publishing engine? How about if you create a zip with your entire plugin and the sample source files and maybe someone on this thread can find some time to look at it.

0 replies

saitejaseedella · 2024-09-11T11:52:24Z

saitejaseedella
Sep 11, 2024
Author

@raducoravu, what I meant by "it’s not working as expected" is that I am unable to use demo-group as a Conditional Processing Attribute.
I've attached a ZIP file containing my source code for further review.
Custom_Conditional_attributes.zip

0 replies

raducoravu · 2024-09-11T11:58:48Z

raducoravu
Sep 11, 2024
Collaborator

@saitejaseedella your attached zip does not contain a full example + DITA OT plugin folder.
Can you pack in the zip something similar to my sample project, containing a samples folder and a complete DITA OT plugin folder?
https://github.com/oxygenxml-incubator/dita-ot-specialization-plugin-sample

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DITA-OT

Custom Conditional Processing Attribute in DITAVAL #4510

{{title}}

Replies: 6 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

DITA-OT

Custom Conditional Processing Attribute in DITAVAL #4510

saitejaseedella Sep 11, 2024

Replies: 6 comments

raducoravu Sep 11, 2024 Collaborator

saitejaseedella Sep 11, 2024 Author

saitejaseedella Sep 11, 2024 Author

raducoravu Sep 11, 2024 Collaborator

saitejaseedella Sep 11, 2024 Author

raducoravu Sep 11, 2024 Collaborator

saitejaseedella
Sep 11, 2024

raducoravu
Sep 11, 2024
Collaborator

saitejaseedella
Sep 11, 2024
Author

saitejaseedella
Sep 11, 2024
Author

raducoravu
Sep 11, 2024
Collaborator

saitejaseedella
Sep 11, 2024
Author

raducoravu
Sep 11, 2024
Collaborator