Date   
Reltable-Struggles #reltable

@l3arn4life
 

Hi there,

we’re making progress on our journey to implementing a reuse-strategy, which made me happy – until I added reltables.
I defined resource-only keys to be used for navigational topicrefs. In my maps, I reference the desired topics using those keys. At the same time, in accordance with Eliot’s prescription about keys, I created unique keys for each instance of a topic on their respective navigational topicref. I then used this unique key to create links among the topics using a reltable. That failed spectacularly: not a single link in my output.
Please refer to the attached sample for the specifics of this setup. I also included an html5-transformation from DOT 3.4.1. (DOT 3.5.2 btw. renders no output at all, which I have no explanation for.)
I tried moving the reltable to its own map, to no avail. In addition to using their unique keys, I added the appropriate href – still no links. I replaced the unique keys and used the resource-only keys – no links.
After searching github, I found a number of bugs related to reltables, some of which had been solved. With the little time I had I unfortunately could not determine whether the issue at hand belongs to one of the known bugs or whether I’m just missing something here. Any help would greatly appreciated.

Many thanks,
Ed

Re: Roadmap of dost.jar #DITA-OT #history

Mark Giffin
 

Hi cant0r,

Wow! This is a problem for ancient history. You might have to rely on the memories of OT developers. Try asking in this group:

https://groups.google.com/forum/#!forum/dita-ot-users

Mark Giffin
Mark Giffin Consulting, Inc.
http://markgiffin.com/

On 8/10/2020 9:20 AM, cant0r via groups.io wrote:

Hi all,

I'm currently in the middle of upgrading my DITA-OT installation from 1.5.2(yeah I know) to 3.5.2. The current version(1.5.2) uses custom Ant scripts and custom start scripts to perform its validating and publishing/formatting tasks. Most of these scripts define a bunch of taskdef with the classpath tag pointing to classes inside the dost.jar archive.
The problem I face is that the paths defined inside the classpath tags became obsolete over the years, some classes were moved or removed, and I was not able to find any changelogs regarding these changes so that I could solve these upcoming issues based on them.
I've managed to solve some issues just by correcting the paths but I cannot figure out what to do with these classes as in I don't know what happened to them and what to use instead of them:

  • org.dita.dost.resolver.URIResolverConfigTask
  • org.dita.dost.util.AntVersion
  • org.dita.dost.log.LogConfigTask
  • org.dita.dost.platform.XmlPropertyTask

I also checked whether someone had this problem in the past by searching through the messages here in the dita-users group but it didn't yield any result.
Also, I had found the release notes of older dita-ots on the old sourceforge page but I had the same success with them as well.

Could you please point me in the right direction?

Thanks, cant0r


Roadmap of dost.jar #DITA-OT #history

cant0r
 

Hi all,

I'm currently in the middle of upgrading my DITA-OT installation from 1.5.2(yeah I know) to 3.5.2. The current version(1.5.2) uses custom Ant scripts and custom start scripts to perform its validating and publishing/formatting tasks. Most of these scripts define a bunch of taskdef with the classpath tag pointing to classes inside the dost.jar archive.
The problem I face is that the paths defined inside the classpath tags became obsolete over the years, some classes were moved or removed, and I was not able to find any changelogs regarding these changes so that I could solve these upcoming issues based on them.
I've managed to solve some issues just by correcting the paths but I cannot figure out what to do with these classes as in I don't know what happened to them and what to use instead of them:

  • org.dita.dost.resolver.URIResolverConfigTask
  • org.dita.dost.util.AntVersion
  • org.dita.dost.log.LogConfigTask
  • org.dita.dost.platform.XmlPropertyTask

I also checked whether someone had this problem in the past by searching through the messages here in the dita-users group but it didn't yield any result.
Also, I had found the release notes of older dita-ots on the old sourceforge page but I had the same success with them as well.

Could you please point me in the right direction?

Thanks, cant0r

Re: How can I just "take the whole thing"

Lief Erickson
 

Roger Sheen has put a lot of work into the DITA-OT website to make it as good as possible. I think he's done a wonderful job. Fortunately, all of Roger's hard work is available for us to mimic and peruse. In addition to the resources from the earlier reply there are these on the DITA-OT website or Github site where the source files are maintained as well.

The DITA-OT website is in this GitHub repository[1]. You can clone it. In there you'll see how the banners are done and the CSS for styling notes and tips. 

You may want to start with the website wiki[2], the "how to build the site" readme [3], and the colophon[4] that explains how everything comes together.


On Fri, Aug 7, 2020 at 11:30 AM Weiwu Zhang via groups.io <weiwu.zhang=alphawallet.com@groups.io> wrote:
Hi fellow users. Just set up my first dita test site & learning DITA
while making it:

https://newsite.alphawallet.com/

Did a bit of customisation too: styled <PRE> for the html5 output:
https://newsite.alphawallet.com/DistinctAttributes.html

My question: the site starts from using minimal CSS and features. How
can I get an "off-you-go" package that includes most of the things
that made this website good?

https://www.dita-ot.org/dev/topics/html-customization-css.html

Specifically, I'm looking to implement the following elements on the above page:

1. Borrow the way it displays a banner:

" May describe unreleased features · Switch to current release 3.5 ·
For shortcuts, type ?"

This is because in our document we also have unreleased features.
(would also be great to get a hint on how to tag certain tech as
"unimplemented")

2. The "Notes" style, like in this:

"Note: As a starting point, you can use the CSS file that is used for
the DITA-OT documentation. This file is available in the installation
folder under docsrc/resources/dita-ot-doc.css."

3. The "Tip" style, like this:

"Tip: For an example of HTML output generated using this method, see
the HTML5 version of the DITA-OT documentation included in the
installation folder under doc/index.html."



Re: Best way for almost identical documents

despopoulos_chriss
 

I'm sorry, but I don't know what you mean by publishing both versions in the same output. 

Do you mean that you want an HTML output that contains both versions, but the user chooses which version to read, and the HTML filters out the other version?  We do that, using audience attributes.  We transform on the fly, so that's how we filter.  But you could just as easily convert audience to some class attribute, and then use CSS to show/hide whatever.

But then again, I'm just guessing at what you want.  Can you be more specific?

Re: [EXT]: Re: [dita-users] Keyscopes?

 

A reusable approach is to use ditaval file to set parameters and then in the map, use <ditavalref> to insert the ditaval file within a key scope.

 

Mona Ross | Principal Information Architect | Ellucian® | M:+1.304.596.3712 | www.ellucian.com

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: Saturday, August 8, 2020 10:43 PM
To: main@dita-users.groups.io
Subject: [EXT]: Re: [dita-users] Keyscopes?

 

**External Email**

What would do within a topic, though? Instead of applying an attribute within that file, would you repeat that DITAVal string in each instance? That appears to be more work. 



On Aug 8, 2020, at 6:04 PM, Chris Papademetrious <chrispitude@...> wrote:

Hi all,

I feel like it would be useful to be able to include DITAVAL directives inline in the map, instead of in files:

<map>

    <topichead keyscope="NoviceSection" navtitle="Novice Documentation">

        <ditaval>

            <prop att="audience" val="novice" action="include"/>

            <prop att="audience" val="expert" action="exclude"/>

            <dvrResourcePrefix>Novice-</dvrResourcePrefix>

            <dvrKeyscopePrefix>Novice-Scope</dvrKeyscopePrefix>

        </ditaval>

        <mapref format="ditamap" keyref="..."/>

    </topichead>


My thinking is,

  • This allows the branch filtering intent to be visible *and* editable directly where the content is instantiated, instead of requiring side files.
  • DITAVAL used for branch filtering is likely to be single-variable and simple (2-3 directives).


Thoughts?

 - Chris

Re: xref to a folder: validation fails

Yves Barbion
 

Hi Radu

ah yes, I missed that one: I can just set @format="folder" but indeed, I had expected a file explorer to open up when I click on that xref in HTML or PDF but indeed, it doesn't happen. So I guess an xref is of no use here and the user can just copy the path in the webhelp and paste it into his file explorer himself.

Thank you for your help again.

Kind regards

Yves

On Mon, 10 Aug 2020 at 10:28, Radu Coravu <radu_coravu@...> wrote:

Hi Yves,

You should definitely set a @format attribute on the xref, otherwise it's interpreted as a reference to a DITA resource.

The @format attribute can take any value, Oxygen just proposes some of the most used ones.

But I'm not sure what you want to obtain or what you'll obtain in the published output, when you click on that link in the generated HTML or PDF what will you expect to happen? Will you expect a file explorer to open up? This will probably not happen.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 8/10/20 11:16 AM, Yves Barbion wrote:
Hi group

I've got this xref to a folder: <xref href="file:///C:/Program%20Files/Oxygen%20XML%20Editor%2021/frameworks/dita/DITA-OT3.x/plugins" scope="external"><filepath>C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins</filepath></xref>

When I validate my topic, I get this validation error:

Reference points to a folder instead of a file: "C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins".

and this warning:

Reference with external scope to non-DITA resource does not have the "format" attribute set correctly on it.

Indeed, the reference does point to a folder, but I don't have "folder" as an option the in the @format attribute values.

Any ideas how I can avoid this validation error?

Kind regards

Yves


  

Re: Dita Build Successful But No PDF Output Generated #DITA-OT #bookmap #PDF

Radu Coravu
 

Hi,

If you look in the console output the publishing seems to break because one of your XSLT stylesheets is not wellformed:

   [xslt] C:\dita-ot\plugins\com.try.custpdf\cfg\fo\attrs\custom.xsl:6:6: Fatal Error! Error reported by XML parser Cause: org.xml.sax.SAXParseException; systemId: file:C:/dita-ot/plugins/com.try.custpdf/cfg/fo/attrs/custom.xsl; lineNumber: 6; columnNumber: 6; Attribute name "version" associated with an element type "xsl" must be followed by the ' = ' character.
Maybe you can fix that error first and then continue your customization.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 8/9/20 5:44 PM, bvigneshwaran21@... wrote:
Hello, Leigh,

Thank you so much for responding.

Based on your advice, I redirected the path of the Build Files to the build.xml file in the dita-ot folder. (Image is attached for your kind reference)
I made sure that all the instructions mentioned in your book are followed. But still, the PDF file is not generated in the output folder, but the build is successful.

I have attached the following:
  1. The output log files.
  2. Screenshot of the output folder
  3. Screenshot of the ant file.
I really have no clue why PDF is not generated. Please help me.

You had advised to upgrade to v2.5.4. (But the full install version is not available for this version.I guess only the minimal version is available to install and that does not have the build file. It just has some folders. In that case,do i need to copy the build.xml files from a fully installed version and paste it to this version.)
  1. I have also attached the screenshot of the 2.5.4 Folder contents. From where to I install the full version. Please guide me.



  

Re: xref to a folder: validation fails

Radu Coravu
 

Hi Yves,

You should definitely set a @format attribute on the xref, otherwise it's interpreted as a reference to a DITA resource.

The @format attribute can take any value, Oxygen just proposes some of the most used ones.

But I'm not sure what you want to obtain or what you'll obtain in the published output, when you click on that link in the generated HTML or PDF what will you expect to happen? Will you expect a file explorer to open up? This will probably not happen.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 8/10/20 11:16 AM, Yves Barbion wrote:

Hi group

I've got this xref to a folder: <xref href="file:///C:/Program%20Files/Oxygen%20XML%20Editor%2021/frameworks/dita/DITA-OT3.x/plugins" scope="external"><filepath>C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins</filepath></xref>

When I validate my topic, I get this validation error:

Reference points to a folder instead of a file: "C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins".

and this warning:

Reference with external scope to non-DITA resource does not have the "format" attribute set correctly on it.

Indeed, the reference does point to a folder, but I don't have "folder" as an option the in the @format attribute values.

Any ideas how I can avoid this validation error?

Kind regards

Yves


  

xref to a folder: validation fails

Yves Barbion
 

Hi group

I've got this xref to a folder: <xref href="file:///C:/Program%20Files/Oxygen%20XML%20Editor%2021/frameworks/dita/DITA-OT3.x/plugins" scope="external"><filepath>C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins</filepath></xref>

When I validate my topic, I get this validation error:

Reference points to a folder instead of a file: "C:\Program Files\Oxygen XML Editor 21\frameworks\dita\DITA-OT3.x\plugins".

and this warning:

Reference with external scope to non-DITA resource does not have the "format" attribute set correctly on it.

Indeed, the reference does point to a folder, but I don't have "folder" as an option the in the @format attribute values.

Any ideas how I can avoid this validation error?

Kind regards

Yves

Re: Best way for almost identical documents

Chris Brand
 

Hi

 

How often do you have this case of almost identical task topics?

 

As a quick shot, I would do the following:

 

  • Create task topic "A" with screenshot "A"
  • Create task topic "B" with screenshot "B" and the key phrase. Conref/Conkeyref everything from "A" that is required. In this case, "A" serves as your toolbox.

 

I understand that filtering is not an option as you need both tasks in the same document, just their content differs in the screenshot and this one key phrase. What I don't understand is the ENTITY thing you tried to do in the DTD for the key phrase. The key phrase is content, right? So what's the idea of messing with the DTD?

 

Greez,

Chris.

 

 

 

Von: main@dita-users.groups.io <main@dita-users.groups.io> Im Auftrag von gdutkowski@...
Gesendet: Donnerstag, 6.
August 2020 02:00
An: main@dita-users.groups.io
Betreff: [dita-users] Best way for almost identical documents

 

Hi,
I have some software that I am describing and for various reasons there are two dialog boxes that are almost identical, except for a key phrase (A or B for simplicity).
So I want to re-use the task document (or most of it) to describe the processes for creating A and B , but have them differ in only the key phrase.

Looking at some of the options, (keydef etc) they seem to rely on different publishing profiles to be able to produce the task for  either A or B, but not both simultaneously.

I hit on using !ENTITY in the DTD header to define the key phrase (I know this is not recommended) in the top of version A and B and then use conref to copy all of the steps from task version A to task version B.
However my DITA CMS promptly removed the !ENTITY definition when I loaded the file back there.

So, is they some alternative way of doing this that I have not yet hit upon?

Sorry of this has been dealt with before, but I could not find it.

Thanks

Greg.

Re: Best way for almost identical documents

Mica Semrick
 


On August 9, 2020 7:15:33 PM PDT, gdutkowski@... wrote:
HI,
Thanks for that.
I am not sure that these answers are addressing the problem, although that may be an indication of my ignorance as I don't recognise all of these tags.

Ditavals, as far as I understand, allow you to publish different versions in different outputs through conditional processing.

I want to publish both versions in the same output as both are needed, they are very similar, different in only a few key phrases.
File t_A.dita
<task id="A">
<steps>
<step><cmd>Go to Page A</cmd></step>
<step><cmd>do X,Y,Z</cmd></step>
</steps>
</task>
File t_B.dita
<task id="B">
<steps>
<step><cmd>Go to Page B</cmd></step>
<step><cmd>do X,Y,Z</cmd></step>
</steps>
</task>

Re: Best way for almost identical documents

gdutkowski@...
 

HI,
Thanks for that.
I am not sure that these answers are addressing the problem, although that may be an indication of my ignorance as I don't recognise all of these tags.

Ditavals, as far as I understand, allow you to publish different versions in different outputs through conditional processing.

I want to publish both versions in the same output as both are needed, they are very similar, different in only a few key phrases.
File t_A.dita
<task id="A">
<steps>
<step><cmd>Go to Page A</cmd></step>
<step><cmd>do X,Y,Z</cmd></step>
</steps>
</task>
File t_B.dita
<task id="B">
<steps>
<step><cmd>Go to Page B</cmd></step>
<step><cmd>do X,Y,Z</cmd></step>
</steps>
</task>

Re: How can I just "take the whole thing"

teamwis
 

Hi Weiwu Zhang,
FYI, both https://infotexture.net/2018/11/customizing-dita-output/ and
http://infotexture.net/2014/04/automating-dita-builds-seattle/ shall
shred some lights on how DITA OT.org works.

We, as one of the Oxygen distributors, have worked with DITA and DITA
OT for quite a while, in case you need timely, professional services,
please let me know.
Cheers



On 8/7/20, Weiwu Zhang via groups.io
<weiwu.zhang=alphawallet.com@groups.io> wrote:
Hi fellow users. Just set up my first dita test site & learning DITA
while making it:

https://newsite.alphawallet.com/

Did a bit of customisation too: styled <PRE> for the html5 output:
https://newsite.alphawallet.com/DistinctAttributes.html

My question: the site starts from using minimal CSS and features. How
can I get an "off-you-go" package that includes most of the things
that made this website good?

https://www.dita-ot.org/dev/topics/html-customization-css.html

Specifically, I'm looking to implement the following elements on the above
page:

1. Borrow the way it displays a banner:

" May describe unreleased features · Switch to current release 3.5 ·
For shortcuts, type ?"

This is because in our document we also have unreleased features.
(would also be great to get a hint on how to tag certain tech as
"unimplemented")

2. The "Notes" style, like in this:

"Note: As a starting point, you can use the CSS file that is used for
the DITA-OT documentation. This file is available in the installation
folder under docsrc/resources/dita-ot-doc.css."

3. The "Tip" style, like this:

"Tip: For an example of HTML output generated using this method, see
the HTML5 version of the DITA-OT documentation included in the
installation folder under doc/index.html."




--
Keep an Exacting Eye for Detail

Re: Dita Build Successful But No PDF Output Generated #DITA-OT #bookmap #PDF

bvigneshwaran21@...
 

Hello, Leigh,

Thank you so much for responding.

Based on your advice, I redirected the path of the Build Files to the build.xml file in the dita-ot folder. (Image is attached for your kind reference)
I made sure that all the instructions mentioned in your book are followed. But still, the PDF file is not generated in the output folder, but the build is successful.

I have attached the following:
  1. The output log files.
  2. Screenshot of the output folder
  3. Screenshot of the ant file.
I really have no clue why PDF is not generated. Please help me.

You had advised to upgrade to v2.5.4. (But the full install version is not available for this version.I guess only the minimal version is available to install and that does not have the build file. It just has some folders. In that case,do i need to copy the build.xml files from a fully installed version and paste it to this version.)
  1. I have also attached the screenshot of the 2.5.4 Folder contents. From where to I install the full version. Please guide me.

Re: Keyscopes?

Thomas Rathkamp
 

What would do within a topic, though? Instead of applying an attribute within that file, would you repeat that DITAVal string in each instance? That appears to be more work. 


On Aug 8, 2020, at 6:04 PM, Chris Papademetrious <chrispitude@...> wrote:

Hi all,

I feel like it would be useful to be able to include DITAVAL directives inline in the map, instead of in files:

<map>
    <topichead keyscope="NoviceSection" navtitle="Novice Documentation">
        <ditaval>
            <prop att="audience" val="novice" action="include"/>
            <prop att="audience" val="expert" action="exclude"/>
            <dvrResourcePrefix>Novice-</dvrResourcePrefix>
            <dvrKeyscopePrefix>Novice-Scope</dvrKeyscopePrefix>
        </ditaval>
        <mapref format="ditamap" keyref="..."/>
    </topichead>

My thinking is,

  • This allows the branch filtering intent to be visible *and* editable directly where the content is instantiated, instead of requiring side files.
  • DITAVAL used for branch filtering is likely to be single-variable and simple (2-3 directives).

Thoughts?

 - Chris

Re: Best way for almost identical documents

Chris Papademetrious
 

Hi all,

I feel like it would be useful to be able to include DITAVAL directives inline in the map, instead of in files:

<map>
    <topichead keyscope="NoviceSection" navtitle="Novice Documentation">
        <ditaval>
            <prop att="audience" val="novice" action="include"/>
            <prop att="audience" val="expert" action="exclude"/>
            <dvrResourcePrefix>Novice-</dvrResourcePrefix>
            <dvrKeyscopePrefix>Novice-Scope</dvrKeyscopePrefix>
        </ditaval>
        <mapref format="ditamap" keyref="..."/>
    </topichead>

My thinking is,

  • This allows the branch filtering intent to be visible *and* editable directly where the content is instantiated, instead of requiring side files.
  • DITAVAL used for branch filtering is likely to be single-variable and simple (2-3 directives).

Thoughts?

How can I just "take the whole thing"

Weiwu Zhang
 

Hi fellow users. Just set up my first dita test site & learning DITA
while making it:

https://newsite.alphawallet.com/

Did a bit of customisation too: styled <PRE> for the html5 output:
https://newsite.alphawallet.com/DistinctAttributes.html

My question: the site starts from using minimal CSS and features. How
can I get an "off-you-go" package that includes most of the things
that made this website good?

https://www.dita-ot.org/dev/topics/html-customization-css.html

Specifically, I'm looking to implement the following elements on the above page:

1. Borrow the way it displays a banner:

" May describe unreleased features · Switch to current release 3.5 ·
For shortcuts, type ?"

This is because in our document we also have unreleased features.
(would also be great to get a hint on how to tag certain tech as
"unimplemented")

2. The "Notes" style, like in this:

"Note: As a starting point, you can use the CSS file that is used for
the DITA-OT documentation. This file is available in the installation
folder under docsrc/resources/dita-ot-doc.css."

3. The "Tip" style, like this:

"Tip: For an example of HTML output generated using this method, see
the HTML5 version of the DITA-OT documentation included in the
installation folder under doc/index.html."

Re: Keyscopes?

Dan Vint
 

My test sample worked. I must be missing something in the content that is causing the problem. I'm going to tease apart the actual content some more as I must be missing some small detail.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Radu Coravu <radu_coravu@...>
Date: 8/5/20 10:13 PM (GMT-08:00)
To: main@dita-users.groups.io, dita-users@groups.io
Subject: Re: [dita-users] Keyscopes?

Hi Dan,

Maybe indeed you can construct a small DITA project exemplifying your
case, then try to publish it to plain HTML5 using the latest DITA OT
distribution. If that does not work, maybe you can share the small DITA
project with us along with details about the expected output.

Regards,
Radu

Radu Coravu
Oxygen XML Editor

On 8/6/20 2:23 AM, Dan Vint wrote:
> How stable or well implemented are they? I'm using DITA OT 3.4.0 and
> they don't appear to be working as expected. I have 5 separate
> publications that had their own copy of keymaps that had a common set
> of variable names. So the name BASE_NAME appears in each keymap but
> with a different value.
>
> We are now publishing these as one bundle. So they have been grouped
> together with one map like this.
> <map>
>    <topichead keyscope="DirectoryServerKeys" navtitle="Server
> Administration Guide">
>       <mapref format="ditamap" keyref="bbv1564011413207"/>
>    </topichead>
>    <topichead keyscope="ProxyServerKeys" navtitle="Proxy Server
> Administration Guide">
>       <mapref format="ditamap" keyref="dsa1564011474136"/>
>    </topichead>
>    <topichead keyscope="ConsentSolutionKeys" navtitle="Consent
> Solution Guide">
>       <mapref format="ditamap" keyref="ugq1564011487101"
>          navtitle="Consent Solution Guide"/>
>    </topichead>
>    <topichead keyscope="DelegatedAdminKeys" navtitle="Delegated Admin
> Application Guide">
>       <mapref format="ditamap" keyref="nyx1564012075196"
>          navtitle="Delegated Admin Guide"/>
>    </topichead>
>    <topichead keyscope="DataSyncKeys" navtitle="Administration Guide">
>       <mapref format="ditamap" keyref="wfk1564011491470"
>          navtitle="Administration Guide"/>
>    </topichead>
> </map>
>
> There is no keymap above any of the maprefs, yet BASE_NAME in all the
> sections shows the same value. For testing I commented out the
> definition that was being used everywhere and one of the other
> definitions replaced it.
>
> This content is huge and ugly. I may try building my own sample and
> testing with it in case I'm not finding the real problem in this
> content and thinking it is the keyscope that is not working.
>
> ..dan
>
>
>




Re: Keyscopes?

Dan Vint
 

Thanks for the info. 1.3 appears to make this much simpler although I was checking Google to see if there was something more needed than just adding this keyscope label.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Lief Erickson <lief.erickson@...>
Date: 8/5/20 10:34 PM (GMT-08:00)
To: main@dita-users.groups.io
Cc: DITA Users <dita-users@groups.io>
Subject: Re: [dita-users] Keyscopes?

Hi Dan--

Here's a mockup of the first three <topichead> elements from your example where I added a <ditavalref> with <dvrResourcePrefix> and <dvrKeyscopePrefix> elements. With these I am able to produce unique output for BASE_NAME. I was using this structure successfully with DITA-OT 2.2.5 (if memory serves) but certainly 2.5.4. I tested this example with DITA-OT 3.4 and 3.5.2 and had successful results. Since you mentioned that BASE_NAME was defined in the separate ditamaps, I went with that. As such, any brave soul copying this would need to also define the key. Further, new ditavals will need to be created. 

<map>
    <topichead keyscope="DirectoryServerKeys" navtitle="Server
        Administration Guide">
        <ditavalref href="DirectoryServerKeys.ditaval">
            <ditavalmeta>
                <dvrResourcePrefix>DirectoryServerKeys-</dvrResourcePrefix>
                <dvrKeyscopePrefix>DirectoryServerKeys-Scope</dvrKeyscopePrefix>
            </ditavalmeta>
        </ditavalref>
        <mapref format="ditamap" keyref="bbv1564011413207"/>
    </topichead>
    <topichead keyscope="ProxyServerKeys" navtitle="Proxy Server
        Administration Guide">
        <ditavalref href="ProxyServerKeys.ditaval">
            <ditavalmeta>
                <dvrResourcePrefix>ProxyServerKeys-</dvrResourcePrefix>
                <dvrKeyscopePrefix>ProxyServerKeys-Scope</dvrKeyscopePrefix>
            </ditavalmeta>
        </ditavalref>
        <mapref format="ditamap" keyref="dsa1564011474136"/>
    </topichead>
    <topichead keyscope="ConsentSolutionKeys" navtitle="Consent Solution
        Guide">
        <ditavalref href="ConsentSolutionKeys.ditaval">
            <ditavalmeta>
                <dvrResourcePrefix>ConsentSolutionKeys-</dvrResourcePrefix>
                <dvrKeyscopePrefix>ConsentSolutionKeys-Scope</dvrKeyscopePrefix>
            </ditavalmeta>
        </ditavalref>
        <mapref format="ditamap" keyref="ugq1564011487101"
            navtitle="Consent Solution Guide"/>
    </topichead>
</map>

Example ditaval files. Modify as necessary.

DirectoryServerKeys.ditaval  
<val>
    <prop action="exclude"/>
    <prop action="include" att="product" val=" DirectoryServerKeys"/>
</val>

ProxyServerKeys.ditaval  
<val>
    <prop action="exclude"/>
    <prop action="include" att="product" val="ProxyServerKeys"/>
</val>

In DITA-OT 3.4.1 there was a change related to the <dvrResourcePrefix> or <dvrResourceSuffix> elements that you may want to be aware of.

-Lief

On Wed, Aug 5, 2020 at 6:23 PM Dan Vint <dvint@...> wrote:
How stable or well implemented are they? I'm using DITA OT 3.4.0 and
they don't appear to be working as expected. I have 5 separate
publications that had their own copy of keymaps that had a common set of
variable names. So the name BASE_NAME appears in each keymap but with a
different value.

We are now publishing these as one bundle. So they have been grouped
together with one map like this.
<map>
    <topichead keyscope="DirectoryServerKeys" navtitle="Server
Administration Guide">
       <mapref format="ditamap" keyref="bbv1564011413207"/>
    </topichead>
    <topichead keyscope="ProxyServerKeys" navtitle="Proxy Server
Administration Guide">
       <mapref format="ditamap" keyref="dsa1564011474136"/>
    </topichead>
    <topichead keyscope="ConsentSolutionKeys" navtitle="Consent Solution
Guide">
       <mapref format="ditamap" keyref="ugq1564011487101"
          navtitle="Consent Solution Guide"/>
    </topichead>
    <topichead keyscope="DelegatedAdminKeys" navtitle="Delegated Admin
Application Guide">
       <mapref format="ditamap" keyref="nyx1564012075196"
          navtitle="Delegated Admin Guide"/>
    </topichead>
    <topichead keyscope="DataSyncKeys" navtitle="Administration Guide">
       <mapref format="ditamap" keyref="wfk1564011491470"
          navtitle="Administration Guide"/>
    </topichead>
</map>

There is no keymap above any of the maprefs, yet BASE_NAME in all the
sections shows the same value. For testing I commented out the
definition that was being used everywhere and one of the other
definitions replaced it.

This content is huge and ugly. I may try building my own sample and
testing with it in case I'm not finding the real problem in this content
and thinking it is the keyscope that is not working.

..dan