Skip to main content
1-Visitor
November 10, 2011
Question

Arbortext Editor 5.3 M111 support to Schematron?

  • November 10, 2011
  • 7 replies
  • 1377 views

Hi Adepters,


Does Arbortext Editor 5.3 M111 has support to Schematron? Or


Your suggestions in implementing the same are appreciated.


My requirement of Schematron implementation, is to run as a follow on process when “check completeness” toolbar option is executed, and any schematron errors should show up in “Arbortext Editor Completeness Check” window.


Thanks in advance,


Suresh.

    7 replies

    1-Visitor
    November 11, 2011

    Hi Suresh,


    Schematron support came in version 6.0, if you have active support & maintenance you can go to the HelpCenter and do a search on Schematron for details.


    There may be a way to support it in version 5.x with customisation, for examplein the S1000D solution there was Schematron capability pre 6.0


    Cheers


    Pete

    1-Visitor
    November 14, 2011

    Hi Pete,


    Thanks for your response.


    We are currently using Arbortext Editor 5.3M111.


    Could you please provide me a pointer to Schematron Customization?


    I could not able to find S1000D solution in my Arbortext Editor installed location.



    Thanks in advance,


    Suresh.

    1-Visitor
    November 14, 2011

    Hi Sudesh,


    I'm afraid I've no idea where you can start with customising Schematron in pre 6.0, someone more technical on this forum may be able to help.


    In regards to the support of Schematron in the S1000D solutions, please contact - for advice.


    Cheers


    Pete

    1-Visitor
    November 15, 2011

    Thanks for your response Peter.


    Can someone in the group throw some light regarding customization of Arbortext Editor 5.3M111 for Schematron Support.

    Suresh

    1-Visitor
    November 16, 2011
    First, the lecture. I'd start by considering carefully the investment
    of time and effort that you're considering, as it is far from trivial.
    This functionality already exists in a newer version of the software
    and the version you're on is already officially unsupported by the
    vendor, so it's worth considering putting that effort towards an
    upgrade process.

    That said, I understand that sometimes, an upgrade simply isn't an
    option due to application requirements (third party tool version
    dependencies or customer requirements) or upgrade costs
    (reverification of the new version, upgrade/testing of customizations,
    etc.).

    If adding Schematron to 5.3 is the way you decide to go, I'd first
    look at the support in 6.0, to see how it works. This may save you
    some design work and better align you for a more seamless transition,
    if you later upgrade to a version that has this support built-in.

    Aside from that, I haven't looked much at Schematron for a while, but
    I believe there is at least one implementation that is built almost
    entirely on top of XSLT. Editor provides good support for XSLT, so it
    probably wouldn't be terribly difficult to integrate something like
    that. Then again, I do a lot of XSLT, so I may be biased. Editor
    provides many options and avenues for customization, so the best
    option really depends on the skill sets you have to put to work on the
    problem.

    -Brandon Smiley Happy


    On Tue, Nov 15, 2011 at 5:36 PM, Venkata Suresh Maddela
    <-> wrote:
    > Thanks for your response Peter.
    >
    > Can someone in the group throw some light regarding customization of
    > Arbortext Editor 5.3M111 for Schematron Support.
    >
    > Suresh
    >
    > -----End Original Message-----
    1-Visitor
    November 16, 2011
    Thanks Brandon for your inputs.
    I will bring up with my management regarding upgrading suggestion.
    May need some help from the group, if I have no option that no customize
    the current version.

    Thanks once again,
    Suresh.

    On Wed, Nov 16, 2011 at 12:05 PM, Brandon Ibach <
    brandon.ibach@single-sourcing.com> wrote:

    > First, the lecture. I'd start by considering carefully the investment
    > of time and effort that you're considering, as it is far from trivial.
    > This functionality already exists in a newer version of the software
    > and the version you're on is already officially unsupported by the
    > vendor, so it's worth considering putting that effort towards an
    > upgrade process.
    >
    > That said, I understand that sometimes, an upgrade simply isn't an
    > option due to application requirements (third party tool version
    > dependencies or customer requirements) or upgrade costs
    > (reverification of the new version, upgrade/testing of customizations,
    > etc.).
    >
    > If adding Schematron to 5.3 is the way you decide to go, I'd first
    > look at the support in 6.0, to see how it works. This may save you
    > some design work and better align you for a more seamless transition,
    > if you later upgrade to a version that has this support built-in.
    >
    > Aside from that, I haven't looked much at Schematron for a while, but
    > I believe there is at least one implementation that is built almost
    > entirely on top of XSLT. Editor provides good support for XSLT, so it
    > probably wouldn't be terribly difficult to integrate something like
    > that. Then again, I do a lot of XSLT, so I may be biased. Editor
    > provides many options and avenues for customization, so the best
    > option really depends on the skill sets you have to put to work on the
    > problem.
    >
    > -Brandon Smiley Happy
    >
    >
    > On Tue, Nov 15, 2011 at 5:36 PM, Venkata Suresh Maddela
    > <-> wrote:
    > > Thanks for your response Peter.
    > >
    > > Can someone in the group throw some light regarding customization of
    > > Arbortext Editor 5.3M111 for Schematron Support.
    > >
    > > Suresh
    > >
    >
    16-Pearl
    November 25, 2011
    Sorry to chime in on an old thread, just clearing out my emails.



    If you didn't already know, Suresh, you can get a Schematron implementation
    in XSLT and run this whichever way you like: