Date   

Glossary term: singular vs. plural #glossary

Wito Zoerkler
 

How do you deal with the following use case? What is your solution?
 
A glossary term is normally defined in singular, e.g. 'software module'. In the context the term is used often as well in plural.
Ideas I am not really satisfied with:
  • Glossary term defined in plural
  • <term keyref="KEYNAME"/>s  --> Definitely problems with localization
  • <term keyref="KEYNAME">software modules</term>  --> Problems with localization? And this only works with <term> not with <abbreviated-form>
Best regards
Wito


Re: Variable text referenced using keys

Patricia Billard
 

Hi Kris, 
Most of our group uses SDL variables instead of keys, but I wanted to respond to your other questions. 
  • We use variable text for the company name (full and abbreviated), product names, URLs, names of websites, software version numbers, publication titles or shortened names, different hardware parts or software components that have changed names in the past, UI window names, and UI button or menu item names - especially when those names are changing often (usually when a product is first being developed).  
  • By far the biggest pain point is that <ph> can't be used in several places in which we'd like to use a variable such as <uicontrol>, <wintitle>, <userinput>, <msgblock><organization>, and so forth. That is a huge pain, because we have to define multiple variable names for the same thing, and we can't offer a single Schematron quick fix to replace a text company name with the correct variable, for example.  
Thank you,
--Trish Billard


Re: Variable text referenced using keys

Chris Papademetrious
 

Hi Kris,

We use variables for

  • Product name
  • Product name, trademarked version
  • Product release version
  • Product release date
  • Product shell prompt (a software thing)

Some of our books are conditional across multiple products, and so we conditionalize product name and shell prompt by @product. If the product has a single book, these are defined right in the bookmap. If there is a family of books related to a product, they are defined in a separate map file.

All products release on a planned version and date schedule. These variables are defined in a separate map file, programmatically updated by our release database.

I hope you are looking at making this element structure more user-friendly:

  <keydef keys="Prompt" product="all">
    <topicmeta>
      <keywords>
        <keyword>this_shell</keyword>
      </keywords>
    </topicmeta>
  </keydef>
  <keydef keys="Prompt" product="prod1">
    <topicmeta>
      <keywords>
        <keyword>prod1_shell</keyword>
      </keywords>
    </topicmeta>
  </keydef>
...


This gets lengthy when defining many values -- or many conditional values!

 - Chris


[ann][webinar] What techcomm can learn from the games industry with Samantha Blackmon #Room42 Oct 28th @ 15:30 UTC #room42

Liz Fraley
 

Title: What techcomm can learn from the games industry

When: Wednesday, Oct 28th @ (8:30 LAX | 11:30 NYC | 16:30 LON | 20:00 BLR)

Register: https://bit.ly/35ohHRp

Description:

Samantha Blackmon will be In The Room!

Room 42 is where practitioners and academics meet to share knowledge about breaking research in an approachable, accessible way.

In our next session, Samantha Blackmon, Purdue University, will be in the room.

Sam will be discussing how to use games in our scholarship, our content projects, and in the classroom. We'll talk about the importance of reaching your audience -- ALWAYS, meeting them where they are, and how to reflect and relate to them. She'll also discuss how lessons from the gaming industry can be useful anywhere people are learning, absorbing, and interacting with content. For example, she'll talk about how games have a way of "scaffolding their tutorials," that promotes quick adoption and long term retention in content consumers.

We're looking forward to exploring what techcomm can learn from the games industry in the next Room 42.

Samantha Blackmon (she/her) is a gamer/researcher/games researcher who loves playing games with her daughter and talking about games with anyone else who will listen or watch. She is passionate about games and making the games community a more inclusive space. Her research focuses on bringing together the voices of gamers, academics, and games industry folks in order to get a fuller picture of the games community and all of the people who comprise it. Her greatest academic goal is to create scholarship that is informed by and accessible to those outside of the academy, which makes for some pretty non-traditional work.

Her recent work has included looking at how to use games in the classroom and a Black Feminist Mixtape analysis of how Black women have affected the video game industry. She is currently working on a project that pays homage to the upcoming 10th anniversary of her blog and podcast, Not Your Mama’s Gamer, and a project that looks at representation and visibility of marginalized people on live streaming platforms. Samantha loves video games, books, crafting, and coffee, definitely coffee.



-:-

The Room 42 is brought to you by Single-Sourcing Solutions. Learn more: http://room42.single-sourcing.com


Register: https://bit.ly/35ohHRp


Variable text referenced using keys

Kristen James Eberlein
 

Hi, DITA users.

I'm looking for information about how your implementations use keys for variable text. Variable text is text that you want to appear differently based on the context.

A couple of questions, for implementations that use keys to define variable text:

  1. What kind of content do you use variable text for? (Examples: product names, device names, product slogans or tag lines ...)
  2. What markup patterns do you use for key definition? For key referencing?
  3. Any pain points around variable text? Any particular successes? Things you wish were different?

For DITA 2.0, the DITA TC will be introducing simplified markup and processing for variable stuff referenced using keys. I am soliciting background information that will help inform our choices.

--
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)


Re: table entry attributes

scott ashmead
 

Hi Eliot,
This problem is looking more and more like some sort of data corruption problem. We are unable to reproduce the error, which occurred in a client's environment.

On Friday, October 23, 2020, 09:49:31 AM EDT, ekimber@... <ekimber@...> wrote:


Would need to see the whole table, including the colspecs.

The most likely answer is that the table is not coded correctly--Oxygen should validate the table structure and report any issues like bad span specs or incorrect column numbers or something.

Is the colname in the table as authored?

Cheers,

E.
--
Eliot Kimber
http://contrext.com


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


            Thanks Eliot.
    The specific problem I'm having is related to the colname attribute in the row below.
    There are six <entry> elements in the row. <entry> number five does not have a colname attribute and I don't know why. There's colname='4', then an empty element. Then colname="5". It's as though the empty <entry> is being ignored. Any idea how/why an <entry> would not have a colname attribute?


                            <row base="VISION_RCF" class="- topic/row " rowsep="0" valign="bottom"
                              xtrf="file:/opt/app/instances/4356386/resxml/workspaces/1ca4cda4a03a4c4d4a92fc1340d6c2636f2f0b91/data/2698167e-29bf-44f8-88e4-4c0fe2dd1c2e/input/prime_Renewal_Change_Form_SO.dita"
                              xtrc="row:7;191:93">
                              <entry align="left" colname="col1">
                                  <p>Vision</p>
                              </entry>
                              <entry align="center" colname="col2">
                                  <p>☐</p>
                              </entry>
                              <entry align="center" colname="col3">
                                  <p>☐</p>
                              </entry>
                              <entry align="center" colname="col4">
                                  <p>☐</p>
                              </entry>
                              <entry/>
                              <entry align="left" colname="col5">
                                  <p>____________________</p>
                              </entry>
                            </row>










                        On Thursday, October 22, 2020, 05:55:38 PM EDT, ekimber@... <ekimber@...> wrote:



                    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">
























   









Re: table entry attributes

ekimber@contrext.com
 

Would need to see the whole table, including the colspecs.

The most likely answer is that the table is not coded correctly--Oxygen should validate the table structure and report any issues like bad span specs or incorrect column numbers or something.

Is the colname in the table as authored?

Cheers,

E.
--
Eliot Kimber
http://contrext.com


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


Thanks Eliot.
The specific problem I'm having is related to the colname attribute in the row below.
There are six <entry> elements in the row. <entry> number five does not have a colname attribute and I don't know why. There's colname='4', then an empty element. Then colname="5". It's as though the empty <entry> is being ignored. Any idea how/why an <entry> would not have a colname attribute?


<row base="VISION_RCF" class="- topic/row " rowsep="0" valign="bottom"
xtrf="file:/opt/app/instances/4356386/resxml/workspaces/1ca4cda4a03a4c4d4a92fc1340d6c2636f2f0b91/data/2698167e-29bf-44f8-88e4-4c0fe2dd1c2e/input/prime_Renewal_Change_Form_SO.dita"
xtrc="row:7;191:93">
<entry align="left" colname="col1">
<p>Vision</p>
</entry>
<entry align="center" colname="col2">
<p>☐</p>
</entry>
<entry align="center" colname="col3">
<p>☐</p>
</entry>
<entry align="center" colname="col4">
<p>☐</p>
</entry>
<entry/>
<entry align="left" colname="col5">
<p>____________________</p>
</entry>
</row>

On Thursday, October 22, 2020, 05:55:38 PM EDT, ekimber@... <ekimber@...> wrote:



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">


[ann][webinar] Explore Web Author beyond technical documentation #Oxygen

alin_belu@...
 

Hello, 
 
Our weekly series of live events continues on Wednesday (October 28), with the “Explore Web Author beyond technical documentation” webinar! 
 
Picture a growing company. As it grows, so does the need for standardized procedures. And when new people join the company, they often need to be trained to follow existing procedures. As you can see, a lot of time is spent in training sessions, affecting your overall productivity. 
 
With this in mind, Bogdan Dumitru, software developer at Syncro Soft, will show you how Web Author comes in handy in instances like this one, allowing you to build guided procedures where new employees don't require additional training or validation. 
 
During this webinar, you will learn various ways in which Web Author can be used to enhance your productivity: 
* Guiding new writers with the help of Schematron Quick Fixes or easy-to-configure contextual actions, so they can just follow the on-screen instructions. 
* Creating forms and sharing them with other users, with the possibility of automated processing. 
* Using Web Author to keep track of standardized procedures (e.g. release notes) with the possibility of filtering out the completed tasks and only focusing on the ongoing ones. 
* Document collaboration with real-time co-authoring. Instead of having read-only access to a document, now you can work alongside other colleagues. 
 
This is a free event and you can register at http://www.oxygenxml.com/evs2020-14.html 
 
Check the full list of the upcoming webinars and follow the links to see more details and register for free: 
 
Best regards,
Alin
--
Alin Belu
Oxygen XML Editor


Re: table entry attributes

Radu Coravu
 

Hi Scott,

Maybe you can come up with a minimal set of map+topic sample project to reproduce the situation.

Then try to see if the problem is still there when using the latest DITA OT stable distribution (DITA OT 3.5.4 right now).

If the problem can be reproduced maybe you can add an issue on the DITA OT issues list:

https://github.com/dita-ot/dita-ot/issues

The DITA OT module which adds these attributes is written in Java. You can search for ""org.dita.dost.writer.NormalizeTableFilter"" to find in the build files the place where the normalize table filter is called.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 10/23/20 1:37 AM, scott ashmead via groups.io wrote:

Thanks Eliot.
The specific problem I'm having is related to the colname attribute in the row below.
There are six <entry> elements in the row. <entry> number five does not have a colname attribute and I don't know why. There's colname='4', then an empty element. Then colname="5". It's as though the empty <entry> is being ignored. Any idea how/why an <entry> would not have a colname attribute?

                        <row base="VISION_RCF" class="- topic/row " rowsep="0" valign="bottom"
                           xtrc="row:7;191:93">
                           <entry align="left" colname="col1">
                              <p>Vision</p>
                           </entry>
                           <entry align="center" colname="col2">
                              <p>☐</p>
                           </entry>
                           <entry align="center" colname="col3">
                              <p>☐</p>
                           </entry>
                           <entry align="center" colname="col4">
                              <p>☐</p>
                           </entry>
                           <entry/>
                           <entry align="left" colname="col5">
                              <p>____________________</p>
                           </entry>
                        </row>



On Thursday, October 22, 2020, 05:55:38 PM EDT, ekimber@... <ekimber@...> wrote:


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">








   










  


Re: table entry attributes

scott ashmead
 

Thanks Eliot.
The specific problem I'm having is related to the colname attribute in the row below.
There are six <entry> elements in the row. <entry> number five does not have a colname attribute and I don't know why. There's colname='4', then an empty element. Then colname="5". It's as though the empty <entry> is being ignored. Any idea how/why an <entry> would not have a colname attribute?

                        <row base="VISION_RCF" class="- topic/row " rowsep="0" valign="bottom"
                           xtrf="file:/opt/app/instances/4356386/resxml/workspaces/1ca4cda4a03a4c4d4a92fc1340d6c2636f2f0b91/data/2698167e-29bf-44f8-88e4-4c0fe2dd1c2e/input/prime_Renewal_Change_Form_SO.dita"
                           xtrc="row:7;191:93">
                           <entry align="left" colname="col1">
                              <p>Vision</p>
                           </entry>
                           <entry align="center" colname="col2">
                              <p>☐</p>
                           </entry>
                           <entry align="center" colname="col3">
                              <p>☐</p>
                           </entry>
                           <entry align="center" colname="col4">
                              <p>☐</p>
                           </entry>
                           <entry/>
                           <entry align="left" colname="col5">
                              <p>____________________</p>
                           </entry>
                        </row>



On Thursday, October 22, 2020, 05:55:38 PM EDT, ekimber@... <ekimber@...> wrote:


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">








   









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.