Thanks for you efforts.
Regards,
Patrik

Hi Radu,

thanks for the hint. I could just replace my include-schema with extends and it worked the same way. Thus, my include-schema is obsolete.

Regards,
Patrik

Hi Stefan, there's no point in using variables in the storage path since this path is no parameter that is stored in the settings or something. It is simple a location on the harddisk. To share frameworks with other computers you have to share the content of the specific frameworks folder and config...

Hi Stefan,

I solved the problem by using an environment variable that needs to be set on every machine (not only for oXygen). Then you can refer to it with ${env(VariableName)}/OxygenFrameworks.

Regards,
Patrik

Hi Adrian, this seems to work only for functions within the saxon namespace. I added the folowing code for testing: <function> <name>saxon:test-saxon</name> <namespace>http://saxon.sf.net/</namespace> <signature> <return>xs:string*</return> </signature> <description xml:space="preserve">Te...

I managed to make it work by modifying the schematron xslt scripts. If someone is interested I'd gladly share the code. (Some more modifications were neccessary.)

It might as well me a nice feature to add "schema aware" as a schematron configuration parameter to oxygen.

Regards,
Patrik

Hi, I have implemented some custom functions for saxon xslt and will add some custom instructions as well. Is there any way I can add these to the content completion? I noticed that the custom functions in the saxon namespace are already included while the saxon instructions are not!? Thanks and reg...

Hi, I had a similar problem with a growing schematron file I'd like to split. Since it seems like there wont be a new schematron version any time soon I modified the files included in oxygen myself. Maybe you could consider adding this to the oxygen distribution as well: customized-iso-schematron.xs...

I figured out why it was not working with schematronDispatcher.xsl: When doing schematron validation oxygen does not use the file schematronDispatcher.xsl directly but oXygenSchematronDispatcher.xsl. And this file imports schematronDispatcher.xsl with a relative path and, thus, within the oxygen.jar...

After diving a little deeper into schematron I found out that it's actually quite easy to add the location information to the messages. I simply added the following code to the template "process-message": <xsl:if test="$show-code-pos = 'true'"> <axsl:text> <xsl:text> [filename: <...

I did copy all the xsl files, so it needs to be something else...

For testing I modified the files in the oxygen.jar/builtin and I worked - wouldn't be my preferred solution though.

Regards,
Patrik

I did as you told me - all without any effect. :(

Maybe you could give me a file (xsl, zip, jar or whatever is necessary) with any(!) noticable modification in schematronDispatcher that you tested successfully?

Thanks and regards,
Patrik

Sorry, but I can't help you since I don't understand what you actually want and my assumptions appear to be wrong.

Regards,
Patrik

It's quite easy to implement a custom author action using XsltOperation. The limits of my implementation: - The author can't enter the filename. It is rather generated from the title. - Thus it is limited to elements with a title element. - It doesn't use the selectionbut takes the first suitable an...

I successfully modified the iso-schematron-message.xsl. And the changes are in effect even without restarting oxygen. However, modifying the schematronDispatcher.xsl or XSD2Schtrn.xsl didn't have any effect so far - even after restarting oxygen. For instance in XSD2Schtrn.xsl I replaced line 80 (in ...

Of course you could adapt the existing stylesheet as well by droping the joe-attibutes and directly formatting the values. But I understood that you WANT to use another transformation...

An alternative would be to add the xml:space attribute with fixed or default value 'preserve' to the schema on the note-element. For my own document type derived from dita I did this for any element that can contain text content - which are quite a lot. (But I wrote my own xml schema anyway, so it w...

An xslt transformation would probably do the trick. Here's a small demonstration how to change the text content of elements with the joe:fixedLength attribute (ignoring the seperator and align attributes so far): Test-Input: <Case xmlns:joe="urn:com.website/joe" joe:separator="&#x...

You need to validate the Test-xsd file against the schematron file DerivedAssert.sch

Thanks Adrian. It works.

Regards,
Patrik

I have some ideas/requirements on improvement for schematron. However, it seems there is no more any development ongoing since the latest news on http://www.schematron.com/index.html is 5 years old and the mailing lists appear to be dead as well. I there any clean way to make adjustments to the sche...

Yes, it's possible to embed schematron rules in xsd. But youÄll have the same problem as with the xs:assert: it applies to the xsml file you're validating rather the the schema itself. For demonstration (and fun) I implemented a simple "DerivedAssert" you can add into the xml schema that i...

Note that you can use any xpath and call xslt function in the schematron rules. Thus, i can hardly imagine anything more flexible than that. Didn't test it but you could probably even implement a very generic schematron rule that actually evaluates an xpath expression written in the xsd. Then you co...

So you want to use the xs:assert to validate your schema and not to validate the xml described by your schema, right? In this case the xs:assert would need to be placed in the xsd describing your xsd. Since you probably don't want to extend the stadard xsd for this you could do this with an addition...

This code <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:template match="Address"...

Hi, when the schematron validation fails it writes a message. When clicking on the message the cursor goes to the node that has been evaluated. Is there an easy way to jump to the schematron rule that generated this message? Since my schema is quite complex with few schematron files and several xsd ...

Hi, I have added soem schematron rules within my xsd. Now with growing complexity it appears that I use the same element name twice and it might happen that a schematron rules matches the second element as well which it shouldn't. Now my idea is to use schema-element or element(*, myType) as pattern...

Hi, this could be done with string-join: <xsl:value-of select="string-join((AddressLine1, AddressLine2, AddressLine3, AddressLine4), ', ')"/> It first create a list of all (existing) AddressLine*-elements and string-join will just add a ", " between all elements. regards, Patrik

Hi Scott, how about doint this in two steps: 1. Use analyze-string to identify words. 2. in matching-substring check if it only contains caps. An alternative might be this rexexp: "(^|[\s])([A-Z\s]+)($|[\s])". With rexex-goup(2) you would get the words. However, the whitespace before/after...

Hi, after some (more or less successfull) experiments with xproc I'm wondering if it wouln't be better to implement everything in xslt and add the missing steps (for instance fop and schematron validation) as custom exention elements written in java. My argumentation: calling xslt from xproc you can...