Metadata and attributes for topicref
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 105
- Joined: Thu Jan 20, 2022 12:36 pm
Metadata and attributes for topicref
Hello,
I feel confused about the attributes that could be applied to topics. Are they only intended for filtering or is it possible to use them as metadata declaration?
For instance, in the map below, I apply an audience attribute to a topicref. So far so good. I specified the attribute lockmeta for the map and I expect my topic to receive the expert value. However, this value isn't transmitted to the topic and first metadata declaration precedes, i.e. the topic receives the value novice?
I presume that I confuse the use of attributes (audience, platform, otherprops) used for filtering with proper metadata declarations. If so, I guess the solution to declare and apply specific metadata to my topic would be with a prolog.
A second question that is still connected to this interrogation concerns the distinction between:
and
Do they achieve the same purpose?
Thank you so much for your feedback.
I feel confused about the attributes that could be applied to topics. Are they only intended for filtering or is it possible to use them as metadata declaration?
For instance, in the map below, I apply an audience attribute to a topicref. So far so good. I specified the attribute lockmeta for the map and I expect my topic to receive the expert value. However, this value isn't transmitted to the topic and first metadata declaration precedes, i.e. the topic receives the value novice?
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
<title>Main Map for Novice Audience</title>
<topicmeta lockmeta="no">
<navtitle>Simple and easy</navtitle>
<linktext>Insert link text here</linktext>
<shortdesc>Short description here</shortdesc>
<audience type="novice"/>
<keywords>
<keyword>Dummy-1</keyword>
</keywords>
</topicmeta>
<topicref href="topic1.dita" audience="expert"/>
</map>
A second question that is still connected to this interrogation concerns the distinction between:
Code: Select all
<audience>novice</audience>
Code: Select all
<audience type="novice"/>
Thank you so much for your feedback.
------
Gaspard
Gaspard
-
- Posts: 9452
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Metadata and attributes for topicref
Hi,
Indeed the "@audience" attribute is a profiling attribute used mostly for filtering, it does not propagate inside the target topic.
About the "<audience>" element, I have not used it much but here's the specs:
https://www.oxygenxml.com/dita/1.3/spec ... ience.html
It needs to have empty text contents, so you can set values only to its allowed attributes.
You can set the <audience> element also directly on a topicref:
About how the <audience> element should cascade from the map or topicrrefs to the referenced:
https://www.oxygenxml.com/dita/1.3/spec ... adata.html
Regards,
Radu
Indeed the "@audience" attribute is a profiling attribute used mostly for filtering, it does not propagate inside the target topic.
About the "<audience>" element, I have not used it much but here's the specs:
https://www.oxygenxml.com/dita/1.3/spec ... ience.html
It needs to have empty text contents, so you can set values only to its allowed attributes.
You can set the <audience> element also directly on a topicref:
Code: Select all
<topicref href="topics/introduction.dita">
<topicmeta>
<audience type="administrator"/>
</topicmeta>
</topicref>
https://www.oxygenxml.com/dita/1.3/spec ... adata.html
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service