Date   

Re: table entry attributes

ekimber@contrext.com
 

The xtrf, xtrc, dita-ot:x and dita-ot:y attributes are added during preprocessing.

Of these, dita-ot:x and dita-ot:y are specific to table entries (they represent the final x/y position of the cell in the table as rendered, taking into account any row or column spanning).

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 10/22/20, 4:11 PM, "scott ashmead via groups.io" <main@dita-users.groups.io on behalf of scott_ashmead=yahoo.com@groups.io> wrote:

Hi All?

When I use DITA-OT I see the following attributes on my <entry> element in the XML output. Does anyone understand how or why they end up there? I don't see them on the input XML.

Thank you very much!
Scott

<entry align="center"
class="- topic/entry "
xtrf="Renewal_Change_Form_SO.dita"
xtrc="entry:8;128:47"
colname="col2"
dita-ot:x="2"
dita-ot:y="2">


table entry attributes

scott ashmead
 

Hi All?

When I use DITA-OT I see the following attributes on my <entry> element in the XML output. Does anyone understand how or why they end up there? I don't see them on the input XML.

Thank you very much!
Scott

                           <entry align="center"
                                  class="- topic/entry "
                                  xtrf="Renewal_Change_Form_SO.dita"
                                  xtrc="entry:8;128:47"
                                  colname="col2"
                                  dita-ot:x="2"
                                  dita-ot:y="2">



Re: filtering <othermeta>

Dan Vint
 

I just looked at my last test and I'm getting only single values. Something else is going on and I need to review the set of ditaval files.

Thanks



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: dvint <dvint@...>
Date: 10/22/20 12:16 PM (GMT-08:00)
To: main@dita-users.groups.io, "Melissa Kershes via groups.io" <sarala557@...>
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

Thanks for alternative ideas, but I'm really trying to understand why I'm not getting the correct result with the markup. Seems to me there is only one value that should appear, but I'm getting multiples in the content. 

Initially I read Melissa's response as being something that happens out of the box and didn't realize she was talking about a customization. I typically don't use build manifests, so I thought it might be something different in the two approaches. 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Jay Sadler <jay.sadler@...>
Date: 10/22/20 11:53 AM (GMT-08:00)
To: "Melissa Kershes via groups.io" <sarala557@...>, main@dita-users.groups.io
Subject: Re: [dita-users] filtering <othermeta>

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.

From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Re: filtering <othermeta>

Dan Vint
 

Thanks for alternative ideas, but I'm really trying to understand why I'm not getting the correct result with the markup. Seems to me there is only one value that should appear, but I'm getting multiples in the content. 

Initially I read Melissa's response as being something that happens out of the box and didn't realize she was talking about a customization. I typically don't use build manifests, so I thought it might be something different in the two approaches. 



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Jay Sadler <jay.sadler@...>
Date: 10/22/20 11:53 AM (GMT-08:00)
To: "Melissa Kershes via groups.io" <sarala557@...>, main@dita-users.groups.io
Subject: Re: [dita-users] filtering <othermeta>

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.

From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Re: filtering <othermeta>

Jay Sadler
 

Ixiasoft also can give you a custom ant task to copy the original (Ixiasoft) name of the ditaval instead of a ditaval file based on the source ditamap name. Create a target in your conductor to use this custom task if you need a copy in your output.


From: main@dita-users.groups.io <main@dita-users.groups.io> on behalf of Melissa Kershes via groups.io <sarala557@...>
Sent: Wednesday, October 21, 2020 6:27
To: main@dita-users.groups.io <main@dita-users.groups.io>
Subject: Re: [dita-users] filtering <othermeta>
 
[External Email]

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Re: filtering <othermeta>

Melissa Kershes
 

I dropped the code to do that into the conductor file as part of the target so it gets called whenever the transform is run, from a build manifest to a regular “generate output” option by a user.

 

Hope this helps a bit!

Melissa

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Dan Vint
Sent: Wednesday, October 21, 2020 9:23 AM
To: main@dita-users.groups.io
Cc: dvint@...
Subject: Re: [dita-users] filtering <othermeta>

 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.

 

 

 

Sent from my Verizon, Samsung Galaxy smartphone

 

 

-------- Original message --------

From: Melissa Kershes <sarala557@...>

Date: 10/20/20 4:40 PM (GMT-08:00)

Subject: Re: [dita-users] filtering <othermeta>

 

Hey Danny. 

 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

 

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

 

Melissa

 

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:

I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan





Re: filtering <othermeta>

Dan Vint
 

I'll check that out. I'm using a build manifest to generate these all at one time and they don't demonstrate that functionality.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Melissa Kershes <sarala557@...>
Date: 10/20/20 4:40 PM (GMT-08:00)
To: main@dita-users.groups.io
Cc: dita-users@groups.io
Subject: Re: [dita-users] filtering <othermeta>

Hey Danny. 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

Melissa

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:
I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan






Re: filtering <othermeta>

Melissa Kershes
 

Hey Danny. 

When I was doing this the bundle name was generated as part of the transform so I used that to make sure I had uniqueness when it was needed.  

The IXIASoft CCMS renames the ditaval file to the map id when it is exported for processing.  Since the bundle name is generally the mapid_ditavalID i added a value in the middle of the bundle name based on vrm. You could use your ditaval values to differentiate the bundle name.  

Melissa

On Tue, Oct 20, 2020, 7:34 PM Dan Vint <dvint@...> wrote:
I checked the spec and othermeta supports/allows filtering with the
@product attribute. I'm running the HTML transformation and it seems
like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
        <title>FORMAT: Single map to use DITAVALS at build time - build
manifest
                <ph product="prod_b">Product B</ph>
                <ph product="prod_c">Product C</ph>
                <ph product="prod_a">Product A</ph></title>
        <topicmeta>
                <othermeta content="FormatProdA" name="bundle" product="prod_a"/>
                <othermeta content="FormatProdB" name="bundle" product="prod_b"/>
                <othermeta content="Formatcommon" name="bundle"
product="prod_common"/>
                <othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
                <othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

        </topicmeta>
        <containerref href="eek1572622465806.ditamap"/>

        <topicref keyref="vln1599578426163"/>
        <!-- topic with ditavals -->
        <topicref keyref="sfq1599578470970" product="prod_a"/>
        <!-- topic product A -->
        <topicref keyref="wkc1599578503581" product="prod_b"/>
        <!-- topic product B -->
        <topicref keyref="vva1599578551353"/>
        <!-- topic all -->
        <topicref keyref="tpu1603147966773" product="prod_c"/>
        <!-- topic product C -->

        <topicref keyref="vln1599578426163" product="prod_c prod_b"/>
        <!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A include Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>
                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>
                        </val>
                </ditavalcontent>
        </body>
</ditaval>

I know the process of filtering is working because the topics are being
stripped out properly, but the HTML shows all the metadata being
generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta
name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating
5 different versions and Zoomin uses this to identify if the content is
new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm
seeing different combinations of the values being written out

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>
        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdA"></meta>

        <meta name="bundle" content="FormatProdAC"></meta>
        <meta name="bundle" content="FormatProdBC"></meta>
        <meta name="bundle" content="Formatcommon"></meta>
        <meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
        <title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
        <shortdesc/>
        <body>
                <ditavalcontent>


                        <val>
                                <prop action="exclude" att="product" val="prod_c"/>
                                <prop action="exclude" att="product" val="prod_b"/>
                                <prop action="include" att="product" val="prod_a"/>

                                <prop action="exclude" att="product" val="prod_common"/>
                                <prop action="exclude" att="product" val="prod_bc"/>
                                <prop action="exclude" att="product" val="prod_ac"/>


                        </val>
                </ditavalcontent>
        </body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan






filtering <othermeta>

Dan Vint
 

I checked the spec and othermeta supports/allows filtering with the @product attribute. I'm running the HTML transformation and it seems like the OT is not processing these elements. I have this map

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN" "PingIdentityMap.dtd">
<map id="kmd1603213063098" xml:lang="en-us">
<title>FORMAT: Single map to use DITAVALS at build time - build manifest
<ph product="prod_b">Product B</ph>
<ph product="prod_c">Product C</ph>
<ph product="prod_a">Product A</ph></title>
<topicmeta>
<othermeta content="FormatProdA" name="bundle" product="prod_a"/>
<othermeta content="FormatProdB" name="bundle" product="prod_b"/>
<othermeta content="Formatcommon" name="bundle" product="prod_common"/>
<othermeta content="FormatProdBC" name="bundle" product="prod_bc"/>
<othermeta content="FormatProdAC" name="bundle" product="prod_ac"/>

</topicmeta>
<containerref href="eek1572622465806.ditamap"/>

<topicref keyref="vln1599578426163"/>
<!-- topic with ditavals -->
<topicref keyref="sfq1599578470970" product="prod_a"/>
<!-- topic product A -->
<topicref keyref="wkc1599578503581" product="prod_b"/>
<!-- topic product B -->
<topicref keyref="vva1599578551353"/>
<!-- topic all -->
<topicref keyref="tpu1603147966773" product="prod_c"/>
<!-- topic product C -->

<topicref keyref="vln1599578426163" product="prod_c prod_b"/>
<!-- topic with ditavals for Prod B and C-->
</map>

And for instance this DITAVAL file

<ditaval id="dyr1599584459162" xml:lang="en-us">
<title>FORMAT Prod A include Prod B and Prod C exclude</title>
<shortdesc/>
<body>
<ditavalcontent>
<val>
<prop action="exclude" att="product" val="prod_c"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>
</val>
</ditavalcontent>
</body>
</ditaval>

I know the process of filtering is working because the topics are being stripped out properly, but the HTML shows all the metadata being generated

<html lang="en-us"><head>
<meta charset="UTF-8"></meta>
<meta name="copyright" content="(C) Copyright 2020"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2020"></meta>
<meta name="DC.type" content="concept"></meta>
<meta name="description" content=""></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="DC.format" content="HTML5"></meta>
<meta name="DC.identifier" content="tpu1603147966773"></meta><meta name="DC.language"

The bundle value controls how Zoomin manages my content. I'm generating 5 different versions and Zoomin uses this to identify if the content is new or replaces something on the site.

In writing this up, I'm looking at a topic from each bundle and I'm seeing different combinations of the values being written out

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>
<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdA"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdA"></meta>

<meta name="bundle" content="FormatProdAC"></meta>
<meta name="bundle" content="FormatProdBC"></meta>
<meta name="bundle" content="Formatcommon"></meta>
<meta name="bundle" content="FormatProdB"></meta>

I modified my DITAVAL file to remove the other labels

<ditaval id="dyr1599584459162" xml:lang="en-us">
<title>FORMAT Prod A incluude Prod B and Prod C exclude</title>
<shortdesc/>
<body>
<ditavalcontent>


<val>
<prop action="exclude" att="product" val="prod_c"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>

<prop action="exclude" att="product" val="prod_common"/>
<prop action="exclude" att="product" val="prod_bc"/>
<prop action="exclude" att="product" val="prod_ac"/>


</val>
</ditavalcontent>
</body>
</ditaval>

But that didn't change my results.

Any idea what I'm missing?

..ddan


Re: DITA-ish structured authoring in Confluence

Hadley, Roger (Hillsboro)
 

I agree that it is difficult to enforce standards in Confluence. If we want content to be well structured in Confluence, one of our tech writers has to re-write and maintain the content contributed by our subject matter experts.

We wrote some XSL that uses the HTML from Scroll HTML Exporter out of Confluence as its source and converts it to DITA concept or reference topics. That works reasonably well if the tech writer curates the Confluence page. One downside is that when our Confluence admins update the Scroll HTML Exporter and the output HTML structure changes, then the XSL breaks and we have to fix it.

Also, we have seen our organization swing to several "new and better" documentation/collaboration platforms over the years. One is Confluence. The latest trend is Azure DevOps Wiki. And of course there is always Sharepoint. And now Teams, which has a wiki. We are cautious about investing too much in a systematized way to get content in and out of a platform when it is likely the content will be abandoned or moved to a different platform. 


Re: DITA-ish structured authoring in Confluence

Nicholas Mucks
 

Hi Yves,
This is an interesting find. We have found Confluence to be both difficult to enforce standards and the best tool for collaboration.

We use Confluence for requirements reviews. We built an OT plugin to create a CSV from DITA source files (based on the title and shortdesc) and import that into a Confluence form so that teams can quickly review and provide feedback. It’s helpful because we can also integrate associations to Jira tickets with that requirements content.

To get content out of Confluence, we usually go from Confluence to DITA via Markdown. It loses some structure along the way, but it’s fine for content with significant team interaction like a Confluence page because sometimes the most important goal is to get that feedback from non-writers.

Take care,
- Nick

Sent from mobile

On Oct 20, 2020, at 1:57 AM, Yves Barbion <yves.barbion@...> wrote:


Hi group

The screen shot in the section "More Guidance, Fewer Constraints" seems to suggest that it must be possible to use custom templates in Confluence, based on the DITA information models:


Is anyone doing this? Any experiences you can share?

Thanks

Yves


DITA-ish structured authoring in Confluence

Yves Barbion
 

Hi group

The screen shot in the section "More Guidance, Fewer Constraints" seems to suggest that it must be possible to use custom templates in Confluence, based on the DITA information models:


Is anyone doing this? Any experiences you can share?

Thanks

Yves


Re: Con(key)reffing terms: uppercase - lowercase

 

Sorry, that is not Dutch, but Danish. I believe that is a common confusion. The country is just as flat and has as many bicycles. But the Dutch phrases would be ‘een systeem’ and ‘het systeem’.

Just sayin'

Jang 

Smart Information Design
Amsterdam, Netherlands
Cell: +31 646 854 996

On 19 Oct 2020, 19:21 +0200, Joe Russo <dita.dude@...>, wrote:
From my experience working with content that is translated, use conref for whole sentences, proper names that aren't translated, or snippets like button names. Don't use conrefs for text that is part of the grammar of the sentence.
"A color definition", "the color definition", "the color definitions" could all be translated and capitalized differently in different contexts.

As an example, in Dutch, "a system" is "en system" but "the system" is "systemet". This means I can't use conrefs for text like "Thanks for buying an <ph>XYZ system</ph>. The <ph>XYZ system</ph> is the best in the industry!".

Even if your content stays in only one language, be aware what happens if you replace product names for OEM. "Thanks for buying an <ph>XYZ system</ph>." breaks if you change the name to PDQ system.


Re: Con(key)reffing terms: uppercase - lowercase

Joe Russo
 

From my experience working with content that is translated, use conref for whole sentences, proper names that aren't translated, or snippets like button names. Don't use conrefs for text that is part of the grammar of the sentence.
"A color definition", "the color definition", "the color definitions" could all be translated and capitalized differently in different contexts.

As an example, in Dutch, "a system" is "en system" but "the system" is "systemet". This means I can't use conrefs for text like "Thanks for buying an <ph>XYZ system</ph>. The <ph>XYZ system</ph> is the best in the industry!".

Even if your content stays in only one language, be aware what happens if you replace product names for OEM. "Thanks for buying an <ph>XYZ system</ph>." breaks if you change the name to PDQ system.


Re: Word2DITA plug-in: cross-references

Pieterjan Vandenweghe
 

Hi Eliot,

I downloaded the project and ran some extra tests which worked fine.
Thanks a lot for your help!


Kind regards,

Pieterjan


On Sun, Oct 18, 2020 at 5:41 PM ekimber@... <ekimber@...> wrote:
I've merged the initial implementation for handling REF complex fields to the develop branch of the https://github.com/dita4publishers/org.dita4publishers.word2dita project. I'm not quite ready to make a formal release but you should be able to download the project and test it.

This update also provides the base for general complex field support, something that wasn't there before.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 10/13/20, 11:18 AM, "ekimber@..." <main@dita-users.groups.io on behalf of ekimber@...> wrote:

    Please file an issue on the word2dita github project and provide a DOCX file that demonstrates the issue and I'll take a look at it.

    https://github.com/dita4publishers/org.dita4publishers.word2dita/issues

    I’m not sure I understand the difference between hyperlinks and cross references in this context, so I you can describe how the cross references are created that will help too.

    Cheers,

    E.

    --
    Eliot Kimber
    http://contrext.com


    On 10/13/20, 10:54 AM, "Pieterjan Vandenweghe" <main@dita-users.groups.io on behalf of pieterjan.vandenweghe@...> wrote:

        I am using the Word2DITA plug-in for the conversion of Word files to DITA.
        This works fine for me in most cases, but I have a problem when cross-references are inserted in the DOCX files.


        The links to all cross-references are lost in my final DITA files.
        Is there any support for cross-references in the plug-in? (If I am correct, hyperlinks added with the Insert > Link feature in Word is supported).
        Is there anyone who can help me to solve this or give me an idea how get this done?

        Thanks a lot in advance for your reply.
        Pieterjan





















Re: Word2DITA plug-in: cross-references

ekimber@contrext.com
 

I've merged the initial implementation for handling REF complex fields to the develop branch of the https://github.com/dita4publishers/org.dita4publishers.word2dita project. I'm not quite ready to make a formal release but you should be able to download the project and test it.

This update also provides the base for general complex field support, something that wasn't there before.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 10/13/20, 11:18 AM, "ekimber@contrext.com" <main@dita-users.groups.io on behalf of ekimber@contrext.com> wrote:

Please file an issue on the word2dita github project and provide a DOCX file that demonstrates the issue and I'll take a look at it.

https://github.com/dita4publishers/org.dita4publishers.word2dita/issues

I’m not sure I understand the difference between hyperlinks and cross references in this context, so I you can describe how the cross references are created that will help too.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 10/13/20, 10:54 AM, "Pieterjan Vandenweghe" <main@dita-users.groups.io on behalf of pieterjan.vandenweghe@gmail.com> wrote:

I am using the Word2DITA plug-in for the conversion of Word files to DITA.
This works fine for me in most cases, but I have a problem when cross-references are inserted in the DOCX files.


The links to all cross-references are lost in my final DITA files.
Is there any support for cross-references in the plug-in? (If I am correct, hyperlinks added with the Insert > Link feature in Word is supported).
Is there anyone who can help me to solve this or give me an idea how get this done?

Thanks a lot in advance for your reply.
Pieterjan


Re: Con(key)reffing terms: uppercase - lowercase

Nicholas Mucks
 

Hi Yves,
We added custom processing on keyword, term, and abbreviated-form that transforms the first letter to uppercase if the writer sets outputclass = cap_first_letter.

We decided to the let the writer decide instead of doing this automatically because all the edge cases would make processing more complex. It also means they can use the same keyreffed element but control the output depending on where the element exists in context.

Take care,
- Nick

Sent from mobile

On Oct 17, 2020, at 8:21 AM, Jarno Elovirta <jelovirt@...> wrote:


Hi,

I've written a DITA-OT implementation for a customer where if you had markup such as

<p><keyword keyref="color-def"/> blaa blaa <keyword keyref="color-def"/>. <keyword keyref="color-def"/> blaa.</p>

When the keyrefs were processed, got transformed into something like

<p><keyword><?keyref?>color definitions</keyword> blaa blaa <keyword><?keyref?>color definitions</keyword>. <keyword><?keyref?>color definitions</keyword> blaa.</p>

So processing instruction keyref is used to mark that something comes from a keyref. Then, another step goes through all those processing instructions and tries to guess if the first character of the keyref content should be uppercased. The rules were simple,
  • Is this the first character in a block element
  • is this character preceded by one or more whitespace characters and a period, exclamation mark or question mark.
This would result in

<p><keyword><?keyref?>Color definitions</keyword> blaa blaa<keyword><?keyref?>color definitions</keyword>. <keyword><?keyref?>Color definitions</keyword> blaa.</p>

This worked well enough, but you could add more complex rules using this same approach.

So you can solve this problem at processing side.

Jarno

On Wed, 19 Aug 2020 at 15:46, Yves Barbion <yves.barbion@...> wrote:
Hi group

Suppose you wish to reuse a term, for example the term "color definitions". This term can, of course, occur anywhere in a sentence, so also at the beginning, where it needs to start with a capital.

What's the best practice in this case? Having the term twice in the "warehouse topic": once with uppercase "C" and once with lowercase?

Or are there any better solutions?

Thanks

Yves


Re: Con(key)reffing terms: uppercase - lowercase

Jarno Elovirta
 

Hi,

I've written a DITA-OT implementation for a customer where if you had markup such as

<p><keyword keyref="color-def"/> blaa blaa <keyword keyref="color-def"/>. <keyword keyref="color-def"/> blaa.</p>

When the keyrefs were processed, got transformed into something like

<p><keyword><?keyref?>color definitions</keyword> blaa blaa <keyword><?keyref?>color definitions</keyword>. <keyword><?keyref?>color definitions</keyword> blaa.</p>

So processing instruction keyref is used to mark that something comes from a keyref. Then, another step goes through all those processing instructions and tries to guess if the first character of the keyref content should be uppercased. The rules were simple,
  • Is this the first character in a block element
  • is this character preceded by one or more whitespace characters and a period, exclamation mark or question mark.
This would result in

<p><keyword><?keyref?>Color definitions</keyword> blaa blaa<keyword><?keyref?>color definitions</keyword>. <keyword><?keyref?>Color definitions</keyword> blaa.</p>

This worked well enough, but you could add more complex rules using this same approach.

So you can solve this problem at processing side.

Jarno

On Wed, 19 Aug 2020 at 15:46, Yves Barbion <yves.barbion@...> wrote:
Hi group

Suppose you wish to reuse a term, for example the term "color definitions". This term can, of course, occur anywhere in a sentence, so also at the beginning, where it needs to start with a capital.

What's the best practice in this case? Having the term twice in the "warehouse topic": once with uppercase "C" and once with lowercase?

Or are there any better solutions?

Thanks

Yves


Re: Does Adobe Framemaker support Schematron? #schematron #FrameMaker

Alan Houser
 

Hi Kris,

No, not directly, and definitely not integrated with the application as with Oxygen XML Editor.

You could use FrameMaker's Extendscript customization language to apply a Schematron validation to a FrameMaker XML document (FrameMaker ships with Saxon and Xalan), and generate a report.

-Alan

On 10/16/20 1:19 PM, Kristen James Eberlein wrote:


If it does, how does their support stack up next to Oxygen XML Editor?
--
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532


Does Adobe Framemaker support Schematron? #schematron #FrameMaker

Kristen James Eberlein
 

If it does, how does their support stack up next to Oxygen XML Editor?

--
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)

481 - 500 of 46295