Date   

Re: ditavalref ditaval file not recognized and excluded during processing

ekimber@contrext.com
 

You should not be able to use key references on ditavalref--the DTD for your map should not allow @keyref on <ditavalref>, so the fact that you have it there suggests something is not right with the DTD (or else the document is not actually valid).

From the DITA 1.3 spec:

2.4.4.5 Branch filtering: Implications of processing order

Because the branch filtering process can result in new or renamed keys, key scopes, or URIs, the full effects of
the branch filtering process MUST be calculated by processors before they construct the effective map and key
scope structure.

Note: The @keyref attribute and related attributes are explicitly disallowed on <ditavalref>. This prevents
any confusion resulting from a @keyref that resolves to additional key- or resource-renaming metadata.

So your map structure is not correct per the spec--you'll need to make direct URI references to your ditaval files.

Cheers,

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


On 9/9/20, 4:13 PM, "Dan Vint" <main@dita-users.groups.io on behalf of dvint@...> wrote:

I'm not sure what is going on. I'm trying to setup a map that will have
different sections that have the same content but will be filtered with
with ditvals for different results. My main map references several other
maps for those sections and each section/submap uses a different
ditaval.

The setup and content of these objects are correct and validate. But
when I run them through the DITA-OT version = 3.4.1 OT, it looks like
the dtaval files are not being recognized as ditaval files and they are
being stripped out. End result is that my content is not being filtered.
Here are the OT messages

gen-list:
[gen-list] Using Xerces grammar pool for DTD and schema caching.
[gen-list] Processing
file:/Users/danvint/Desktop/_multi-ditaval/_fkn1599574223928.ditamap
[gen-list] Processing
file:/Users/danvint/Desktop/_multi-ditaval/dyr1599584459162.ditaval
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<val>'. The element will be processed as an unknown or non-DITA
element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<prop>'. The element will be processed as an unknown or
non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<prop>'. The element will be processed as an unknown or
non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<prop>'. The element will be processed as an unknown or
non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<prop>'. The element will be processed as an unknown or
non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for
element '<prop>'. The element will be processed as an unknown or
non-DITA element.
[gen-list] [DOTJ021E][ERROR] File
'file:/Users/danvint/Desktop/_multi-ditaval/dyr1599584459162.ditaval'
will not generate output because because all content has been filtered
out by DITAVAL "exclude" conditions, or because the file is not valid
DITA.

That ditaval file looks like this

<?xml version="1.0" encoding="UTF-8"?>
<val>
<prop action="include"/>
<prop action="include" att="platform"/>
<prop action="include" att="audience"/>
<prop action="include" att="rev"/>
<prop action="include" att="otherprops"/>
<prop action="include" att="deliveryTarget"/>
<prop action="include" att="product"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>
</val>


My root map has this

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="fkn1599574223928" xml:lang="en-us">
<title>FORMAT: multiditaval - ditavalref testing</title>
<topicmeta> </topicmeta>


<keydef href="dyr1599584459162.ditaval" keys="dyr1599584459162"
xtrc="ixiasoft.drm.remove"/>
<keydef href="msz1599584786347.ditaval" keys="msz1599584786347"
xtrc="ixiasoft.drm.remove"/>
<keydef href="kgo1599578351118.ditamap" keys="kgo1599578351118"
xtrc="ixiasoft.drm.remove"/>
<keydef href="vva1599578551353.dita" keys="vva1599578551353"
xtrc="ixiasoft.drm.remove"/>
<keydef href="sfq1599578470970.dita" keys="sfq1599578470970"
xtrc="ixiasoft.drm.remove"/>
<keydef href="wkc1599578503581.dita" keys="wkc1599578503581"
xtrc="ixiasoft.drm.remove"/>
<keydef href="cjq1599588363521.ditamap" keys="cjq1599588363521"
xtrc="ixiasoft.drm.remove"/>
<keydef href="tur1599578307311.ditamap" keys="tur1599578307311"
xtrc="ixiasoft.drm.remove"/>
<keydef href="vln1599578426163.dita" keys="vln1599578426163"
xtrc="ixiasoft.drm.remove"/>
<keydef href="fjg1599584933747.ditaval" keys="fjg1599584933747"
xtrc="ixiasoft.drm.remove"/>
<keydef href="liz1599578247043.ditamap" keys="liz1599578247043"
xtrc="ixiasoft.drm.remove"/>
<topichead navtitle="All content no filters">
<mapref format="ditamap" keyref="cjq1599588363521"/>
</topichead>

<topichead navtitle="Common Content only - Exclude A and B ">
<mapref format="ditamap" keyref="liz1599578247043"/>
</topichead>

<topichead navtitle="Product A - Exclude B">
<mapref format="ditamap" keyref="tur1599578307311"/>
</topichead>
<topichead navtitle="Product B - Exclude A">
<mapref format="ditamap" keyref="kgo1599578351118"/>
</topichead>


</map>

The map using that particular ditaval is structured this way

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN"
"PingIdentityMap.dtd">
<map id="tur1599578307311" xml:lang="en-us">
<title>FORMAT: Product A content only</title>
<topicmeta> </topicmeta>

<ditavalref keyref="dyr1599584459162" processing-role="resource-only"/>
<topicref keyref="vln1599578426163"/> <!-- topic with ditavals -->
<topicref keyref="sfq1599578470970"/> <!-- topic product A -->
<topicref keyref="wkc1599578503581"/> <!-- topic product B -->
<topicref keyref="vva1599578551353"/> <!-- topic all -->

</map>

I've attached a zipfile of the complete fileset.

I looked to see if there was any other setup required. I thought maybe a
processing-role was required, but I see that ditavalref defaults to
resource only.

..dan


ditavalref ditaval file not recognized and excluded during processing

Dan Vint
 

I'm not sure what is going on. I'm trying to setup a map that will have different sections that have the same content but will be filtered with with ditvals for different results. My main map references several other maps for those sections and each section/submap uses a different ditaval.

The setup and content of these objects are correct and validate. But when I run them through the DITA-OT version = 3.4.1 OT, it looks like the dtaval files are not being recognized as ditaval files and they are being stripped out. End result is that my content is not being filtered. Here are the OT messages

gen-list:
[gen-list] Using Xerces grammar pool for DTD and schema caching.
[gen-list] Processing file:/Users/danvint/Desktop/_multi-ditaval/_fkn1599574223928.ditamap
[gen-list] Processing file:/Users/danvint/Desktop/_multi-ditaval/dyr1599584459162.ditaval
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<val>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<prop>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<prop>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<prop>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<prop>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ030I][INFO] No 'class' attribute for was found for element '<prop>'. The element will be processed as an unknown or non-DITA element.
[gen-list] [DOTJ021E][ERROR] File 'file:/Users/danvint/Desktop/_multi-ditaval/dyr1599584459162.ditaval' will not generate output because because all content has been filtered out by DITAVAL "exclude" conditions, or because the file is not valid DITA.

That ditaval file looks like this

<?xml version="1.0" encoding="UTF-8"?>
<val>
<prop action="include"/>
<prop action="include" att="platform"/>
<prop action="include" att="audience"/>
<prop action="include" att="rev"/>
<prop action="include" att="otherprops"/>
<prop action="include" att="deliveryTarget"/>
<prop action="include" att="product"/>
<prop action="exclude" att="product" val="prod_b"/>
<prop action="include" att="product" val="prod_a"/>
</val>


My root map has this

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN" "PingIdentityMap.dtd">
<map id="fkn1599574223928" xml:lang="en-us">
<title>FORMAT: multiditaval - ditavalref testing</title>
<topicmeta> </topicmeta>


<keydef href="dyr1599584459162.ditaval" keys="dyr1599584459162" xtrc="ixiasoft.drm.remove"/>
<keydef href="msz1599584786347.ditaval" keys="msz1599584786347" xtrc="ixiasoft.drm.remove"/>
<keydef href="kgo1599578351118.ditamap" keys="kgo1599578351118" xtrc="ixiasoft.drm.remove"/>
<keydef href="vva1599578551353.dita" keys="vva1599578551353" xtrc="ixiasoft.drm.remove"/>
<keydef href="sfq1599578470970.dita" keys="sfq1599578470970" xtrc="ixiasoft.drm.remove"/>
<keydef href="wkc1599578503581.dita" keys="wkc1599578503581" xtrc="ixiasoft.drm.remove"/>
<keydef href="cjq1599588363521.ditamap" keys="cjq1599588363521" xtrc="ixiasoft.drm.remove"/>
<keydef href="tur1599578307311.ditamap" keys="tur1599578307311" xtrc="ixiasoft.drm.remove"/>
<keydef href="vln1599578426163.dita" keys="vln1599578426163" xtrc="ixiasoft.drm.remove"/>
<keydef href="fjg1599584933747.ditaval" keys="fjg1599584933747" xtrc="ixiasoft.drm.remove"/>
<keydef href="liz1599578247043.ditamap" keys="liz1599578247043" xtrc="ixiasoft.drm.remove"/>
<topichead navtitle="All content no filters">
<mapref format="ditamap" keyref="cjq1599588363521"/>
</topichead>

<topichead navtitle="Common Content only - Exclude A and B ">
<mapref format="ditamap" keyref="liz1599578247043"/>
</topichead>

<topichead navtitle="Product A - Exclude B">
<mapref format="ditamap" keyref="tur1599578307311"/>
</topichead>
<topichead navtitle="Product B - Exclude A">
<mapref format="ditamap" keyref="kgo1599578351118"/>
</topichead>


</map>

The map using that particular ditaval is structured this way

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//PINGIDENTITY//DTD DITA Map//EN" "PingIdentityMap.dtd">
<map id="tur1599578307311" xml:lang="en-us">
<title>FORMAT: Product A content only</title>
<topicmeta> </topicmeta>

<ditavalref keyref="dyr1599584459162" processing-role="resource-only"/>
<topicref keyref="vln1599578426163"/> <!-- topic with ditavals -->
<topicref keyref="sfq1599578470970"/> <!-- topic product A -->
<topicref keyref="wkc1599578503581"/> <!-- topic product B -->
<topicref keyref="vva1599578551353"/> <!-- topic all -->

</map>

I've attached a zipfile of the complete fileset.

I looked to see if there was any other setup required. I thought maybe a processing-role was required, but I see that ditavalref defaults to resource only.

..dan


Re: relationship beteween 3 types of documents for the same concept

Weiwu Zhang
 

On Thu, 3 Sep 2020, Weiwu Zhang via groups.io wrote:

My question is what's the best practise to connect these 3 types of
document?
Ah, after banging my head on this wall for a week, I saw the new post from Tonia asking about "Relationship table publishing?" and google searched from there. It turns out the answer to my question is simple: use relationsihp table. Would have saved me much time if I had known what search keyword to use.

It's surprising that after reading dozens and dozens of web pages, and
finishing a book about LwDita (yes I known this falls outside LwDita
but only in hindsight) I have not chanced upon related links
management, and it only shows magically after I learned the name of
the technology for related links management. I guess related links
management wasn't shown in related links of the docs I read!

Regards
W Z


Re: Relationship table publishing?

Nicholas Mucks
 

Hi Tonia,
If you never care about the automatically-created links and care only about the links in the reltable, then I believe setting args.rellinks to nofamily and including the reltable will meet your needs.

Take care,
- Nick

Sent from mobile

On Sep 6, 2020, at 5:49 PM, Tonia <sharpwriter@...> wrote:


Hi all,
I’m looking at the Rellinks.arg and wondering how to publish related links only if the ditamap has a relationship table.

For ditamap that aren’t using a relationship table, the desired behavior is that no related links are shown. I’m told that this configuration also blocks inclusion of a relationship table.

We’d like to serve both use cases with the same output transform. Is this possible?

Thanks for any guidance,
Tonia




Relationship table publishing?

Tonia
 

Hi all,
I’m looking at the Rellinks.arg and wondering how to publish related links only if the ditamap has a relationship table.

For ditamap that aren’t using a relationship table, the desired behavior is that no related links are shown. I’m told that this configuration also blocks inclusion of a relationship table.

We’d like to serve both use cases with the same output transform. Is this possible?

Thanks for any guidance,
Tonia


Opportunity at Peterbilt #jobhunting

David Yin
 

Peterbilt is currently looking for a Technical Content Lead. This role will be responsible for information architecture of the technical content (operator and service manuals) for Peterbilt. 

https://jobs.paccar.com/job/Denton-Technical-Content-Lead-Job-TX-76201/616533201/


Re: Are you using <data-about>?

stinakab
 

Hi Kris,

We have no use case for <data-about>, so we don't need it.

Best,
Christina


Re: New Oxygen add-on to help translators

Radu Coravu
 

Hi Jonathan,

Thanks for the feedback, we considered that if the end user selects plain text, without any XML tags, and translates it there would be no need to show the extra dialog with the "Replace" button, they can just paste the translated text over the selection. That dialog allowing you to replace the translated content is handy if the initial content contains various XML elements so the translated content needs to be massaged back in the original XML structure.

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 9/3/20 6:37 PM, Jonathan Hanna wrote:

Hi Radu,

Thank you for bringing this great feature to our attention! I just tried using it and was able to get it to work when selecting all the content in a topic or all the content in a section. However, the Translation using Google Translate dialog does not show up when I select only a single block of text (such as all the text in a <p> element). Is that the intended behavior or is there a bug?

Regards,
Jonathan


Re: New Oxygen add-on to help translators

Jonathan Hanna
 

Hi Radu,

Thank you for bringing this great feature to our attention! I just tried using it and was able to get it to work when selecting all the content in a topic or all the content in a section. However, the Translation using Google Translate dialog does not show up when I select only a single block of text (such as all the text in a <p> element). Is that the intended behavior or is there a bug?

Regards,
Jonathan


Re: Are you using <data-about>?

glenn emerson
 

I’ve never used it either, though I have used <data> quite a bit.

On Sep 1, 2020, at 5:02 PM, ekimber@... wrote:

I have never used data-about, even when I thought it would be a useful thing to do.

Basically, the authoring overhead required to make the authoring of data-about practical coupled with the need to implement whatever data-about processing you might need means that the implementation cost almost (or always) outweighs any potential value from a metadata representation standpoint.

In addition, because the TC has expanded the places where <data> is allowed, it's largely removed the need to be able to point at something within a topic or map in order to impose metadata on to it (the intended purpose of data-about).

I can imagine some use case where you might want to use DITA to impose metadata onto non-DITA objects but doing so with DITA and data-about would be so one-off and outside the mainstream of any existing metadata infrastructure that I can't see it ever being done. And even without data-about you can get the same effect with topicrefs that contain the metadata they want to impose (which is basically what subject scheme does).

I think data-about falls into the category of DITA features that were a good idea at the time or were suggested by design symmetry and completeness but where overtaken by practical realities and other technologies.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 9/1/20, 4:24 PM, "Kristen James Eberlein" <main@dita-users.groups.io on behalf of @keberlein> wrote:







At today's DITA Technical Committee meeting, we discussed the
possibility of removing <data-about> from DITA 2.0. The
rationale for removal is:


* The spec element-reference topic is extremely convoluted.
Neither spec editors (Robert Anderson and I) has been able to
rework it and make it comprehensible.

* There is nothing done with <data-about> that cannot be
done with <data>.

* We suspect that the element is little used -- and if used, is
usually misused.


So, our query to the larger DITA-using community:


* Does your implementation use the <data-about> element?

* (If the <data-about> element is used) What are the use
cases for <data-about>? Please note that these should be
actual, not theoretical.


As always, thanks for your participation in the dita-users list.

--
Best,
Kris

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











relationship beteween 3 types of documents for the same concept

Weiwu Zhang
 

We have a tech called TokenScript which has concepts that is

- Defined in XML by Token Issuers
- Presented to the web developers as JavaScript

For example, a concept called Card will have 3 pages of document

𝑎. What is a Card, where to use it

𝑏. How is it defined in XML (interesting to the XML author)

𝑐. How is it used by JavaScript web developers (interesting to the web
developer who takes the XML and use it as a library)

All of the three are about the same thing, but each of them is
included in a different dita map.

My question is what's the best practise to connect these 3 types of
document?

Right now,

𝑎 is in a concept called Card.dita
𝑏 is in a topic called card_element.dita
𝑐 is in a topic called manipulate_card_in_JavaScript.dita

They are connected in a rudimentary way: in 𝑎, there are two <note>
elements that links to the corrisponding document 𝑏 and 𝑐; and there
are <notes> in 𝑏 and 𝑐 linking back to 𝑎.

With a bit of Google search I found the <audience> tag which is
relevant, but it seem to be a way to tag information by audience,
doesn't work to linking documents of one same concept for different
audiences.

These days I always got the right answers from this mailing list so thanks
in advance!

P.S. I feel DITA itself need such kind of "linking mechanism". Sometimes,
in the Style Guide I found a dita document page about where to use it,
then I need to do a second Google search to find out how to use it.
Maybe there are mechanism to do so, but can't be used because Style
Guide is from different DITA repository than the how-to information.

Regards
Weiwu Z.


Re: Can LwDITA MDITA format transclude "normal" dita content?

Weiwu Zhang
 

On Mon, 31 Aug 2020, Radu Coravu wrote:

If you open it in a DITA editing tool and validate it, there are about 4
problems with it:
1) The element <div> is not accepted in a Lightweight DITA topic. Only the
following elements are allowed:
2) The @conref element is allowed only on these Lightweight DITA elements:
3) The @type element is not allowed on the <div> element.
4) When you conref in a DITA topic you need to conref to an equivalent DITA
element from the target topic. So a DITA <div> may conref to another <div>
located in another DITA topic, not to a <concept> element.
Thanks Radu. Having fixed all 4 problems now the document works!

changing the element to <section>, now conref from a <section> to a <section> and dropped @type (as referring to XDITA doesn't require specifying type).

Regards
Weiwu Z.


New Oxygen add-on to help translators

Radu Coravu
 

Hi everyone,

Over the course of this summer one of our interns, Mircea Badoi, worked on a free Oxygen XML add-on designed to help translating XML content.

Starting from yesterday, the add-on is available for Oxygen vesions 21.1 or newer in our default add-on repository. If you want to install it, you can use the Oxygen main menu "Help->Install new add-ons", choose the default Oxygen add-on update site and you will find an add-on named "Translator Helper (Experimental)" in the list.

The add-on has two main features:

  1. You can translate content using Google Translate to various languages:
    • Select the content to translate in the Author visual editing mode. You can also select the entire document contents. DITA topics are small so you can select the entire topic contents.
    • Right click. Select "Google Translate into" and choose the target language.
    • Copy the translated content from the opened web page.
    • Click Replace in the Oxygen Translate using Google Translate dialog that showed up. The original content should now be replaced with the translated content, the original element structure and attributes should remain unchanged.
    • In addition you can choose to show the original document content in the Translator Helper side view. This will allow you to correct the translation further by looking at the original text and the translated text side by side.
  2. You can see the original content side by side with the content that you are translating, so you can translate correctly and easy by right clicking in the Author visual editing mode and invoking the Show current content in side view action.

So I hope you will enjoy the add-on, if you have questions or improvement requests, they are as usual welcomed. One area in which the plugin may be useful is for example if you want to quickly demo to a customer how a topic written in English would look like in other languages like Japanese Chinese, French, German, Russian, etc.

Regards,

Radu

Radu Coravu
Oxygen XML Editor


Re: error in producing troff output

Radu Coravu
 

Hi,

I had the changes to make the plugin work on my side, as part of the DITA Open Toolkit bundled with Oxygen XML Editor, so I just added them back to the original project.

About the issue you added, I'm not very familiar with troff output but maybe someone else will be able to help. Maybe as a workaround for the problem instead of a DITA <section> you could insert another <concept> element after the end of the </conbody> in the first concept.

Regards,
Radu

Radu Coravu
Oxygen XML Editor

On 9/3/20 3:16 AM, Weiwu Zhang wrote:


On Wed, 2 Sep 2020, Radu Coravu wrote:

I added an issue on the plugin's GitHub issues list to make it compatible
with DITA OT 3.5:

https://github.com/dita-ot/org.dita.troff/issues/5
Impressive! The issue is solved in 24 hours.

Following what you did I filed another issue about a bug in the troff output that concatenated two unrelated paragraphs. Hope that the project responds.


Re: error in producing troff output

Weiwu Zhang
 

On Wed, 2 Sep 2020, Radu Coravu wrote:

I added an issue on the plugin's GitHub issues list to make it compatible
with DITA OT 3.5:
https://github.com/dita-ot/org.dita.troff/issues/5
Impressive! The issue is solved in 24 hours.

Following what you did I filed another issue about a bug in the troff output that concatenated two unrelated paragraphs. Hope that the project responds.


Re: proper way to do trouble-shooting containing console commands

Weiwu Zhang
 

On Wed, 2 Sep 2020, danlittman via groups.io wrote:

Weiwu, just want to point out before you release this error message
that the <p> </p> says singing, instead of signing. _._,_._,_
Weiwu here. Thank you! And thank you everyone who proposed the new
element.


Re: proper way to do trouble-shooting containing console commands

danlittman
 

On Tue, Sep 1, 2020 at 03:35 AM, Weiwu Zhang wrote:
<condition>
<title>Wrong key used for signing</title>
<p>Error on the singing</p>
</condition>
Weiwu, just want to point out before you release this error message that the <p> </p> says singing, instead of signing.


Re: error in producing troff output

Radu Coravu
 

Hi,

The readme for the DITA to Troff plugin says:

https://github.com/dita-ot/org.dita.troff

Compatibility

  • DITA-OT 3.1
So it no longer works with DITA OT 3.5.x. Maybe you can download an older version of the DITA OT publishing engine (3.1) and try to use this plugin with it.

I added an issue on the plugin's GitHub issues list to make it compatible with DITA OT 3.5:

https://github.com/dita-ot/org.dita.troff/issues/5

Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 9/1/20 4:30 PM, Weiwu Zhang wrote:
Following the guide from here:

https://www.dita-ot.org/plugins#!org.dita.troff

I installed the plugin on dita-ot 3.6

$ dita install org.dita.troff
Added org.dita.troff

and attempted to make troff out of a file:

$ dita --input=a_topic.dita --format=troff
Error: Includesfile /tmp/temp20200901230030922/${fullditatopicfile} not found.

No luck replacing the dita file with a ditamap either. It is from a project which already works with other output (html5/pdf).

Any hint how to proceed on / file bug?

Regards







  


Re: Are you using <data-about>?

ekimber@contrext.com
 

I have never used data-about, even when I thought it would be a useful thing to do.

Basically, the authoring overhead required to make the authoring of data-about practical coupled with the need to implement whatever data-about processing you might need means that the implementation cost almost (or always) outweighs any potential value from a metadata representation standpoint.

In addition, because the TC has expanded the places where <data> is allowed, it's largely removed the need to be able to point at something within a topic or map in order to impose metadata on to it (the intended purpose of data-about).

I can imagine some use case where you might want to use DITA to impose metadata onto non-DITA objects but doing so with DITA and data-about would be so one-off and outside the mainstream of any existing metadata infrastructure that I can't see it ever being done. And even without data-about you can get the same effect with topicrefs that contain the metadata they want to impose (which is basically what subject scheme does).

I think data-about falls into the category of DITA features that were a good idea at the time or were suggested by design symmetry and completeness but where overtaken by practical realities and other technologies.

Cheers,

E.

--
Eliot Kimber
http://contrext.com


On 9/1/20, 4:24 PM, "Kristen James Eberlein" <main@dita-users.groups.io on behalf of @keberlein> wrote:







At today's DITA Technical Committee meeting, we discussed the
possibility of removing <data-about> from DITA 2.0. The
rationale for removal is:


* The spec element-reference topic is extremely convoluted.
Neither spec editors (Robert Anderson and I) has been able to
rework it and make it comprehensible.

* There is nothing done with <data-about> that cannot be
done with <data>.

* We suspect that the element is little used -- and if used, is
usually misused.


So, our query to the larger DITA-using community:


* Does your implementation use the <data-about> element?

* (If the <data-about> element is used) What are the use
cases for <data-about>? Please note that these should be
actual, not theoretical.


As always, thanks for your participation in the dita-users list.

--
Best,
Kris

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


Re: Are you using <data-about>?

Lionel Moizeau
 

Hi 
I do not, I was actually wondering what it was for...

Lionel Moizeau

On Tue, Sep 1, 2020 at 11:24 PM Kristen James Eberlein <kris@...> wrote:

At today's DITA Technical Committee meeting, we discussed the possibility of removing <data-about> from DITA 2.0. The rationale for removal is:

  • The spec element-reference topic is extremely convoluted. Neither spec editors (Robert Anderson and I) has been able to rework it and make it comprehensible.
  • There is nothing done with <data-about> that cannot be done with <data>.
  • We suspect that the element is little used -- and if used, is usually misused.

So, our query to the larger DITA-using community:

  • Does your implementation use the <data-about> element?
  • (If the <data-about> element is used) What are the use cases for <data-about>? Please note that these should be actual, not theoretical.

As always, thanks for your participation in the dita-users list.

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