January 2009 - oXygen-user - www.oxygenxml.com

set an XML Schema for a directory?
by Robert Koberg 30 Mar '09

30 Mar '09

Hi, I haven't used project mode much, but I just created a new project and imported a directory structure into it. One of the folders contains content files that are supposed to adhere to one XML Schema. I see the 'validate selection with...' which allows me to validate the entire directory -- which is great. However, when I bring up an invalid file I would like to have the editor know which schema to use (the one I validated the dir against) so the editor will give the element/attribute options without having to assign the schema each time. Make sense? Is this possible? best, -Rob

2 2

using catalogs
by Steven_Carmody＠brown.edu 04 Mar '09

04 Mar '09

I'm trying to use Oxygen to edit the set of XML-based config files that come with the Shibboleth package. The package is typically installed on linux, as a plugin into a web server such as apache. The package comes with a set of .xsd files, and an accompanying set of xml catalog files. Here's what a typical supplied catalog file looks like: <?xml version="1.0" encoding="UTF-8"?> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <system systemId="urn:oasis:names:tc:SAML:1.0:assertion" uri="/opt/local/shibboleth-sp/share/xml/opensaml/cs-sstc-schema-assertion-1.1.xsd"/> <system systemId="urn:oasis:names:tc:SAML:1.0:protocol" uri="/opt/local/shibboleth-sp/share/xml/opensaml/cs-sstc-schema-protocol-1.1.xsd"/> </catalog> I've tried the following steps: -- downloaded all of the xsd and catalog files to my desktop Mac -- edited the catalog files, changing the file system path in all the uri attributes - launched Oxygen, went to Preferences/XML Catalog, and added the five catalog files that come with the package. - quit Oxygen, re-launched (to have the new Preferences take effect) -- open a Shibboleth xml file, and attempt to validate it I'm presented with an error -- "There is no schema or DTD associated with the document. You can create an association either with the Associate Schema action or from the Options men Preferences/Editor/Default Schema Association." does anyone have a suggestion on a way to get validation to work, using catalog files? Rather than adding everything to the Default Schema Association?

3 12

Format and Indent Problem
by Jeff Sese 02 Mar '09

02 Mar '09

Hi, As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to? I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome. Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product? Thanks, Jeff

3 16

RE: [oXygen-user] How to switch off automatic generation of attributes in XSL [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 16 Feb '09

16 Feb '09

Thanks Eliot, I will join the XSL mail list in future solutions. John > -----Original Message----- > From: Eliot Kimber [mailto:ekimber@reallysi.com] > Sent: Thursday, 22 January 2009 10:45 AM > To: Hockaday John > Subject: Re: [oXygen-user] How to switch off automatic > generation of attributes in XSL [SEC=UNCLASSIFIED] > > > On 1/21/09 5:38 PM, "John.Hockaday(a)ga.gov.au" > <John.Hockaday(a)ga.gov.au> > wrote: > > > Hi, > > > > My friend and colleague sent me some XSL which he asked me > to validate the > > output XML. The output includes namespaces for the XSDs > but also some of the > > namespaces that he used for functions that generated some > of the element > > content. For example, xmlns:util="java:java.util.UUID" to > generate a UUID for > > the gmd:fileIdentifier element. If he removes these > namespaces from the XSL of > > course the transformation fails. If he includes them the > transformation is > > successful but I don't see how to get rid of the namespaces > and attributes for > > the unwanted namespaces in the output XML. > > > > For example I don't want the xmlns:dif, xmlns:fn, > xmlns:util namespaces as > > attributes in the root element and I also don't want the > xmls:srv attribute in > > the elements. > > > > How do I get rid of this content? > > This is really a question for the XSL mailing list, but the answer is: > > <xsl:stylesheet version="2.0" exclude-result-namespaces="util > fn dif" ...> > > MarkMail.org is your friend for getting quick answers to XSLT > questions (and > lots of other questions). > > Cheers, > > Eliot > > ---- > Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. > email: ekimber(a)reallysi.com <mailto:ekimber@reallysi.com> > office: 610.631.6770 | cell: 512.554.9368 > 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 > www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com > <http://blog.reallysi.com> | www.rsuitecms.com > <http://www.rsuitecms.com> > >

3 9

Early access to oXygen 10.1
by George Cristian Bina 13 Feb '09

13 Feb '09

Hi all, You can find below links to an early access build of oXygen 10.1 for different platforms (Windows, Mac OS X and Linux). What we are looking for is feedback on the new main features of 10.1 like: - the new XML Schema visual editor - the new XML Schema documentation (PDF, DocBook, HTML output) - the new Outliner for XSLT, XML Schema and XQuery - the XQuery content completion support that goes into modules for proposals - XSLT processor options at transformation scenario level A couple of questions: - The default page for opening an XML Schema should be the Text or the new Schema (visual editor) page? - The old diagram is still available if enabled from Options->Preferences -- Editor / Pages / Text / Diagram -- Show XML Schema diagram. Do you want that to be visible by default? The version 10 license key works with 10.1 and it can be installed side by side with 10.0. Windows: -------- http://www.oxygenxml.com/beta/InstData/Windows/VM/oxygen.exe Mac OS X: --------- http://www.oxygenxml.com/beta/InstData/MacOSX/oxygen.tar.gz Linux: ------ http://www.oxygenxml.com/beta/InstData/Linux/VM/oxygen.sh Linux64: ------ http://www.oxygenxml.com/beta/InstData/Linux64/VM/oxygen.sh Enjoy, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

2 4

switch off: auto self-standing tag function
by Takako Kato 03 Feb '09

03 Feb '09

Dear list, In my xsl, in my header, I have a link to java script file, which cannot be a self-standing tag: <SCRIPT language="Javascript1.2" src="../java/menu_desc.js" type="text/javascript"></SCRIPT> Every time I transform a xml file, however, the Oxygen automatically change the above link into: <SCRIPT language="Javascript1.2" src="../java/menu_desc.js" type="text/javascript"/>. I want to switch off this function, i.e, the function, which change the empty tags into self-standing tag automatically. Could anybody teach me how to do this, please/ Thanks very much. Best wishes, Tak -- -------------------------- Takako Kato TakakoKato123(a)gmail.com School of English University of Leicester University Road Leicester LE1 7RH, UK +44-(0)116-252-2628 http://www.le.ac.uk/ee/em1060to1220/

2 2

What is better: bold the names or bold the values?
by George Cristian Bina 30 Jan '09

30 Jan '09

Hi, We need your feedback on one of the oXygen 10.1 features. We implemented a new XML Schema editor where XML Schemas can be edited visually. The properties of the selected component are available in a side view (Attributes view). Now, some attributes are specified by the user, some other have default values. For marking the specified ones we though of two possibilities: - bold the attribute names as you can see in http://www.oxygenxml.com/update/boldNames.jpg or - bold the values, as you can see in http://www.oxygenxml.com/update/boldValues.jpg Do you have a preference for any of these? Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

8 9

Spam message
by Sorin Ristache 26 Jan '09

26 Jan '09

Hello all, Sorry, there was a spam email message sent from the email address of a subscribed user but we will filter all such messages in the future before they get to the list subscribers. Regards, Sorin

1 0

Impressive Tag Heuer timepieces
by Reed Crowley 26 Jan '09

26 Jan '09

Dear Cory, If you've waited to get your Breitling watch, this is the right time to go for it. http://muldrow216puge.freehostingz.com We are offering wholesaler prices on all watches during the month of January 2009. http://muldrow216puge.freehostingz.com Our Breitling watches have Weights/feels and looks exactly same as original. Sincerely, Mr Kirkpatrick

1 0

How to switch off automatic generation of attributes in XSL [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 21 Jan '09

21 Jan '09

Hi, My friend and colleague sent me some XSL which he asked me to validate the output XML. The output includes namespaces for the XSDs but also some of the namespaces that he used for functions that generated some of the element content. For example, xmlns:util="java:java.util.UUID" to generate a UUID for the gmd:fileIdentifier element. If he removes these namespaces from the XSL of course the transformation fails. If he includes them the transformation is successful but I don't see how to get rid of the namespaces and attributes for the unwanted namespaces in the output XML. For example I don't want the xmlns:dif, xmlns:fn, xmlns:util namespaces as attributes in the root element and I also don't want the xmls:srv attribute in the elements. How do I get rid of this content? Thanks. John Here is the head of the XSL: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gml="http://www.opengis.net/gml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:util="java:java.util.UUID" xmlns:dif="http://gcmd.gsfc.nasa.gov/Aboutus/xml/dif/" xmlns:fn="http://www.w3.org/2005/02/xpath-functions" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://www.isotc211.org/2005/gmd/gmd.xsd http://www.opengis.net/gml http://www.isotc211.org/2005/gml/gml.xsd http://www.w3.org/1999/xlink http://www.isotc211.org/2005/xlink/xlinks.xsd"> <xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes" media-type="text/plain"/>   <xsl:template match="dif:DIF">  <gmd:MD_Metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gml="http://www.opengis.net/gml" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://www.isotc211.org/2005/gmd/gmd.xsd http://www.isotc211.org/2005/gco http://www.isotc211.org/2005/gco/gco.xsd http://www.isotc211.org/2005/gts http://www.isotc211.org/2005/gts/gts.xsd http://www.isotc211.org/2005/gsr http://www.isotc211.org/2005/gsr/gsr.xsd http://www.isotc211.org/2005/gss http://www.isotc211.org/2005/gss/gss.xsd"> <gmd:fileIdentifier> <gco:CharacterString> <xsl:variable name="uid" select="util:toString(util:randomUUID())"/> <xsl:value-of select="$uid"/> </gco:CharacterString> </gmd:fileIdentifier> ...

1 1