TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: oXygen XML editor for XSDs and (potentially) tech doc formats: Mac or Win?
Subject:Re: oXygen XML editor for XSDs and (potentially) tech doc formats: Mac or Win? From:Michael Hopwood <Michael -dot- Hopwood -at- Gleif -dot- org> To:Alan Houser <arh -at- groupwellesley -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 27 Jul 2016 16:49:28 +0000
Hi Alan,
Correct.
I got the schema docsâ content and formatting looking maybe 60-80% just using
- annotation/documentation elements (for single-sourcing goodness) and
- a little bit of HTML (plenty to enable a minimum semantics as I mentioned below and even a nested list suitable for exporting to shiny Word docs for review)
It's been a while since I've used it, but check out oXygen's schema
documentation generator: "Tools>Generate Documentation>Generate Schema
Documentation." The online help for the tool is pretty good.
I would generally favor the schema "annotation" and "documentation"
elements over free-form XML comments for what you're doing.
HTH!
-Alan
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532
On 7/26/16 11:45 AM, Michael Hopwood wrote:
> Hello Alan, colleagues,
>
> firstly thanks to Alan for this excellent feedback â I am now looking at a (valid) draft XML schema writing with oXygen in record time.
>
> My follow-up question is for the whole list, because itâs not necessarily specific to oXygen:
>
> Before I reinvent any wheels, could anyone share some best practice of single-sourcing the XML schema documentation?
>
> Status quo is a lot of freehand <! - - comments - - >in the XML schema itself. Not very reusable or easy to keep updated.
>
> Iâm planning on going through them all to at least chunk them down into e.g.
>
> - element name
> - cardinality
> - content specification/datatype
> - business rules beyond schema validation
>
> The idea is to then update the comments simultaneously to changes to the schema content, and export the XML comments into some text format before editing and applying formatting for review. There will be a few cycles of this at least.
>
> But are there some good tips and tricks, maybe using oXygen, maybe generally part of XML, like using <annotation> or some XSLT someone might know of (I found a lot of dead links while searching for that).
>
> Iâm afraid I need something pretty simple, like dumping a table of extracted comments for use in Word - learning DocBook etc. will have to wait til next year once the schemaâs in use and stable.
>
> Best wishes,
>
> Michael
> Technical Writer, GLEIF
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com