formatting xml with namespaces

**Richard Light** · Nov 20 '06, 08:15 AM

Re: formatting xml with namespaces

In message <1163941565.968 192.318020@h48g 2000cwc.googleg roups.com>,
"printdude1968@ gmail.com" <printdude1968@ gmail.comwrites

>What I need is an xsl or something which will let me go through the
>document and create a table
>Pseudo code
for each destination d in production
for each printer (ie. lp10) in d
format a line for each attribute
done
done
for each destination d in developement
for each printer (ie. lp10) in d
format a line for each attribute
done
done
>
>
>I've played around with xsl and xslt and seem to run into issues when I
>find that I need to process the
>namespaces.. ..

The local-name() function allows you to access the name of an element
irrespective of its namespace URI, and name() gives you the whole name,
namespace prefix included. So you could do:

<xsl:template match="*[local-name()='configu ration']">
<div>
<div>
<xsl:value-of select="substri ng-before(name(), ':')"/>
</div>
<div>
<xsl:apply-templates mode="descripti on"/>
</div>
</div>
</xsl:template>

<xsl:template match="*" mode="descripti on">
<div>
<xsl:value-of select="concat( local-name(), '=>', text())"/>
</div>
</xsl:template>

where I have used <divelements to indicate whatever structure you
might like to put around your output.

Richard Light

>There must be an easy way to do it
>Here's what I'd like my output to look like
>
>Production
lp110
BackToBCISClass =>H
queueType=>psfO ther
logicalQueue=PD ${localQueueDes tCode}PSF3
defaultMedium=> 3hol
form=>$( cat ${optionsInputT extFile} | awk '{print $7}' |
>awk -F=
>'{print $2}')
formfontFilters =>/dev/fs/E/PrintApps/LBM/filters/
formfontPath=>/dev/fs/E/PrintApps/LBM
jobName=>$(cat ${optionsInputT extFile} | awk '{print $1}' |
>awk
>-F= '{print $2}')
optionsInputTex tFile=>${LPSDIR }/${DEST}/o.${SEQ}
dataInputTextFi le=>${LPSDIR}/${DEST}/p.${SEQ}
chequeOutputPCL File=>${LPSDIR}/${DEST}/cheque.${SEQ}
pclOutputPCLFil e=${LPSDIR}/${DEST}/file.${SEQ}
billsOutputText File=>${dataInp utTextFile}.bil l
changeDate=>$(d ate "+%Y-%m-%d")
lpsdirWin=>"E:\ \ROC\\OM\\serve r"
splitOn=>$( head -n 1 ${dataInputText File} | cut -c2-4)
>
>Is this possible using xsl or xslt and if so, how do I reconcile the
>namespaces?
>

--
Richard Light
SGML/XML and Museum Information Consultancy
richard@light.d emon.co.uk

**Manuel Collado** · Nov 20 '06, 09:35 AM

Re: formatting xml with namespaces

printdude1968@g mail.com escribió:

Hi Everyone...
>
I'm a newbie to this stuff so bear with me.
>
I have a well formed xml document (I use jdom to verify)

Sorry, no. There is at least one unmatched tag: </destination7>.

>
<?xml version="1.0" encoding="ISO-8859-1"?>
<print-control>
<destinations
xmlns:destinati on0="http://mydomain.com/destinations/dest0"
xmlns:destinati on1="http://mydomain.com/destinations/dest1"
...
</destinations>
<production
xmlns:lp10="htt p://mydomain.compri nters/lp10"
xmlns:lp20="htt p://mydomain.compri nters/lp20"
...
<destination1 >
<lp10:configura tion>
<lp10:mapsBackT oBCISClass>W</lp10:mapsBackTo BCISClass>
<lp10:queueType >psfOther</lp10:queueType>
<lp10:formfontF ilters>/dev/fs/E/PrintApps/LBM/filters/</lp10:formfontFi lters>
<lp10:formfontP ath>/dev/fs/E/PrintApps/LBM</lp10:formfontPa th>
<lp10:jobName>$ (cat ${optionsInputT extFile} | awk '{print $1}' |
awk -F= '{print $2}')</lp10:jobName>
<lp10:optionsIn putTextFile>${L PSDIR}/${DEST}/o.${SEQ}</lp10:optionsInp utTextFile>
<lp10:dataInput TextFile>${LPSD IR}/${DEST}/p.${SEQ}</lp10:dataInputT extFile>
<lp10:chequeOut putPCLFile>${LP SDIR}/${DEST}/cheque.${SEQ}</lp10:chequeOutp utPCLFile>
<lp10:pclOutput PCLFile>${LPSDI R}/${DEST}/file.${SEQ}</lp10:pclOutputP CLFile>
<lp10:billsOutp utTextFile>${da taInputTextFile }.bill</lp10:billsOutpu tTextFile>
<lp10:changeDat e>$(date "+%Y-%m-%d")</lp10:changeDate >
<lp10:splitOn>$ ( head -n 1 ${dataInputText File} | cut
-c2-4)</lp10:splitOn>
...
</lp900:configura tion>
</destination3>
</development>
</print-control>
>
>
What I need is an xsl or something which will let me go through the
document and create a table ...
>
I've played around with xsl and xslt and seem to run into issues when I
find that I need to process the
namespaces....
>
There must be an easy way to do it
...
Is this possible using xsl or xslt and if so, how do I reconcile the
namespaces?

Any programming language with decent XML libraries can be used instead of XSLT.

Your data contains some references to AWK. Perhaps you could try xmlgawk:

Page not found - SourceForge.net

http://sourceforge.net/projects/xmlgawk

Free, secure and fast downloads from the largest Open Source applications and software directory - SourceForge.net

Regards.
--
Manuel Collado - http://lml.ls.fi.upm.es/~mcollado

**printdude1968@gmail.com** · Nov 20 '06, 03:15 PM

Re: formatting xml with namespaces

Hi

I was able to solve it... basically I took out all the namespaces.
Once I did that, adding the xslt to display it was pretty easy.

Richard Light wrote:

In message <1163941565.968 192.318020@h48g 2000cwc.googleg roups.com>,
"printdude1968@ gmail.com" <printdude1968@ gmail.comwrites

What I need is an xsl or something which will let me go through the
document and create a table
Pseudo code
for each destination d in production
for each printer (ie. lp10) in d
format a line for each attribute
done
done
for each destination d in developement
for each printer (ie. lp10) in d
format a line for each attribute
done
done

I've played around with xsl and xslt and seem to run into issues when I
find that I need to process the
namespaces....

>
The local-name() function allows you to access the name of an element
irrespective of its namespace URI, and name() gives you the whole name,
namespace prefix included. So you could do:
>
<xsl:template match="*[local-name()='configu ration']">
<div>
<div>
<xsl:value-of select="substri ng-before(name(), ':')"/>
</div>
<div>
<xsl:apply-templates mode="descripti on"/>
</div>
</div>
</xsl:template>
>
<xsl:template match="*" mode="descripti on">
<div>
<xsl:value-of select="concat( local-name(), '=>', text())"/>
</div>
</xsl:template>
>
where I have used <divelements to indicate whatever structure you
might like to put around your output.
>
Richard Light
>

There must be an easy way to do it
Here's what I'd like my output to look like

Production
lp110
BackToBCISClass =>H
queueType=>psfO ther
logicalQueue=PD ${localQueueDes tCode}PSF3
defaultMedium=> 3hol
form=>$( cat ${optionsInputT extFile} | awk '{print $7}' |
awk -F=
'{print $2}')
formfontFilters =>/dev/fs/E/PrintApps/LBM/filters/
formfontPath=>/dev/fs/E/PrintApps/LBM
jobName=>$(cat ${optionsInputT extFile} | awk '{print $1}' |
awk
-F= '{print $2}')
optionsInputTex tFile=>${LPSDIR }/${DEST}/o.${SEQ}
dataInputTextFi le=>${LPSDIR}/${DEST}/p.${SEQ}
chequeOutputPCL File=>${LPSDIR}/${DEST}/cheque.${SEQ}
pclOutputPCLFil e=${LPSDIR}/${DEST}/file.${SEQ}
billsOutputText File=>${dataInp utTextFile}.bil l
changeDate=>$(d ate "+%Y-%m-%d")
lpsdirWin=>"E:\ \ROC\\OM\\serve r"
splitOn=>$( head -n 1 ${dataInputText File} | cut -c2-4)

Is this possible using xsl or xslt and if so, how do I reconcile the
namespaces?

>
--
Richard Light
SGML/XML and Museum Information Consultancy
richard@light.d emon.co.uk

**printdude1968@gmail.com** · Nov 20 '06, 03:25 PM

Re: formatting xml with namespaces

I didn't include the entire XML document as I was just trying to show a
snippet of the document (it's over 1500 lines long).

Manuel Collado wrote:

printdude1968@g mail.com escribió:

Hi Everyone...

I'm a newbie to this stuff so bear with me.

I have a well formed xml document (I use jdom to verify)

>
Sorry, no. There is at least one unmatched tag: </destination7>.
>

<?xml version="1.0" encoding="ISO-8859-1"?>
<print-control>
<destinations
xmlns:destinati on0="http://mydomain.com/destinations/dest0"
xmlns:destinati on1="http://mydomain.com/destinations/dest1"
...
</destinations>
<production
xmlns:lp10="htt p://mydomain.compri nters/lp10"
xmlns:lp20="htt p://mydomain.compri nters/lp20"
...
<destination1 >
<lp10:configura tion>
<lp10:mapsBackT oBCISClass>W</lp10:mapsBackTo BCISClass>
<lp10:queueType >psfOther</lp10:queueType>
<lp10:formfontF ilters>/dev/fs/E/PrintApps/LBM/filters/</lp10:formfontFi lters>
<lp10:formfontP ath>/dev/fs/E/PrintApps/LBM</lp10:formfontPa th>
<lp10:jobName>$ (cat ${optionsInputT extFile} | awk '{print $1}' |
awk -F= '{print $2}')</lp10:jobName>
<lp10:optionsIn putTextFile>${L PSDIR}/${DEST}/o.${SEQ}</lp10:optionsInp utTextFile>
<lp10:dataInput TextFile>${LPSD IR}/${DEST}/p.${SEQ}</lp10:dataInputT extFile>
<lp10:chequeOut putPCLFile>${LP SDIR}/${DEST}/cheque.${SEQ}</lp10:chequeOutp utPCLFile>
<lp10:pclOutput PCLFile>${LPSDI R}/${DEST}/file.${SEQ}</lp10:pclOutputP CLFile>
<lp10:billsOutp utTextFile>${da taInputTextFile }.bill</lp10:billsOutpu tTextFile>
<lp10:changeDat e>$(date "+%Y-%m-%d")</lp10:changeDate >
<lp10:splitOn>$ ( head -n 1 ${dataInputText File} | cut
-c2-4)</lp10:splitOn>
...
</lp900:configura tion>
</destination3>
</development>
</print-control>

What I need is an xsl or something which will let me go through the
document and create a table ...

I've played around with xsl and xslt and seem to run into issues when I
find that I need to process the
namespaces....

There must be an easy way to do it
...
Is this possible using xsl or xslt and if so, how do I reconcile the
namespaces?

>
Any programming language with decent XML libraries can be used instead ofXSLT.
>
Your data contains some references to AWK. Perhaps you could try xmlgawk:
>

Page not found - SourceForge.net

http://sourceforge.net/projects/xmlgawk

Free, secure and fast downloads from the largest Open Source applications and software directory - SourceForge.net

Regards.
--
Manuel Collado - http://lml.ls.fi.upm.es/~mcollado

**Joe Kesselman** · Nov 21 '06, 04:15 AM

Re: formatting xml with namespaces

A smaller (and complete) sample would have been more useful; easier to
read and to discuss. So would a more specific description of what
"issues" you run into when you "need to process the namespaces".

Handling namespaces in XSLT should be easy enough -- to reference a
namespaced element or attribute, you need to define a prefix in the XSLT
that refers to the same namespace, and use that in your paths and
patterns. It's common, but not necessary, to use the same prefix in the
stylesheet that you use in your source documents. One complication: In
their 1.0 versions, XPath and XSLT can't set a default namespace; you
must use a prefix in the stylesheet even if your source document used
the default shorthand.

As others have noted, if you want to deliberately ignore the namespaces
-- which is a VERY BAD idea, since you wouldn't have used namespaces in
the first place if they weren't semantically significant! -- you can
kluge that by using wildcard patterns combined with predicates that
explicitly test only the localname, or (if you want to completely bollox
the intent and make other developers curse your name) the prefix and/or
qname.

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

formatting xml with namespaces

formatting xml with namespaces

Comment

Comment

Comment

Comment

Comment