Hi Radu<div><br></div><div>I agree that, if the topic type changes, you don't have to remember to update @type on the topicref. However, I don't think that topic types changes that often, also because it's kinda hard to change topic types afterwards, because you also have to change the child elements, for example conbody and refbody. In my experience, it's easier to create a new topic and then just copy/paste the content into the <body> (or conbody, taskbody, refbody) of that topic.</div>
<div><br></div><div>My use case:</div><div><br></div><div>I'm not using a CMS. I add topics to my ditamap in various ways. The easiest one is to just create my topics first and then select the files in Windows Explorer and drag them into my ditamap. I then have to remember to add type="concept" because the DITA Open Toolkit also uses this information for the "generated labels" for related topics (using reltable). For example, if you have related tasks and you have specified type="task", the generated label will read "Related tasks", which is good, because this helps the reader to navigate to the correct type of topic. If you didn't specify the @type attribute, the generated label will read "Related information", which is too vague for me.</div>
<div><br></div><div>Maybe we can cross-post this conversation to the dita-users group and see what other people think?</div><div><br></div><div>Kind regards</div><div><br></div><div>Yves</div><div><br></div><div><br><br><div class="gmail_quote">
On Thu, Aug 16, 2012 at 2:02 PM, Oxygen XML Editor Support <span dir="ltr"><<a href="mailto:support@oxygenxml.com" target="_blank">support@oxygenxml.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Yves,<br>
<br>
I consider that it's more flexible not to add the @type value when a<br>
topic ref is inserted.<br>
In this way, if the type of the referenced topic changes (it was a task<br>
and then you change it to be a concept) then you do not need to remember<br>
to also update the <topicref>.<br>
What is your usecase? Do you have a CMS which requires the @type to be<br>
added?<br>
<br>
The DITA 1.2 specs is very vague:<br>
<br>
> When a referencing element is first added to or updated in a document, DITA aware editors may, but are not required to, set the type attribute value based on the actual type of a referenced DITA topic.<br>
<br>
Regards,<br>
Radu<br>
<br>
Radu Coravu<br>
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger<br>
<a href="http://www.oxygenxml.com" target="_blank">http://www.oxygenxml.com</a><br>
<div><div class="h5"><br>
On 8/16/2012 1:07 PM, Yves Barbion wrote:<br>
> Hi group<br>
><br>
> When I add a topicref to a DITA map, I see that the @type attribute is<br>
> left unspecified. It would be nice if the @type attribute would then<br>
> automatically be filled in, depending on the information type of the<br>
> topic. For example, when I add a topicref to a task topic, the @type<br>
> attribute would automatically be type="task".<br>
><br>
> Is this possible or is this a new feature request?<br>
><br>
> Thanks<br>
><br>
> --<br>
> Yves Barbion<br>
</div></div>> <a href="http://www.scripto.nu" target="_blank">www.scripto.nu</a> <<a href="http://www.scripto.nu" target="_blank">http://www.scripto.nu</a>><br>
><br>
><br>
> _______________________________________________<br>
> oXygen-user mailing list<br>
> <a href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a><br>
> <a href="http://www.oxygenxml.com/mailman/listinfo/oxygen-user" target="_blank">http://www.oxygenxml.com/mailman/listinfo/oxygen-user</a><br>
><br>
_______________________________________________<br>
oXygen-user mailing list<br>
<a href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a><br>
<a href="http://www.oxygenxml.com/mailman/listinfo/oxygen-user" target="_blank">http://www.oxygenxml.com/mailman/listinfo/oxygen-user</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Yves Barbion<br><a href="http://www.scripto.nu">www.scripto.nu</a><br>
</div>