Re: Basic question about Structured Frame
Rick Spiegel wrote: My company is considering switching to Structured Frame to solve our current problems with content reuse, and I have a question, the answer to which, to me, holds the key as to whether or not Structured Frame is the answer we're looking for. With all due respect, I would strongly advise that you get someone to help you with this. Structured data may solve your problems, but FrameMaker is only one part of the solution. Basing your data on an application? I've seen organisations lose a year by starting at the wrong end of the problem. The question is this: if our documents were authored in Structured Frame, could we use the same topic at a heading 1 level in one document and at a heading 2 level in another document? If so, in a very general way (no need to write a small book!) how does this work? You might create fragments of XML data in FrameMaker and manage them on your file system (or something more complex if necessary). Then create configuration documents that describes how to combine the fragments. Then pull it all together using XSLT and pour the data into FrameMaker to paginate. In this scenario, FrameMaker plays a significant role, but the critical stuff has nothing to do with FrameMaker. You'll likely be told that DITA will solve your problems because the learning curve is low. In my opinion, you would be better off either getting a consultant in or settling in for some serious learning. There are no shortcuts to doing structured data properly - you just delay the pain. Good luck, Marcus Carr ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Basic question about Structured Frame
The question is this: if our documents were authored in Structured Frame, could we use the same topic at a heading 1 level in one document and at a heading 2 level in another document? If so, in a very general way (no need to write a small book!) how does this work? Hi Rick, it depends entirely on your DTD/Schema, but if designed correctly, it's easy to do. For example, assume your DTD has a section element, which contains a title and para: section titleMy Section/title paraSome content./para /section You could allow the section element to be used in other sections, or at the top level of a chapter: chapter section titleMy Section/title paraSome content./para section titleMy Second Section/title paraSome more content./para /section /section Using the level rules in your Frame EDD, you could format the title according to its level. For an example that implements this concept, see the recursive section element in DocBook: http://www.docbook.org/tdg5/en/html/section.html If you have a copy of Frame, you can open a new, blank DocBook document, and play around with nested sections to get an idea. Drew Avis - Technical Writer QNX Software Systems Ltd. Ottawa, Ontario ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Basic question about Structured Frame
Rick asked, if our documents were authored in Structured Frame, could we use the same topic at a heading 1 level in one document and at a heading 2 level in another document? The short answer is Yes. The longer answer is yes, if you set up your EDD (and DTD) properly. What you need is to use the same element for all of your headings, for example title or heading. Then, in your EDD, define how that element is formatted based on context. Example (using DITA): If context is: (topic | concept | task | reference | example | section) Count ancestors named: concept | task | reference | example | section If level is: 1 Use paragraph format: Heading1 If level is: 2 Use paragraph format: Heading2 If level is: 3 Use paragraph format: Heading3 Bottom line: Use Heading1 if there is only a single concept or task or reference or example or section element as the parent/grandparent/whatever (ancestor) of the heading. Use Heading2 if the topic is nested in 2 of any of the following: concept or task or reference or example or section. And so on... Example (using a custom DTD/EDD): Count ancestors named: Section If level is: 0 Use paragraph format: Title1 If level is: 1 Use paragraph format: Heading1 If level is: 2 Use paragraph format: Heading2 If level is: 3 Use paragraph format: Heading3 Bottom line: Use Title1 if there are no sections as ancestors of this topic (for example, a Chapter). Use Heading1 if there is only a single section element as the parent/grandparent/whatever (ancestor) of the heading. Use Heading2 if the topic is nested in 2 of sections. And so on... In your example (using the same topic at a heading 1 level in one doc and at a heading 2 level in another doc), you would simply copy whatever parent element that contained the heading and the content, such as a section element or a topic element, into your new document ***in a place where the section or topic element is valid***. Your EDD would then take care of the formatting, not only of the heading, but also of anything else that needed to be formatted differently based on context and your EDD definitions. HTH, M Marsha Lofthouse Motorola, Inc., Public Safety Applications North America Government Commercial Markets Division Boulder Design Center [EMAIL PROTECTED] 303.527.4178 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
