xslt « WordPress.com Tag Feed

erayizgin — Fri, 27 Nov 2009 17:58:32 +0000

XSLt,XML veri dosyasında bulunan elementler üzerinde seçme ve bu seçime göre çıktı üretebilen şablonlar ve direktifleri kullanır.Şablon içindeki direktifler,veri dosyası içindeki elementlerin bağlarını seçme ve bu seçime göre işlenen verilerin çıktısını formatlamayı sağlar.

PHP ve XSLT ile XML verilerinin İşlenmesi

rssxsl.xsl

<?xml version=”1.0″ encoding=”ISO-8859-9″ ?>
<xsl:stylesheet version=”1.0″xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”>

<xsl:output method=”xml” encoding=”ISO-8859-9″ />

<xsl:template match=”/”>

<html>

<body>

<xsl:apply-templates select=”rss/channel”/>

</body>

</html>

</xsl:template>

<xsl:template match=”item”>

Baslik:<xsl:value-of select=”title”/></br>

Link:<xsl:value-of select=”link”/></br>

Aciklama:<xsl:value-of select=”description”/></br>

<hr/>

</xsl:template>

</xsl:stylesheet>

Recuperar información de una base de datos y mostrarla en un webBrowser (C#, PHP, XML, XSLT)

admin — Sun, 22 Nov 2009 19:15:53 +0000

Código fuente ejemplo que recupera información de una base de datos y la muestra en el webbrowser de

XML Message Forum in PHP & XML

Manoj Gumber — Sun, 22 Nov 2009 12:29:28 +0000

I had coded this message forum as part of an assignment. This is a really very simple message forum using only PHP and XML and no database required. It just illustrates the concepts of

XML
XSLT
DOM
XPATH

You can download this forum here.

It contains a readme.txt file which explains how to use this.

Using xsl:value-of inside an html tag

Manoj Gumber — Wed, 18 Nov 2009 08:47:26 +0000

I was working on an xml assignment when I came across this problem. While writing xsl sheet for an displaying an xml file , I had to use <xsl:value-of > element inside an html tag or any other tag. But with normal syntax , things were not working. Stumbling on some books and xslt documentation , I found a way out.

Attribute Value Templates are solution for this problem.

e.g when you use,

<a href=’<xsl:value-of select=”/page/results/prevnext/@prevresult”>’ >Previous</a>

It results in errors. The correct way using AVT is

<a href=”{/page/results/prevnext/@prevresult”}>Previous</a>
Note the curly brackets { } which indicate the Attribute Value Template.

AVTs are a convenience method for you to insert the result of an expression

into an attribute value. Otherwise you would have to use the equivalent

long-hand approach:
<a><xsl:attribute name=”href”><xsl:value-of

select=”/page/results/prevnext/@prevresult”/></xsl:attribute>Previous</a>

Hope it is useful !!

Mapping fields from WoS API => LOM

Nick — Mon, 16 Nov 2009 10:05:08 +0000

This is my first attempt at mapping the fields returned from the WoS API to LOM – hopefully this can form the basis of an appropriate XSLT transformation.

As my template I’ve used the first record from Mike’s full query to the API which happens to be a book review. It might have been better to start with a journal article but we’ll obviously need to look at the full range of records (N.B. Will we actually be able to return <doctype> when API restrictions are applied?)

Metadata	WoS API field[s]	LOM field[s]
Record unique identifier	<ut>ISI UT identifier</ut>	<lom:identifier><lom:entry>ISI UT identifier</lom:entry></lom:identifier>
		<ns0:bibliographicCitation xmlns:imsmd=”http://www.imsglobal.org/xsd/imsmd_v1p2″>
Source title	<source_title>TITLE</source_title>	<ns0:title><ns0:string >TITLE</ns0:string></ns0:title>
Volume/issue/pages/Date (month/year)	<bib_id>31 (7): 1116-1117 NOV 2009</bib_id>	<ns0:volume>31</ns0:volume><ns0:issue>7</ns0:issue><ns0:date>NOV 2009</ns0:date>
Pages	<bib_pages begin=”1116” end=”1117” pages=”2“>1116-1117</bib_pages>	<ns0:spage>1116</ns0:spage><ns0:epage>1117</ns0:epage>
		</ns0:bibliographicCitation>
Date(year)/volume	<bib_issue year=”2009” vol=”31” />	<ns0:volume>31</ns0:volume><ns0:date>NOV 2009</ns0:date>
Item title	<item_title>ITEM TITLE</item_title>	<lom:title><lom:string >ITEM TITLE</lom:string></lom:title>
Author(role/name)	<authors count=”1“><primaryauthor>Robertson, S</primaryauthor><fullauthorname> <AuRole>Author, Reprint Author</AuRole> <AuLastName>Robertson</AuLastName> <AuFirstName> Steve</AuFirstName> <address number=”1“>Leeds Metropolitan Univ, Ctr Mens Hlth, Leeds LS1 3HE, W Yorkshire, England</address> <AuCollectiveName> Robertson, Steve</AuCollectiveName> </fullauthorname></authors>	<lom:lifeCycle><lom:contribute><lom:role><lom:source>LOMv1.0</lom:source><lom:value>author</lom:value></lom:role><lom:entity>BEGIN:vcard FN:Steve Robertson END:vcard</lom:entity></lom:contribute> </lom:lifeCycle>

The XML for the record is reproduced below with relevant fields emphasise in red/bold:

<REC inst_id="0" recid="184349093" hot="yes" sortkey="3067387552" timescited="0" sharedrefs="0" inpi="false">
 <item issue="184349006" recid="184349093" coverdate="200911" sortkey="3067387552" refkey="5892051" dbyear="2009">
  <ut>000271043700017</ut>
  <i_ckey>ROBE1116090031SS</i_ckey>
  <i_cid>0130983640</i_cid>
  <source_title>SOCIOLOGY OF HEALTH & ILLNESS</source_title>
  <source_abbrev>SOCIOL HEALTH ILL</source_abbrev>
  <item_title>Men’s Health: Body, Identity and Social Context</item_title>
  <sq>06031J0</sq>
  <bib_id>31 (7): 1116-1117 NOV 2009</bib_id>
  <bib_pages begin="1116" end="1117" pages="2">1116-1117</bib_pages>
  <bib_issue year="2009" vol="31"/>
  <doctype code="B">Book Review</doctype>
  <editions full="SSCI"/>
  <languages count="1">
   <primarylang code="EN">English</primarylang>
  </languages>
  <reviewed_work>
   <rw_langs count="1">
    <rw_lang code="EN">English</rw_lang>
   </rw_langs>
   <rw_authors count="2">
    <rw_author>Broom, A</rw_author>
    <rw_author>Tovey, P</rw_author>
   </rw_authors>
   <rw_year>2009</rw_year>
  </reviewed_work>
  <authors count="1">
   <primaryauthor>Robertson, S</primaryauthor>
   <fullauthorname>
    <AuRole>Author, Reprint Author</AuRole>
    <AuLastName>Robertson</AuLastName>
    <AuFirstName>Steve</AuFirstName>
    <address number="1">
    Leeds Metropolitan Univ, Ctr Mens Hlth, Leeds LS1 3HE, W Yorkshire, England
    </address>
    <AuCollectiveName>Robertson, Steve</AuCollectiveName>
   </fullauthorname>
  </authors>
  <reprint>
   <rp_author>Robertson, S</rp_author>
   <rp_address>Leeds Metropolitan Univ, Ctr Mens Hlth, Leeds LS1 3HE, W Yorkshire, England</rp_address>
   <rp_organization>Leeds Metropolitan Univ</rp_organization>
   <rp_suborganizations count="1">
    <rp_suborganization>Ctr Mens Hlth</rp_suborganization>
   </rp_suborganizations>
   <rp_city>Leeds</rp_city>
   <rp_state>W Yorkshire</rp_state>
   <rp_country>England</rp_country>
   <rp_zips count="1">
    <rp_zip location="AC">LS1 3HE</rp_zip>
   </rp_zips>
  </reprint>
  <research_addrs count="1">
   <research>
    <rs_address number="1">Leeds Metropolitan Univ, Ctr Mens Hlth, Leeds LS1 3HE, W Yorkshire, England</rs_address>
    <rs_organization>Leeds Metropolitan Univ</rs_organization>
    <rs_suborganizations count="1">
     <rs_suborganization>Ctr Mens Hlth</rs_suborganization>
    </rs_suborganizations>
    <rs_city>Leeds</rs_city>
    <rs_state>W Yorkshire</rs_state>
    <rs_country>England</rs_country>
    <rs_zips count="1">
     <rs_zip location="AC">LS1 3HE</rs_zip>
    </rs_zips>
   </research>
  </research_addrs>
  <abstract avail="N"/>
  <refs count="1">
   <ref>184349094</ref>
  </refs>
 </item>
</REC>

As Mike points out, we should bear in mind that there are variations in the fields that come back from the WoS API, for example: bib_id – depends on what bib data has been entered into WoS; authors – The level of detail varies here too, sometimes there is no full author name and so on….all of which will impact on the sophistication we require from the XSLT.

My Year at Harcourt Publishing - XSL-FO

jewelsjacobs — Sat, 14 Nov 2009 20:48:12 +0000

After getting pregnant with sweet baby boy number 2 My husband and I felt the 24-7 life of business ownership was not an ideal situation for an infant and newborn. Both they, and we, needed consistent structure. Someone needed to get a real job.

Because my husband had focused more on the printing side of our business and I the web design / server admin / development, it was thought I would have a better chance of making more money.

With belly still deflating and memory shot from sleep deprivation I entered back into corporate life after 8 years with a contract at Harcourt Publishing thanks to Donna Quinn at COMSYS.

I started out as a Visual Designer working with a talented UI designer under a brilliant Usability expert Karen Bachmann. I got a chance to work on an Ajax / Java app with Riptide – the brilliant Java Shop. The folks at Riptide, including a fantastic developer by the name of Moe Treibiz, were awesome and I learned a lot from them. I saw how Project Management was expertly handled by North Highland. I watched them at work their craft with awe.

The best part, however, was the opportunity I got to develop a PDF generation system with XSL-FO without knowing anything about it before hand thanks to Fred Ganter – at the time the lead of the Content group. This esoteric skill would open doors for me down the road.

I was introduced to so many wonderful technologies, methodologies and people in such a short period of time.

Quick sketch #2

Nick — Fri, 13 Nov 2009 09:15:55 +0000

The diagram below is Arthur’s update of my earlier quick sketch to illustrate what Bibliosight will aim to achieve by the formal #jiscri deadline.

It is numbered and colour coded – stages 1 – 3 (shades of blue) are within the #jiscri timeframe; stages 2 (green) & 5 (buff) will require ongoing work beyond the deadline.

(N.B. Click on the image for a full size view in a separate browser window.)

Mobile programming and expanding menus with XSLT

shirl9141 — Tue, 03 Nov 2009 11:11:39 +0000

I’m working a new project in my web development class, CSCI E-153 and would like to share some of the technologies that we are using. The class includes XML, XSLT, XSL-FO, JSON, AJAX, etc and has been a lot of fun so far. The project we are working on entails XML data files transformed into a collection of well-structured web pages by using XML style sheets, XSLT.

My enviroment consist of the Mac OS(Leopard), Apache Tomcat, and Cocoon. I’ve tried using the online Opera Mini simulator to test my application, but it only works for online apps. So, localhost won’t work. Although, if you prefer to work in the cloud, Amazon EC2 is a good place to start. So, I’m testing with the online IPhone simulator, which is really nice and convenient. If you would like to use a simple browser to test your application for the mime-type, application/vnd.wap.xhtml+xml, the XHTML Mobile profile add-on for Firefox is available to download. The ECMAScript, JavaScript, ActionScript, and JScript, used with the Firefox add-on was Javascript for expanding menus to free up the real estate. Below is the Javascript function to show or hide the menus based on the class attribute.

function showMenu(obj)

{

	if (obj.className==’normal’)
		obj.className = ‘expand’;
	else
		obj.className = ‘normal’;

}

The css stylesheet will look like this.

.normal ul
{
	display:none;
}
.expand ul
{
	display:block;
}

Now we can look at the XSLT portion of the code. This line of code sets the variable $id_name to the current-grouping-key() in a for-each-group loop that groups all the elements in the XML file by a key. All the spaces are replaced by underscores since spaces are not allowed in the id name.
<xsl:variable name="id_name" select="replace(current-grouping-key(),' ','_')"/>

Next we set the onclick event in the ul element, which calls the Javascript function above to show/hide the menus. We also replace the commas with underscores. Of course, we could have nested the replace functions and then set the variable $id_name or make a new template function and call it recursively until we have replaced all the commas, spaces, tabs, etc.

<ul onclick="javascript:showMenu(this)" id="{replace($id_name,',','_')}" class="normal">

<li><xsl:value-of select="normalize-space(current-grouping-key())"/> more code …..

</li></ul>

Make sure the ul element is assigned an id, otherwise the showMenu(this) will not work.

Senior Web Developer

Michelle — Wed, 28 Oct 2009 03:00:32 +0000

Our client in SAN MATEO, CA, is looking for a SENIOR WEB DEVELOPER for front-end development of next generation data modeling and visualization tools. The ideal candidate would have expertise in front end development of complex Rich Internet Applications (RIA) and have demonstrated the ability to develop high quality enterprise software in a dynamic environment.

Responsibilities

Develop front end of Rich Internet Applications for Java-based server products
Analyze functional requirements and specifications through close interaction with Product Management and other team members
Participate in product design and architectural discussions
Write unit tests to ensure developed user interfaces meet product requirements
Provide support to the QA and support organizations
Provide feedback and guidance to technical writers
Develop appropriate documentation for architectural, design, implementation and test activities.

Required Skills

Bachelor’s degree in Computer Science (or related field of study)
Minimum of 6 years experience with front end development of Web-based user interfaces
Minimum of 2 years experience with front end development of rich internet applications (RIA)
Expertise in building applications using the following technologies: Flex 3/4, Flash Action Script, HTML, DHTML, JavaScript, JSON, CSS
Experience with the following tools: Maven, ANT, Subversion, CVS
Familiar with cross browser support issues and solutions as well as i18n issues and solutions
Experience doing software development in a structured, automated, and distributed development environment including design, development, QA, and documentation.
Strong communication skills with the ability to present technical concepts concisely to non-technical members of the team.

Nice to Have:

Familiarity with existing data modeling tools is a plus: ER/Studio ERWin, TOAD
Experience in building applications using any of the following technologies is a plus: JSP, Struts, JavaScript, JQuery, SEAM, GWT, Rich Faces, extjs, XML/XSLT, AIR

If you are interested, please send us your resume to raj@mindsource.com.

DownLoad Excel MultiSheet

kuanglian2000 — Mon, 26 Oct 2009 10:48:18 +0000

這裡是asp.net Code的部份，這裡作了一個Excel檔案。

protected string ExportExeclByXSLT_Direct(DataSet dsReportData)
{
string fileName = “././DownLoadFile/ExcelExport.xls”;
string xslPath = “././Xsl_Template/Excel.xslt”;
string xlsPath = “././DownLoadFile/ExcelExport.xls”;
StreamWriter oExcelWriter = System.IO.File.CreateText(Server.MapPath(xlsPath));
try
{
XmlDataDocument xddData = new XmlDataDocument(dsReportData);
XslCompiledTransform xt = new XslCompiledTransform();
xt.Load(Server.MapPath(xslPath));
xt.Transform(xddData, null, oExcelWriter);
return fileName;
}
catch (Exception ex)
{
return “”;
}
finally
{
oExcelWriter.Close();
}
}

這裡是Excel下載的頁面(DownLoad.aspx)

protected void Page_Load(object sender, EventArgs e)
{
NameValueCollection coll = Request.QueryString;
String strRequest = coll["file"];
if (strRequest != “”)
{
String path = Server.MapPath(strRequest);
FileInfo file = new FileInfo(path);
StreamReader sr = null;
try
{
if (file.Exists)
{
//Method-1 將檔案資料讀入Stream,這時檔案已經可以刪除了..之後再把檔案內容輸出即可
//Read File Content
sr = new StreamReader(path);
Response.Clear();
Response.AddHeader(“Content-Disposition”, “attachment; filename=ExcelExport.xls”);
Response.AddHeader(“Content-Length”, file.Length.ToString());
Response.ContentType = “application/vnd.ms-excel”;
Response.Write(sr.ReadToEnd());
Response.End();

//Method-2 這是第二個方法,直接把檔案內容寫到前端,此時是不允許將檔案給刪除的,因為檔案是讀取的目標
//Response.Clear();
//Response.AddHeader(“Content-Disposition”, “attachment; filename=ExcelExport.xls”);
//Response.AddHeader(“Content-Length”, file.Length.ToString());
//Response.ContentType = “application/vnd.ms-excel”;
//Response.WriteFile(file.FullName);
//Response.End();

}

}
catch
{

}
finally
{
if (sr != null) sr.Close(); //Close Reader 注意:要記得把連接關閉
if (file.Exists)file.Delete(); //Delete Temp DownLoad File
}
}
}

這裡是XSLT的部份，負責將DataSet轉換成Excel的XML資料

<xsl:stylesheet version=”1.0″
xmlns=”urn:schemas-microsoft-com:office:spreadsheet”
xmlns:xsl=”http://www.w3.org/1999/XSL/Transform”
xmlns:msxsl=”urn:schemas-microsoft-com:xslt”
xmlns:o=”urn:schemas-microsoft-com:office:office”
xmlns:x=”urn:schemas-microsoft-com:office:excel”
xmlns:ss=”urn:schemas-microsoft-com:office:spreadsheet” >

<xsl:template match=”*”>
<ss:Workbook xmlns:ss=”urn:schemas-microsoft-com:office:spreadsheet”>
<ss:Worksheet ss:Name=”Main”>
<ss:Table>
<!–資料標題–>
<ss:Row>
<xsl:for-each select=”Main[position() = 1]/*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”local-name()”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
<xsl:for-each select=”Main”>
<!–資料內容–>
<ss:Row>
<xsl:for-each select=”*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”.”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
</xsl:for-each>
</ss:Table>
</ss:Worksheet>
<ss:Worksheet ss:Name=”HQ_Detail”>
<ss:Table>
<!–資料標題–>
<ss:Row>
<xsl:for-each select=”HQ_Detail[position() = 1]/*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”local-name()”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
<xsl:for-each select=”HQ_Detail”>
<ss:Row>
<xsl:for-each select=”*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”.”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
</xsl:for-each>
</ss:Table>
</ss:Worksheet>
<ss:Worksheet ss:Name=”NL_Detail”>
<ss:Table>
<!–資料標題–>
<ss:Row>
<xsl:for-each select=”NL_Detail[position() = 1]/*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”local-name()”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
<xsl:for-each select=”NL_Detail”>
<ss:Row>
<xsl:for-each select=”*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”.”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
</xsl:for-each>
</ss:Table>
</ss:Worksheet>
<ss:Worksheet ss:Name=”CH_Detail”>
<ss:Table>
<!–資料標題–>
<ss:Row>
<xsl:for-each select=”CH_Detail[position() = 1]/*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”local-name()”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
<xsl:for-each select=”CH_Detail”>
<ss:Row>
<xsl:for-each select=”*”>
<ss:Cell>
<ss:Data ss:Type=”String”>
<xsl:value-of select=”.”/>
</ss:Data>
</ss:Cell>
</xsl:for-each>
</ss:Row>
</xsl:for-each>
</ss:Table>
</ss:Worksheet>

</ss:Workbook>
</xsl:template>

</xsl:stylesheet>

Insert [content data] into HTML control - XSLT

lifeisimple — Fri, 23 Oct 2009 04:37:19 +0000

The first example is more verbose than the second, as the second uses the shortcut method of including commands inside existing tags such as the anchor (a) tag. The first example uses the xslt commands to inject the attribute into the preceding tag

<ul>

<xsl:for-each select=”$currentPage/node”>

<li><a>

<xsl:attribute name=”href”>

<xsl:value-of select=”umbraco.library:NiceUrl(current()/@id)”/>

</xsl:attribute>

<xsl:value-of select=”current()/@nodeName”/>

</a></li>

</xsl:for-each>

</ul>

<ul>

<xsl:for-each select=”$currentPage/node”>

<li><a href=”{umbraco.library:NiceUrl(current()/@id)}”>

<xsl:value-of select=”current()/@nodeName”/>

</a></li>

</xsl:for-each>

</ul>

Transforming XML with XSLT in PHP

Prabir Choudhury — Thu, 15 Oct 2009 11:00:50 +0000

DOM object. DOM stands for the Document Object Model, and it’s a way of representing a documen

New Image Search and Catalogue Pages

spcoll — Fri, 09 Oct 2009 19:45:18 +0000

Continuing the theme from our last post, Redesigning our Web Presence, here is a closer look at how we built the new Image Search feature as well as what it takes to create the catalogue pages showing the detailed holdings of our collections.

New Image Search Feature

Our main web search feature, now on all of our pages, is provided by Oregon State’s campus search engine running the Nutch software. This software works similar to Google and has web crawlers that find web pages and indexes them for searching. Each Documentary History website and Linus Pauling Day-by-Day have a search box that limits results to the pages and items on only that site.

However, the main search feature on the OSU Libraries homepage does not use the campus engine, and our websites and digital objects were not included. The Library’s search feature is powered by LibraryFind, built by a team at OSU using the Ruby on Rails web application software. LibraryFind harvests and indexes many records and data sources, but does not crawl web pages. We needed to get our records harvested by and indexed into LibraryFind.

Since our digital object records are stored using the METS format with MODS metadata, it was fairly easy to convert this to Dublin Core metadata, which can then be served up by an OAI-PMH provider. LibraryFind then checks our OAI-PMH provider and harvests our digital object metadata for indexing into LibraryFind. Thanks to Terry Reese for his assistance on setting up the provider software and for his work on LibraryFind.

One piece of metadata that our METS records didn’t have that we needed to add was a URL where the digital object sits once it’s part of our Documentary History websites or Linus Pauling Day-by-Day. Our own scripts and stylesheets didn’t need this information, since they built the pages, but LibraryFind needed the URL to know where to provide a link to from search results that included our digital objects. This required adding:

<mods:location><mods:url access="object in context" displayLabel="Linus Pauling and the Race for DNA: A Documentary History. Pictures and Illustrations.">
http://osulibrary.oregonstate.edu/specialcollections/coll/pauling/dna/pictures/1948i.61.html
</mods:url></mods:location>

as appropriate to our metadata files.

Now that our digital objects are harvested into LibraryFind, they are included in results for searches done from the Library’s homepage. We can also limit the search results to just our materials, and by turning on the image results view, we get our new Image Search functionality. Now it is easy to search for digitized materials that are online, including photographs, scans of documents, and more.

Image Search results, powered by LibraryFind

In the future, we plan to include more of our digital objects and increase support for complex items and multimedia files.

Building Catalogue Pages from EAD

Each of our collections are stored in Encoded Archival Description (EAD) XML files, which include collection information as well as detailed catalogue listings for most of our collections. Often these descriptions go down to the item level, and there are varying levels and hierarchies in use, depending on what was appropriate for the material. The EAD files are processed by XSLT stylesheet files, similar to the rest of our website, and ideally we’d like to have a single set of files that can handle the different description levels and that we don’t have to tweak for specific collections. Here is a snippet of EAD XML for the Pauling Photographs series:

<c02 level="file">
<did>
<container type="box">1933i</container>
<unittitle>Photographs and Images related to Linus Pauling, <unitdate>1933</unitdate>.</unittitle>
</did>

<c03 level="item">
<did>
<container type="folder">1933i.1</container>
<unitid audience="internal">1311</unitid>
<unittitle>Linus Pauling at OSU (Oregon Agricultural College) to receive an honorary doctorate of science. Pictured from left are Dr. Marvin Gordon Neale, president of the University of Idaho, David C. Henny, Linus Pauling, Chancellor W. J. Kerr, and Charles A. Howard, state superintendent of public instruction in Oregon. June 5, 1933. "LP at OSU (OAC) honorary doctorate 1933" Photographer unknown. Black and white print courtesy of the Oregon State University Archives.</unittitle>
<unitdate>1933</unitdate>
</did>
</c03>

<c03 level="item">
<did>
<container type="folder">1933i.2</container>
<unittitle>D.C. Henny, C.A. Howard and Linus Pauling. Linus Pauling receiving an honorary degree from Oregon Agricultural College. Print courtesy of the Oregon State University Archives. Photographer unknown. Black and white print.</unittitle>
<unitdate>1933</unitdate>
</did>
</c03>

Our previous setup for processing catalogues was heavily modified from older EAD Cookbook stylesheet files and contained a large amount of custom code. One of the major sections we added was code that split up very large sections and box listings into separate web pages that were a reasonable size, instead of presenting hundreds of boxes or folders on each page. To accomplish this, the stylesheet used to first make a temporary file that built a high-level ‘menu’ of the catalogue, which had a range for each page that was to be created. The rest of the stylesheet would then use this menu file to determine what pages to create, and searched over the whole collection for the IDs of the start and end of each page. This was complicated by the fact that some box IDs are not easy to compare numerically, such as ‘1954h3.4′ or ‘NDi.2′. Usually the alphabetic characters were replaced with numbers or punctuation to facilitate comparing them against each other. This technique was not very efficient for large sections, and required lots of tweaking to be able to handle all the various box and folder IDs we have.

Also, separate stylesheet files had to be created to better handle the Pauling Papers since it was so much larger than anything else, which meant that it was a pain to maintain features in both sets of stylesheet files. For the newer set of catalogue XSLT stylesheet files, we took a few different approaches.

First, a lot of redundant code was eliminated through the use of more XSLT matching templates. These allow you to write one set of formatting code and reuse it whenever an element appears. This made it easier to work around EAD’s flexibility for container lists, so a series or box would get processed the same no matter where it was in the encoded hierarchy. Here are some examples of the EAD matching templates:

<xsl:template match="ead:unittitle">
<xsl:apply-templates/>
<xsl:if test="not(ends-with(., '.'))">.</xsl:if>
<xsl:text> </xsl:text>
<xsl:if test="following-sibling::ead:unittitle"><br/></xsl:if>
</xsl:template>

<xsl:template match="ead:unitid[@type]">
<xsl:choose>
<xsl:when test="@type = 'isbn'">
  <a class="nowrap" href="http://www.worldcat.org/search?q=isbn%3A{replace(., '-', '')}" title="Look up this title in WorldCat"><xsl:value-of select="."/></a></xsl:when>
<xsl:when test="@type = 'oclc'">
  <a class="nowrap" href="http://www.worldcat.org/search?q=no%3A{.}" title="Look up this title in WorldCat"><xsl:value-of select="."/></a></xsl:when>
<xsl:when test="@type = 'lcc'">
  <a class="nowrap" href="http://oasis.oregonstate.edu/search/c?SEARCH={replace(., ' ', '+')}" title="Look up this title in the OSU Libraries' catalog"><xsl:value-of select="."/></a></xsl:when>
<xsl:when test="@type = 'gdoc'">
  <a class="nowrap" href="http://oasis.oregonstate.edu/search/?searchtype=g&amp;searcharg={replace(replace(., ' ', '+'), '/', '%2F')}" title="Look up this title in the OSU Libraries' catalog"><xsl:value-of select="."/></a></xsl:when>
<xsl:otherwise><xsl:value-of select="."/></xsl:otherwise>
</xsl:choose>
</xsl:template>

Second, the code to break long sections into smaller pages for web display was redone, this time using the position of a box or item instead of the IDs. IDs are still used for display purposes, but the output is all based on position (such as 1-10, 11-20, etc.) This code is much cleaner since IDs are no longer directly compared. It’s also faster since it deals with the pages sequentially and doesn’t loop over the whole section every time a page is processed.

Example of new catalogue page of Pauling Correspondence

Third, instead of using HTML tables for the columns layout of catalogue pages, we switched to a CSS-based layout that approximates the look of columns and indents. This requires much less code in both the XSLT for processing and the output files.

Finally, all catalogues are processed by the same set of files, and separate ones for the Pauling Papers are no longer needed. This will enable us to make improvements faster, expanding our links to digital content and increasing the access options for our materials.

Back in the Saddle Again

matthewgraybosch — Thu, 08 Oct 2009 17:50:49 +0000

Here I am, blogging on my lunch break on my second day working for Conduit IT. I’ve already im

Xselerator

myfog — Wed, 07 Oct 2009 10:58:04 +0000

Sito: Xselerator

Xselerator è un comodo validatore/trasformatore di xml e xsl..

Per essere free, è davvero curato.. non esegue soltanto operazioni basilari come la trasformazione ma permette anche il debug dell’xsl e molto altro..

Al giorno d’oggi, con tutto Xml che gira, è uno strumento indispensabile

Unemployed no more!

matthewgraybosch — Mon, 05 Oct 2009 23:49:48 +0000

YES!! I’ve got a new job. Last Thursday, I answered an ad on Craigslist for somebody who can d

XML-In-Practice Conference Notes, Day Two

xmlgeek — Thu, 01 Oct 2009 18:05:48 +0000

Started out on time, but Mills Davis had a lot to share and we went over. Talking about the use of XML in research, publishing, databases, and future tools is somewhat comfortable, in that we have had these conversations before. The tools change from year to year, but the requirements stay pretty close to the same. We just need to go further every year.

eGovernment sessions, right now we are talking about publishing using DITA. Now this is interesting. I need more information and have found lots of websites and also people who I can email or call when I have questions. The training still needs to be done at my customers site. They will not have success unless they start to understand what they are working with.

Some of the case studies I have seen this morning and yesterday actually feel kinda old, they don’t seem to use any of the new technologies. Does this mean the new technologies don’t work?

And/Or is it possible, that these systems they are building don’t truly work! Or don’t work well, and they are difficult to maintain or use? I have real questions about this. Having been around for a true failure at my customer site, and watching the reasons unfold in front of me, I also think people tend to get in their own way when taking on projects like this.

Quick sketch

Nick — Thu, 01 Oct 2009 12:10:24 +0000

I’ve just had a meeting with Sue and Sam (from URO) about use cases. It was useful, as always, to put our heads together and we came up with a quick sketch of a potential infrastructure for Bibliosight that we would like feedback on:

A quick sketch

N.B. This assumes it is possible to programmatically bulk upload XML records to EndNote – I have no idea if this is possible – and to intraLibrary which should be possible based on discussion at the meeting on Tuesday.

The sketch arose from the fact that research administrators currently use EndNote which they wish to continue using as dedicated citation management software for its high level functionality and the need to simplify their workflow rather than expect them to add records to two separate systems. Such an approach could also inform our developing use cases to a) auto-populate the repository with metadata from WoS and b) alert repository/research administrators when an article is published so we can pursue an appropriate full text version for the repository.

XML-In-Practice Conference Notes - Day One

xmlgeek — Wed, 30 Sep 2009 13:39:18 +0000

Sitting waiting for the first speaker at the conference (Clement McDonald, Lister Hill Center). Lots of people, some old familiar faces. Really excited about the technical side of the conference.

First speaker is Medical HL7 XML….not something I know a lot about. Interesting, but not going to help me with my day to day work. Have you ever heard of Health Information Exchange – HIE? They want to be more efficient, to share data across systems, across insurance companies, across doctors. My biggest concern would be the security of our data….who is going to have access to this data?

Next speaker I am sitting in on is G. Ken Holman, my fellow colleague in UBL, he is still working with UBL and has actually spent many cycles working on the Code List issues. I am going to talk to him about this later.

Ken’s talk is about”The problem being solved with markup.” This is probably the wrong session for me to be sitting in on. Very foundational stuff, what is XML, etc. I know I can get something out of this…..UBL……31 different business documents with a common vocabulary that is standardized and ready to use – YIPEE. Did you know, in the country of Denmark, since 2005, you have to use XML, and, they are using UBL – Universal Business Language. http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl

Another issue that keeps coming to me, is how do I get my staff members up and running with some of these technologies? I need them to learn XML, XSLT, XSL-FO, XPath, and XQuery. Okay, so how, assuming they want to be XML “geeks”?

The discussion about DITA has been lively. Some opinions say DITA is just another DocBook, and other opinions seem to say its better, its here and it works. I remember clearly when DocBook came onto the scene and how excited people were about it. I think they both have their place, and should be used according to need.

Traditional publishing models don’t work anymore. You have to take into account how many different outputs you will need from your data and what it is going to take to get them. Traditional publishing is slow and by the time you are printing, your data may be out of date. Getting output for online, print, CD/DVD for users offline, different websites with different purposes, and many more.

I want to hear less about what you think your company can do, and what you actually have done and is working….

Tonight they are having a demo competition, everyone bring your laptops!

Pretty printing xhtml with nokogiri and xslt

emmanueloga — Tue, 29 Sep 2009 04:06:30 +0000

Today I was looking for a way to pretty print xhtml. Good’ol REXML supports this in a very simple way:

Document.new("<some>XML</some>")doc.write($stdout, indent_spaces = 4)

This generates a nicely indented xml document. But REXML was not robust enough for my needs. Luckily, we now have a couple of excellent choices on ruby for parsing xml, including hpricot, nokogiri and libxml-ruby bindings.

I did not find a way to pretty print xhtml as easy as you can do with REXML with any of these libraries, though. But I did find a way of doing it using XSLT. Nokogiri supports applying XSLT to an XML document (probably libxml bindings do too, hpricot does not). Here is how:

    xsl = Nokogiri::XSLT("pretty_print.xsl")
   html = Nokogiri(File.read("source.html"))
   File.open("output.html", "w") { |f| f << xsl.apply_to(html).to_s }

That’s it, simple enough. Got the idea from this dzone snippet.

For the xslt file I used this nice one I found on this site: http://www.printk.net/~bds/indent.html

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:output method="xml" encoding="ISO-8859-1"/>
  <xsl:param name="indent-increment" select="'   '"/>

  <xsl:template name="newline">
    <xsl:text disable-output-escaping="yes">
</xsl:text>
  </xsl:template>

  <xsl:template match="comment() | processing-instruction()">
    <xsl:param name="indent" select="''"/>
    <xsl:call-template name="newline"/>
    <xsl:value-of select="$indent"/>
    <xsl:copy />
  </xsl:template>

  <xsl:template match="text()">
    <xsl:param name="indent" select="''"/>
    <xsl:call-template name="newline"/>
    <xsl:value-of select="$indent"/>
    <xsl:value-of select="normalize-space(.)"/>
  </xsl:template>

  <xsl:template match="text()[normalize-space(.)='']"/>

  <xsl:template match="*">
    <xsl:param name="indent" select="''"/>
    <xsl:call-template name="newline"/>
    <xsl:value-of select="$indent"/>
      <xsl:choose>
       <xsl:when test="count(child::*) > 0">
        <xsl:copy>
         <xsl:copy-of select="@*"/>
         <xsl:apply-templates select="*|text()">
           <xsl:with-param name="indent" select="concat ($indent, $indent-increment)"/>
         </xsl:apply-templates>
         <xsl:call-template name="newline"/>
         <xsl:value-of select="$indent"/>
        </xsl:copy>
       </xsl:when>
       <xsl:otherwise>
        <xsl:copy-of select="."/>
       </xsl:otherwise>
     </xsl:choose>
  </xsl:template>
</xsl:stylesheet>

SharePoint Internal Data Types - Reference

sanghvinirav — Mon, 28 Sep 2009 12:45:48 +0000

Sharepoint supports different types of columns, this column types are reffered as following data typ

XQilla Project - XSLT 2.0 and XPath 2.0 for C++

dmaggot — Tue, 22 Sep 2009 22:30:39 +0000

When it comes down to XML, everybody knows Java is one of the most powerful programming languages to deal with this format. The Java XML API, the documentation and the size of projects such as Xerces, Xalan and Saxon make Java an excellent option to work with XML. But then again, I’m not a Java programmer and I love C++

I recently had to code a little project to simulate an automaton for a programming language. I used the FSMXML project to define the automaton, so I needed a good library to deal with XPath on C++. As I mentioned in my previous post, I discovered I needed XPath 2.0 for some queries, so on I went to find an XPath 2.0 library fo C++, since Xalan-C, as its Java counterpart, only supports version 1.0 of the specification.

I googled around and came accross XQilla which is an XQuery and XPath 2 library based on Xerces-C. It looked like something I could use for my project, so I searched a Sabayon package for that, but found none. I searched then for a Gentoo package for it, and even though I found one, there was something terribly wrong with it, which I didn’t fully understand… I think it was still on testings or something, but the thing is one of the versions was hard masked and the other needed a Xerces-C version I couldn’t install for some reason I don’t remember. But I still wanted to try the project out, so I downloaded the sources and built the libraries successfully without problems, except for a weird --with-xerces=/usr configuration option I had to add for the configure script to find Xerces-C headers (shouldn’t it default to /usr/include?). After a good amount of compile time (864 binary files outputted on the main directory) I had my working XPath 2 C++ library and I started using it by taking a look at the examples provided at the project’s homepage.

After understanding the modus-operandi of this library, I started incorporating it into my program. One API design I remember I immediately questioned was regarding these lines of code:

AutoRelease<DOMXPathExpression> expressionKeywords(document->createExpression(X("language/keywords/keyword/@name"), 0)); AutoRelease<DOMXPathResult> resultKeywords(expressionKeywords->evaluate(document, DOMXPathResult::ITERATOR_RESULT_TYPE, 0));

Here, document is declared as a DOMDocument. I wondered why, if I created the expression in the first line from the document itself, I had to pass the document again as an argument to the evaluate function. A few days later I discovered an answer for that: the DOMDocument object is the only one capable of creating an expression, but what if you want to apply the expression in the context of an internal node and not the document itself? That’s what the argument passed to the evaluate function indicates, as shown in these lines of code

AutoRelease<DOMXPathExpression> expressionMonoid(document->createExpression(X("n:label/n:monElmt/n:monGen/@value"), fsmxmlNamespace)); AutoRelease<DOMXPathResult> resultMonoid(expressionMonoid->evaluate(resultTransitions->getNodeValue(), DOMXPathResult::ITERATOR_RESULT_TYPE, 0));

Here, the expression created by the document object was evaluated using the resultTransitions DOMNode value as the context, which is exactly what I wanted to do.

One other trick I learned about XQilla (which may actually be regarded as a Xerces-C issue) was that it wouldn’t work if your XML Schema Definition was on a remote location and you had no internet because, of course, of validation problems. To avoid this, you must disable both XercesSchema and DOMValidateIfSchema options in your parser, as shown in the following lines

parser->getDomConfig()->setParameter(XMLUni::fgDOMNamespaces, true); parser->getDomConfig()->setParameter(XMLUni::fgXercesSchema, false); parser->getDomConfig()->setParameter(XMLUni::fgDOMValidateIfSchema, false);

I haven’t tested the XQuery capabilities of this library, but if you are going to use XSLT 2 in your C++, I can highly recommend this project.

User Interfacing with XSLT

Joel Stevick — Sun, 15 Nov 2009 14:29:54 +0000

If you feel that you must completely refactor an application so that the data model is cleanly seperated from the presentation, then you can use the XML-related technologies for this. You should use XSLT (expresses rules for how to convert XML data into something else like HTML content) to achieve this.