[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Re: [Schematron-love-in] ISO Schematron Update (RETRY)
Fraser, Thanks, but I have already done this in the same way myself. My point was just that, if there was a new implementation coming, XML would be a better output for the default as this is easy to convert to HTML or a specific XML format. For example, I have a test suite for the OASIS Election Markup Language. This produces the standard EML error message from a stylesheet that imports skeleton. I did this before 1-6 came out. I guess I will switch at my next revision, but 1-5 is working for me. Regards Paul > -----Original Message----- > From: Fraser Goffin [mailto:goffinf@g...] > Sent: 22 May 2006 15:57 > To: Paul Spencer > Cc: schematron-love-in@e...; XML-Dev Mailing list > Subject: Re: Re: [Schematron-love-in] ISO Schematron Update > (RETRY) > > > Paul, > > there is an xslt (attached) that produces xml output (it imports > skeleton). If you need a customised output then you are actively > encouraged to create your own implementation, at least, thats what we > did (its fairly easy). > > Also we use the 1-6 implementation since this fixes a few bugs and > adds some features (let, id/keys, ...) > > Regards > > Fraser. > > On 22/05/06, Paul Spencer <xml-dev-list@b...> wrote: > > Ken, > > > > > >A while back there was some talk of a possible XSLT implementation > > > >being available at some point too ? > > > > > > Works are in progress ... no announcements yet ... sorry for any > > > delay ... the development of implementations is independent of the > > > standardization process. > > > > I have used the old skeleton1-5.xslt. This is extremely useful, > but had a > > couple of problems from my point of view. I don't know whether > it is useful > > for you to know of these if you are doing a new version. > > > > The first is that I found I had to be very careful on the context of the > > rules to make sure that the right one was run. For example, I > might write a > > rule for all elements A, then another for element A when it contained an > > element B. I'm sure you can see the problem - the prioritisation of XSLT > > templates would stop the first rule running if the A in > question contained a > > B. The intention was for both to run. The workaround is easy, > but it is easy > > to miss the problem, especially as I write my rules as a > spreadsheet with a > > context for each rule (easier to review with business people) > then create > > the Schematron automatically from that. > > > > The second problem is just the fact that skeleton1-5.xslt > produces an HTML > > output. Producing an XML output is much more flexible. Not a > problem for me > > to change, but it would be useful if this were the standard as HTML can > > always be produced from this. > > > > Paul Spencer > > > > > > ----------------------------------------------------------------- > > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > > initiative of OASIS <http://www.oasis-open.org> > > > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > > > To subscribe or unsubscribe from this list use the subscription > > manager: <http://www.oasis-open.org/mlmanage/index.php> > > > > >
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|