FW: Use of relationship tables

Hi -- My 2 cents. If you plan to be the person who updates all the reltables in perpetuity, then using <reltable>s probably makes sense. If writers who you do not know will be updating/maintaining them, it's more of a crap shoot. Some writers easily grok the logic, many do not. A specialized DITA map may be the way to go from a maintenance point of view. Stan On Thu, Dec 21, 2023 at 11:23 AM Kristen James Eberlein < [email protected] > wrote: Hi, DITA TC colleagues. I am designing information architecture and markup for some Mayo content. It s a library of content called Ask Mayo Expert, and the targeted audience is clinicians. Some of the simplest content is about particular medical condition, for example, bipolar disorder. Here is a screen capture of how the content is currently presented: Here s an explanation of the areas that I ve marked: Navigation of the publication, easily handled with a DITA map that references topics such as Symptoms (adult). As a user clicks on different nodes in the navigation, what is displayed in the central pane changes but the top navigation pane (include #2) does not change. Links that are hand-curated by subject matter expert. The items grouped under Guidelines & Resources tend to be links to external web sites, and the items grouped under Patient Education tend to be PDFs developed by Mayo patient education specialists for different branches of the clinical practice at Mayo. These links are applicable to ALL of the Bipolar disorder content. I, of course, immediately thought of expressing these relationships with a <reltable>. But when I looked through the spec, it was pretty clear that all our element-reference topics are written with focus on using relationship tables to define relationships between individual topics, rather than relationships between a publication and external links. A couple of questions: Are we being too old-school in how we define relationship tables in the spec? There will be custom processing (of course) for the Mayo DITA source, so from that perspective, I can broaden the usage of a relationship table. But I am urging that all Mayo transformations begin with using base DITA-OT transformations. Might I be better off with a specialized DITA map that had specific structures for Guidelines & Resource and Patient Education, rather than using a relationship table? Thoughts very much welcome. Kristen James Eberlein Content Engineer Health Education & Content Services 507-293-0006 [email protected] My pronouns are she/her/hers.