- oXygen-user - www.oxygenxml.com

default attribute value
by Roderik Dernison 07 Dec '12

07 Dec '12

Hi, My colleagues want default attribute values for some tags. I've tried: <xs:element name="wordgroup" > <xs:annotation> <xs:documentation>The actual words or sentence of an example.</xs:documentation> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="wordgroup.class">  </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <xs:complexType name="wordgroup.class" mixed="true"> <xs:attributeGroup ref="wordgroup.attributes"/> </xs:complexType> <xs:attributeGroup name="wordgroup.attributes"> <xs:attribute name="type" type="wordgroup-type-att.class" default="unspecified"/> </xs:attributeGroup> <xs:simpleType name="wordgroup-type-att.class"> <xs:restriction base="xs:string"> <xs:enumeration value="unspecified" /> <xs:enumeration value="compoundpart" /> <xs:enumeration value="circumfix" /> <xs:enumeration value="infix" /> </xs:restriction> </xs:simpleType> But in this case, no value is set for the attribute "type". How can I manage to set a default attribute value that is also shown in oXygen? Kind regards, Ing. Roderik Dernison Programmeur/ontwikkelaar INL * Schatkamer van de Nederlandse Taal Matthias de Vrieshof 2 * Kamer 106a * 2311 BZ Leiden Tel. +31 (0)71 527 2491 * www.inl.nl<http://www.inl.nl/> ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ----------------------------------------------------------

2 1

Highlighting text between processing instructions.
by Michael Anthony Smith 03 Dec '12

03 Dec '12

Hi, I have read several previous posts on this topic, but still have some questions. Previous topics: http://www.oxygenxml.com/forum/topic4909.html http://www.oxygenxml.com/forum/topic6949.html http://www.oxygenxml.com/forum/topic7103.html Using oXygen 14.1: I am able to write a custom StylesFilter that appropriately adjusts the colour highlighting of elements near processing instructions. I am also able to use the CSS form based editing (oxy_editor) to provide formatting and selection lists for elements. However, I have been unable to find a technique that allows the nodes between a <?oxy_custom_start?> and <?oxy_custom_end?> processing instruction to be accessed via CSS, rather than the AuthorPersistentHighlighter API. Is this possible? The problem with the element based approach is that this requires non-DITA (or other format specific doctype) elements to represent the additional information that we want to process. We would prefer to use processing instructions to contain this additional information, as this would not break the DITA validation. Ideally, we would like to be able to use the form based editing functionality with processing instructions (PIs), whilst the PIs are still hidden from view. Is it possible to 'link' a StyleFilter to the form based editing functionality through the API? Any suggestions welcome. Best regards. Anthony. -- -- ------------------------------------------------------------------------- Michael Anthony Smith, DeltaXML Ltd "Michael Anthony Smith, DeltaXML Ltd "Experts in Information Change"" T: +44 1684 869035 E: anthony.smith(a)deltaxml.com http://www.deltaxml.com Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK

2 1

Using xs:unique
by Olumide 29 Nov '12

29 Nov '12

I'd appreciate help figuring out why the schema below validates the following xml file even though it the id='3' is not unique. Regards, - Olumide --------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="Item"> <xs:complexType> <xs:sequence maxOccurs="unbounded"> <xs:choice> <xs:element name="a"> <xs:complexType> <xs:attribute name="id" use="required"/> </xs:complexType> <xs:unique name="uniqueId-a"> <xs:selector xpath="*"/> <xs:field xpath="@id"/> </xs:unique> </xs:element> <xs:element name="b"> <xs:complexType> <xs:attribute name="id" use="required"/> </xs:complexType> <xs:unique name="uniqueId-b"> <xs:selector xpath="*"/> <xs:field xpath="@id"/> </xs:unique> </xs:element> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> ---------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <Item> <a id="3"/>  <a id="2"/> <b id="3"/>  <a id="4"/> <b id="0"/> <b id="3"/>  </Item>

2 4

Insert <image> workflow
by KAATMAN Matthew 29 Nov '12

29 Nov '12

Hello Everyone, This is probably something that is obvious, but there are two workflows for inserting an <image> tag: 1. DITA->Insert->Image - This pops up a URI box to select the image and then adds the tag with the href to the document. 2. From the elements list, select image - This adds the tag to the document. Is there a way to access the URI selection box if you use the 2nd workflow? I guess I'd like to either double click on the image tag to bring it up (currently does nothing). Alternatively/Additionally, when I select href in the attributes list I'd like it to pop up the URI selection. Am I missing an obvious way to do this? If not, is there any way I can configure this behavior? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 2

Automatically generating XML schemas using XSLT
by Olumide 27 Nov '12

27 Nov '12

Hello, Following this tutorial (http://www.liquid-technologies.com/Tutorials/XmlSchemas/XsdTutorial_04.aspx -- don't worry, I use Oxygen ;-) ) I've refactored my 733 line schema into 16 separate files or sub-schemas, each with its own namespace. Now the top level schema is just 77 lines. The plan is to use these sub-schema's to build other top-level schemas. The problem is that most top level schema's are quite similar and only differ in a few low level details. For example while one top level schema supports all PaymentMethodType's (see tutorial) another top-level schema may support only VISA and MasterCard. Currently my method of creating top-level schemas involves considerable duplication. For example, my current method of creating a top-level schema in which only VISA and MasterCard are supported would involve duplicating Main.xsd and OrderType.xsd, but customizing CommonTypes.xsd and reuse CustomerTypes.xsd. (As my actual schema is a lot longer a lot more duplication is involved.) I find this duplication unacceptable primarily because it introduces a maintenance challenge i.e. I would have to maintain any number of identical sub-schemas with different names. What I would like to know is if there is a method of automatically generating a schema without via a config file of some sort (XSLT perhaps?), in order to avoid duplicating sub-schemas. Also, is it good practice for all the sub-schemas to declare the same target namespace in this case (just like the xml schema namespace xs, but have custom sub-schemas declare a separate namespace? - Olumide

2 7

Re: [oXygen-user] Automatically generating XML schemas using XSLT
by Olumide 22 Nov '12

22 Nov '12

On 21/11/2012 21:48, Sebastian Rahtz wrote: > The Text Encoding Initiative (http://www.tei-c.org/) manages this sort of thing by defining a whole new higher-level XML > language of its own for describing the various areas it covers (dictionaries, plays, manuscript descriptions, transcriptions > of spoken speech etc). This language includes mechanisms for subsetting, group, classes of objects etc. All the processing > is done using XSLT, to generate DTD or RELAX NG schemas (from which XSD can be generated) or extracted ISO Schematron > or, documentation. > > I don't particularly suggest you adopt the TEI ODD language for your own work (fun though it would be), but just to point > out that there are precedents for large-scale generation of schemas Why don't you recommend TEI ODD? - Olumide

1 0

ANNOUNCEMENT: Releasing collada framework 1.0.0 for COLLADA (.dae) files.
by Jarl Friis 21 Nov '12

21 Nov '12

Just announcing collada framework 1.0.0. It supports schema validation and auto completion for COLLADA 1.4.1 and 1.5.0 and has a template for each of them. See installation instructions on https://github.com/softace/oxygen-collada Jarl

1 0

George's Meetup Talk on Debugging Toolkit Transforms
by Eliot Kimber 19 Nov '12

19 Nov '12

At the Oxygen User Meetup George presented how to debug Toolkit transforms using the Oxygen debugger. Apparently I wasn't paying close attention because now I can't remember how to do it. Is George's presentation available somewhere or is the process documented somewhere? Thanks, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

3 4

How to Resolve references to Toolkit-provided Java Functions?
by Eliot Kimber 19 Nov '12

19 Nov '12

In my project for working on custom Toolkit plugins, I have all my master transforms defined as master files and everything validates nicely except that I still get messages on the dost.jar-provided Java functions getWidth() and getHeight(): Engine name: Saxon-PE 9.4.0.4 Severity: fatal Description: Cannot find a matching 2-argument function named {org.dita.dost.util.ImgUtils}getWidth() What else do I need to do to remove these validation errors? Cheers, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

2 2

xs:keyref not working in 14.1
by Jirka Kosek 19 Nov '12

19 Nov '12

Hi, I have just noticed that in the recent version of oXygen 14.1 xs:keyref is not working. See attached files. Probably this is Xerces bug and you have just upgraded Xerces version between releases. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------

3 2