- oXygen-user - www.oxygenxml.com

How Does Oxygen Validate This Dublin Core Schema?
by Eliot Kimber 10 Mar '08

10 Mar '08

In testing our own schema-based validation features in our RSuite product we discovered that as far as we can tell Xerxes 2.9.x fails to validate the valid Dublin Core schema given below. This is a documented problem with Xerces in that it doesn't handle the particular pattern of restriction and substitution groups used in this schema. However, Oxygen happily (and correctly) validates documents using this schema (that is, our test case fails when we parse it with our Xerces-based code but Oxygen reports it as valid). My understanding was that Oxygen used Xerces for its schema processing, so my question is: what does Oxygen do special that allows it to process this case, or is our understanding of Xerces flawed? The failure we get is than an instance of e.g., dc:title is reported by Xerces as not allowing character data content when of course it does. The original discussion of this issue from the Dublin Core people is here: http://dublincore.org/schemas/xmls/qdc/2008/02/11/notes/ Very near the bottom is this: This derivation of a complexType with simpleContent by restriction of a base complexType with complexContent is valid under section 3.4.6 of XML Schema Part 1: Structures, specifically item 5.1.2 of the section "Schema Component Constraint: Derivation Valid (Restriction, Complex)", because the base complexContent is mixed and emptiable. This was confirmed by Henry Thompson, see e.g. http://www.w3.org/2001/05/xmlschema-rec-comments#pfiSimpleContent http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0005.html http://lists.w3.org/Archives/Public/xmlschema-dev/2002Oct/0008.html Conclusion: Xerces appears to be behaving incorrectly in rejecting this derivation. Thanks, Eliot <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://purl.org/dc/elements/1.1/" targetNamespace="http://purl.org/dc/elements/1.1/" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:documentation xml:lang="en"> DCMES 1.1 XML Schema XML Schema for http://purl.org/dc/elements/1.1/ namespace Created 2003-04-02 Created by Tim Cole (t-cole3(a)uiuc.edu) Tom Habing (thabing(a)uiuc.edu) Jane Hunter (jane(a)dstc.edu.au) Pete Johnston (p.johnston(a)ukoln.ac.uk) Carl Lagoze (lagoze(a)cs.cornell.edu) This schema declares XML elements for the 15 DC elements from the http://purl.org/dc/elements/1.1/ namespace. It defines a complexType SimpleLiteral which permits mixed content and makes the xml:lang attribute available. It disallows child elements by use of minOcccurs/maxOccurs. However, this complexType does permit the derivation of other complexTypes which would permit child elements. All elements are declared as substitutable for the abstract element any, which means that the default type for all elements is dc:SimpleLiteral. </xs:documentation> </xs:annotation> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd"> </xs:import> <xs:complexType name="SimpleLiteral"> <xs:annotation> <xs:documentation xml:lang="en"> This is the default type for all of the DC elements. It permits text content only with optional xml:lang attribute. Text is allowed because mixed="true", but sub-elements are disallowed because minOccurs="0" and maxOccurs="0" are on the xs:any tag. This complexType allows for restriction or extension permitting child elements. </xs:documentation> </xs:annotation> <xs:complexContent mixed="true"> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/> </xs:sequence> <xs:attribute ref="xml:lang" use="optional"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="any" type="SimpleLiteral" abstract="true"/> <xs:element name="title" substitutionGroup="any"/> <xs:element name="creator" substitutionGroup="any"/> <xs:element name="subject" substitutionGroup="any"/> <xs:element name="description" substitutionGroup="any"/> <xs:element name="publisher" substitutionGroup="any"/> <xs:element name="contributor" substitutionGroup="any"/> <xs:element name="date" substitutionGroup="any"/> <xs:element name="type" substitutionGroup="any"/> <xs:element name="format" substitutionGroup="any"/> <xs:element name="identifier" substitutionGroup="any"/> <xs:element name="source" substitutionGroup="any"/> <xs:element name="language" substitutionGroup="any"/> <xs:element name="relation" substitutionGroup="any"/> <xs:element name="coverage" substitutionGroup="any"/> <xs:element name="rights" substitutionGroup="any"/> <xs:group name="elementsGroup"> <xs:annotation> <xs:documentation xml:lang="en"> This group is included as a convenience for schema authors who need to refer to all the elements in the http://purl.org/dc/elements/1.1/ namespace. </xs:documentation> </xs:annotation> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="any"/> </xs:choice> </xs:sequence> </xs:group> <xs:complexType name="elementContainer"> <xs:annotation> <xs:documentation xml:lang="en"> This complexType is included as a convenience for schema authors who need to define a root or container element for all of the DC elements. </xs:documentation> </xs:annotation> <xs:choice> <xs:group ref="elementsGroup"/> </xs:choice> </xs:complexType> </xs:schema> -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 3

browser
by Boojum 03 Mar '08

03 Mar '08

When I selected XML Document --> Open in Browser, nothing is displayed in the browser (my default browser is Firefox).

2 1

Feature Request: Allow Insertion of Inline Markup Within CDATA Marked Sections in Author Mode
by Eliot Kimber 29 Feb '08

29 Feb '08

This may not be either doable or worth the effort, but in doing markup samples for DTD documentation, I've started using CDATA marked sections to hold the examples and then breaking them to insert pairs around parts of the example, e.g.: <pre> <![CDATA[<sometag> <more-markup> ]]><![CDATA[<this-is-bold/>]]<![CDATA[ </more-markup> </sometag>]]> </pre> In theory it should be possible for the editor to automatically adjust the marked section markup to allow the real markup within what was a single CDATA marked section. At the moment I have to bounce in and out of Author mode in order to adjust the highlighting in my examples. Not a big deal but it could be more convenient. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

1 1

Problem generating XML document from schema
by Bradley, Peter 20 Feb '08

20 Feb '08

Hi, I'm involved in writing an application that will obtain data from and send data to the UK Student Loan Company via a Web service that is planned to be available shortly. The necessary schema information is contained in the Database Schema and Database Types xsd files available from: http://www.ucisa.ac.uk/groups/cisg/misgdocs/HEICourseDatabase I've downloaded the files and opened them in <oXygen/>. In order to get an idea of the kind of document I will need to be able to write into and generate from our database, I have tried to generate a sample XML file. With the HEICourseDatabaseSchema.xsd file open in <oXygen/> I do Tools --> Generate Sample XML Files ... In the dialog, I browse to the HEICourseDatabaseSchema.xsd file, for the URL. I then try to set a document root, but the Document root drop down list is empty. The HEICourseDatabaseTypes.xsd file is in the same directory as the HEICourseDatabaseSchema.xsd file and should therefore be available, so it's not that. Can anyone point out to me the obvious point that I'm missing, please? I've never had trouble generating sample files before, so I just don't see what I'm doing wrong. Many thanks Peter

4 6

xinclude
by Boojum 20 Feb '08

20 Feb '08

Posted this to the forum, too. Sorry for the dupe. I'm learning OxygenXML's 9.1 support for Xinclude. I have two files, with one pointing by means of Xinclude to the other - no Xpointer, just want the contents of the entire second file. Validation succeeds with no errors, so I assume that the Xinclude is correct. Next--how can I view the resulting document, with the contents of the second file displayed in the first? Must I perform a transformation to see the results, or is there some other way?

4 3

Re: [oXygen-user] Re: [dita-users] All possible Xpath generator?
by Wendell Piez 15 Feb '08

15 Feb '08

Hedley, Unfortunately the list of "all possible XPaths to a text file" is infinite in many cases, due to the possibility of recursive structures such as nested div or section elements, lists inside lists, or inline elements that may have arbitrary inline elements in their content. Do you really want a path such as "/doc/body/div/div/div/div/list/item/list/item/list/item/p/figure/caption/p/b/i/mono/i/b" even such a path points to an element that could be valid? I think Dan is right that the requirement needs some refinement. Cheers, Wendell At 08:42 PM 2/12/2008, you wrote: >Dan: > >>At Wednesday, 13/02/2008, 12:16 PM;, Dan wrote: >>your post is a bit confusing, and some better details/explanations >>would be nice to see. What do you mean by "write a list of all >>possible absolute Xpaths to a text file." > >Rephrasing my original request: >I am developing a CSS implementation for [instance documents that >conform to] an XML schema. It would really help to check if all >[required CSS class matches] have been covered if I could find a >utility that would scan a DTD (including *.mod inclusions) or XML >Schema to write a list of all absolute -- not including wildcards -- >[Xpaths from the root element to each possible leaf element] ... to >a text file. For example, using a possible path from a DITA DTD: > > /reference/refbody/section/p > >This would help determine what class definitions can be generic >no matter in what context an element apppears (e.g. ) and what >may need different treatment depending on context >(e.g. */section/title). Oh, and if the generator could list the >Xpath in reverse, from leaf node to root, as well that would be pleasant: > > p\section\refbody\reference\ > >Then I could sort the list of paths so that all instances where >was a leaf would be together and I could decide which contexts could >share a CSS class and which would need context-specific classes. > >I've tried using the <oXygen/> instance generator on the DITA >task.xsd, but even limiting recursion depth and number of >repetitions, it produces very large files, possibly not completing >in my lifetime. And then there is the problem of extracting the Xpaths. > >Hope that makes it clearer, >Hedley > > >-- >Hedley Stewart Finger >28 Regent Street Camberwell VIC 3124 Australia >Tel. +61 3 9809 1229 Mobile +61 412 461 558, >E-mail <mailto:hfinger@handholding.com.au> > > >_______________________________________________ >oXygen-user mailing list >oXygen-user(a)oxygenxml.com >http://www.oxygenxml.com/mailman/listinfo/oxygen-user ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

2 1

Re: [dita-users] All possible Xpath generator?
by Hedley Finger 12 Feb '08

12 Feb '08

Dan: >At Wednesday, 13/02/2008, 12:16 PM;, Dan wrote: >your post is a bit confusing, and some better details/explanations >would be nice to see. What do you mean by "write a list of all >possible absolute Xpaths to a text file." Rephrasing my original request: I am developing a CSS implementation for [instance documents that conform to] an XML schema. It would really help to check if all [required CSS class matches] have been covered if I could find a utility that would scan a DTD (including *.mod inclusions) or XML Schema to write a list of all absolute -- not including wildcards -- [Xpaths from the root element to each possible leaf element] ... to a text file. For example, using a possible path from a DITA DTD: /reference/refbody/section/p This would help determine what class definitions can be generic no matter in what context an element apppears (e.g. ) and what may need different treatment depending on context (e.g. */section/title). Oh, and if the generator could list the Xpath in reverse, from leaf node to root, as well that would be pleasant: p\section\refbody\reference\ Then I could sort the list of paths so that all instances where was a leaf would be together and I could decide which contexts could share a CSS class and which would need context-specific classes. I've tried using the <oXygen/> instance generator on the DITA task.xsd, but even limiting recursion depth and number of repetitions, it produces very large files, possibly not completing in my lifetime. And then there is the problem of extracting the Xpaths. Hope that makes it clearer, Hedley -- Hedley Stewart Finger 28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Mobile +61 412 461 558, E-mail <mailto:hfinger@handholding.com.au>

1 0

All possible Xpath generator?
by Hedley Finger 12 Feb '08

12 Feb '08

XML/Xpath/CSS heavy hitters: I am developing a CSS implementation for an XML schema. It would really help to check if all possibilities have been covered if I could find a utility that would scan a DTD (including *.mod inclusions) or XML Schema to write a list of all possible absolute Xpaths to a text file. This would help determine what class definitions can be generic no matter in what context an element apppears (e.g. ) and what may need different treatment depending on context (e.g. */section/title). Oh, and if the generator could list the Xpath in reverse, from leaf node to root, as well that would be pleasant: p/section/refbody/reference. Trawling through the Help for <oXygen/> 9.1 didn't give any joy, likewise Google. Regards, Hedley -- Hedley Stewart Finger 28 Regent Street Camberwell VIC 3124 Australia Tel. +61 3 9809 1229 Mobile +61 412 461 558, E-mail <mailto:hfinger@handholding.com.au>

1 0

CSS alternatives?
by Wendell Piez 11 Feb '08

11 Feb '08

Hi, Not exactly a bug, but a glitch. When xml-stylesheet PIs are being used, "CSS Alternatives" appears not to work unless the CSS files are provided with title pseudo-attributes in their respective PIs. I guess this is not unreasonable, if you need a label for the pull-down menu. But the "Associate XSLT/CSS Stylesheet" dialog box doesn't offer a place to enter a title; it has to be done by hand. Maybe: (1) the dialog box should offer a field for a CSS title, and possibly (2) if one isn't given, the CSS Alternatives pull-down should fall back to the stylesheet href? What do you think? Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

3 8

Reporting of Imported/Included XSLT Component in Error Messages
by Eliot Kimber 07 Feb '08

07 Feb '08

I have a complext XSLT made up of many parts. In running it from inside Oxygen using Saxon 9, I was getting an error message but the message was reported against a line number in the top-level style sheet. When I run the same script outside Oxygen the error messages is associated with the correct component file (not the top-level). Is this a limitation in Oxygen's integration with Saxon or a bug? The message in this case was a run-time error reporting that a template's parameter was not set by the caller and the default was not consistent with the declared data type of the parameter. Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

2 2