What are ramifications on the Oxygen plugin if Schematron, Constraints, and Subject Schemes are integrated into Oxygen?

From the perspective of the SDL tools, what are the ramifications of implementing each of these features?

My feeling is that a Schematron and some quick fixes (QFX) won't affect the Oxygen plugin...but not entirely sure.

Constraints though I think are implemented via DTDs, which I'm sure would affect the SDL plugin for Oxygen.

Lastly, my feeling is that subject schemes probably wouldn't affect the plugin.

I need an expert answer to these questions about the affects of integrating a Schematron, a set of constraints, and a set of subject schemes on the SDL plugin for Oxygen.

 

Thanks for any help on this.

Jerry

  • I'd also be interested in an answer to this question, if someone at SDL can comment or someone has tried it.
  • We went ahead and implemented a Schematron, quick fixes, and subject schemes. These tools have not created any issues for us with regard to impacting the oXygen plug-in. They co-exist fine.

    We've not implemented constraints. So, I have nothing to add on that point. I still feel in my gut though that, because constraints affect the DTD mix, they likely would affect the SDL plugin for Oxygen. But, I really don't know.

    HTH.

    Jerry
  • Forgive me for a late reply to this thread, but we're looking at how to implement a similar setup in Oxygen as well, and I was curious how easy or difficult of a process this was for you. Do you have everything synchronized through SDL KC to the client PCs? Any suggestions or advice?

    Thanks in advance for your help. I appreciate it.
  • Because we didn't have sufficient skills on our team, we hired a contractor (Scott Hudson) to develop the SCH, quick fixes, and pick lists (via subject schemes). Installing those documents was easy. He even created a batch of test files for us, a "fail" test and a "pass" test for each rule: Two test files for each business rule.

    To install the Schematron and quick fixes, you need only to place them at a network location that's accessible to all writers. Each writer would need then to configure their personal instance of Oxygen to pull in the SCH. They can do that via Options > Preferences > Document Type Association. In that dialog, you'd need to create a new association for business rules affecting topics and a new association for business rules affecting maps. On the Validation tab, select the scenario (topic or map, depending) and then click the configure icon (looks like a wrench). Add a new file type of XML document and create an entry under Schema that points to your Schematron document.

    We did nothing with SDL tools to get this implemented. We simply modified the associations that oxygen uses. If we were more skilled with oxygen, I'm sure there are ways to get SCH documents to universally impact all authors so that you don't have to ensure each author makes these changes.

    If you implement constraints, you'd have work to do to get the SDL DTDs modified to integrate the constraints.

    HTH
    Jerry
  • Thanks Jerry. I set up the schematron yesterday, and it works as beautifully as you described. Going to work on the quick fixes next. Greatly appreciate your help and insight.
  • You're welcome. Have fun! SCH and QFX really do enhance the authoring experience. Realize though that SCH has its weaknesses and will likely give you some frustrations. Just realize that SCH does what it can do pretty well but don't push it too hard :-). (I had to give up on some of my business rules cuz of their complexities.)