Hi,
I am still a bit unsure of Tridion's support of lack of support for standard DITA condition profiling attributes (audience, platform, product etc.). If I use them, how will they be handled by the SDL processors?
Also if I use the Content Importer to import DITA content that uses these, they are converted to ishconditions. Can this conversion be turned off?
Any feedback around this topic is greatly appreciated,
Regards,
Ann
Ann,
I am not speaking from experience, but I wouldn't expect that SDL had somehow removed support for standard DITA profiling. The profiling attributes are like any other attributes in terms of XML... just names and values as defined in the DITA Specification. I think most TDocs users choose to use the CMS condition management and ishconditions because they believe that they are easier to manage than DITAVALs and the OT, and can be applied to a much broader range of markup and structure. If your need to apply profiling any more sophisticated than @audience, @platform, @product, @otherprops, @rev (DITA 1.2/1.3), and @deliveryTarget (DITA 1.3), you need to specialize @props. With ishconditions, you don't need to deal with specializing your DTDs.
I would think that Content Importer could be configured to not auto-convert to ishconditions. But I don't know; it would be nice if SDL could comment.
If using standard DITA profiling, the profiling attributes are just going to get passed through to the DITA XML output (resolved with all TDocs artifacts removed), and then it's up to the DITA-OT to process for profiling using the DITAVAL you reference. This is not SDL functionality; it's the DITA-OT whether you use TDocs or not.
If I am wrong about any of this, I'd love to be corrected and better informed! I just say all this because it wouldn't make sense to me for a "DITA" CMS to disable standard DITA markup or OT functionality.
Thank you Jay for your reply before. I apologise that I got sidetracked from that research and am just back to it now. On rereading your detailed reply above, your mention of the DITAVAL file resonates with the challenge I am facing now. The sample scenario is that a team is coming from using a pre-defined DITAVAL file which can be created per category and it lists the instructions (include or exclude) for each relevant condition. What approach can this team use in SDL Publication Manager to maintain this type of shareable resource where they maintain all their condition rules for a given category which may be a large collection of rules that they don't want to have to recreate for every publication?
Am I wrong, or does this seem more challenging in Publication Manager where you can't apply a DITAVAL file or something similar?
Thanks again,
Ann
Thank you Jay for your reply before. I apologise that I got sidetracked from that research and am just back to it now. On rereading your detailed reply above, your mention of the DITAVAL file resonates with the challenge I am facing now. The sample scenario is that a team is coming from using a pre-defined DITAVAL file which can be created per category and it lists the instructions (include or exclude) for each relevant condition. What approach can this team use in SDL Publication Manager to maintain this type of shareable resource where they maintain all their condition rules for a given category which may be a large collection of rules that they don't want to have to recreate for every publication?
Am I wrong, or does this seem more challenging in Publication Manager where you can't apply a DITAVAL file or something similar?
Thanks again,
Ann
Translate
