<?xml version="1.0" encoding="utf-8"?><!-- generator="b2evolution/1.9.3" -->
<rss version="0.92">
	<channel>
		<title>Map Of London</title>
					  <link>http://hcmc.uvic.ca/blogs/index.php?blog=41</link>
			  <description></description>
			  <language>en-CA</language>
			  <docs>http://backend.userland.com/rss092</docs>
			  			  <item>
			    <title>Various tweaks to XSLT and CSS</title>
			    <description> (Mins: 180) &lt;p&gt;Following a meeting at which we discussed strategy, and decided to focus for now on the Mayoral Pageants, worked with KMF on a range of minor display and rendering issues for primary source documents, including bylines, marginal labels, and text indents.&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=various_tweaks_to_xslt_and_css&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Beginning of tutorial for primary source encoding</title>
			    <description> (Mins: 180) &lt;p&gt;Started a tutorial based on SNOW1 (for the moment), and in the process of writing the first bit of it, came up against many annoyances in the rendering of egXML blocks; fixed those rendering issues (in three places, site, redesign, and codesharing. Grrr).&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=beginning_of_tutorial_for_primary_source&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Added handling for dramatic text tags</title>
			    <description> (Mins: 30) &lt;p&gt;Added rendering handling for sp, speaker, and p within sp. The stage tag isn't handled yet. Rolled out changes both to site and to redesign codebases.&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=added_handling_for_dramatic_text_tags&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Troubleshooting: encoded title page of SNOW1, found and fixed rendering bug</title>
			    <description> (Mins: 120) &lt;p&gt;Since SNOW1 was a bit of a mess at the beginning, because of the encoders following obsolete examples, I've manually encoded the title page as an example.&lt;/p&gt;

&lt;p&gt;Also found a problem with METR1 which was not really a bug, nor an encoding invalidity: a body element which goes straight to content (e.g. a head) with no intervening div is not invalid, but it triggered rendering problems because it was completely unexpected. As it happens, the encoding should not have been that way -- other divs appear later in the body -- but it wasn't technically wrong, so it would be good to figure out a way to prevent this through the schema or more likely through Schematron. We could change the content model of body so that it can only have divs, of course.&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=troubleshooting_encoded_title_page_of_sn&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Fixes and updates</title>
			    <description> (Mins: 120) &lt;p&gt;Did some tasks from yesterday and some new ones:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Files that used &lt;code&gt;&amp;lt;group&amp;gt;&lt;/code&gt; have now been converted to &lt;code&gt;&amp;lt;div&amp;gt;&lt;/code&gt;s. (The only exception is stow_1633, which probably does need &lt;code&gt;&amp;lt;group&amp;gt;&lt;/code&gt;.)&lt;/li&gt;
  &lt;li&gt;XSLT rendering has been updated to handle this.&lt;/li&gt;
  &lt;li&gt;Extra stray copies of METR1 have been identified in the db and removed. These were causing errors in the redesign pipeline.&lt;/li&gt;
&lt;/ul&gt;

</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=fixes_and_updates&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Meeting and tasks</title>
			    <description> (Mins: 120) &lt;p&gt;I have these tasks coming out of the team meeting today:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;DONE: Fix rendering of org popups.&lt;/li&gt;
  &lt;li&gt;DONE: Add Schematron constraint for malformed Julian dates.&lt;/li&gt;
  &lt;li&gt;DONE: Fix rendering of persNames with genName and roleName in them.&lt;/li&gt;
  &lt;li&gt;DONE (for group elements): Make a list of files containing group elements, and other bad old code.&lt;/li&gt;
  &lt;li&gt;DONE: Transform files with group elements into nested divs.&lt;/li&gt;
  &lt;li&gt;Add an attribute value parameter to the CodeSharing interface (will have to be done after July, probably).&lt;/li&gt;
  &lt;li&gt;Add handling for @style on list, along with documentation for it, change existing usage of list/@type to @style, then remove list/@type from schema.&lt;/li&gt;
  &lt;li&gt;DONE: Look at forme works in SNOW1 and figure out why they're not rendering properly.&lt;/li&gt;
  &lt;li&gt;Collapse the myth and fict personography types to a single type &quot;lit&quot;. This will involve both data and rendering and must be done simultaneously.&lt;/li&gt;
  &lt;li&gt;Add rendering for sp, speaker and stage for SNOW1.&lt;/li&gt;
  &lt;li&gt;In redesign (with Pat): make page credits work like page TOC (pop-out rather than long list).&lt;/li&gt;
&lt;/ul&gt;

</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=meeting_and_tasks&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>eXist build script</title>
			    <description> (Mins: 420) &lt;p&gt;I've spent the whole day working on getting a more flexible and successful build system for eXist. This is what I've added to Greg's script:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;It now checks for the presence of Saxon and warns if it's not available.&lt;/li&gt;
  &lt;li&gt;It checks for three XSLT files, and in each case, if the file is there, it transforms a target file in the build tree. These are for conf.xml.tmpl, mime-types.xml.tmpl, and controller-config.xml. This should allow us to set up build environments for each of our specific projects.&lt;/li&gt;
  &lt;li&gt;It excludes XML Calabash and includes FOP. The former was blocking the build because its download location is down.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Found a number of problems with eXist, which I've reported, including a bad one once the webapp is running: you can no longer call transform:transform with a relative path to the XSLT file, otherwise you get an error. A full path from /db seems to work.&lt;/p&gt;




</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=exist_build_script&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Wrote an eXist module for similarity metric comparisons</title>
			    <description> (Mins: 240) &lt;p&gt;I've now figured out how to create an extension module for eXist, following the instructions &lt;a href=&quot;http://www.exist-db.org/exist/apps/doc/extensions.xml&quot;&gt;here&lt;/a&gt;. These are some things I've learned:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;The only practical way to do this is to work with your module code in the context of the eXist tree, in $EXIST_HOME/extensions/modules/src/org/exist/xquery/modules.&lt;/li&gt;
  &lt;li&gt;You can use a non-eXist namespace -- I'm using &lt;a href=&quot;http://hcmc.uvic.ca/ns/usm&quot;&gt;http://hcmc.uvic.ca/ns/usm&lt;/a&gt; -- but it seems safest to use the eXist package structure, so my package is in org.exist.xquery.modules.unisimmetric.&lt;/li&gt;
  &lt;li&gt;All the extension modules are built together into a single jar called exist-modules.jar. You can build this jar alone, using &lt;code&gt;build.sh extension-modules&lt;/code&gt;, then drop that jar into an existing eXist instance (although if the new jar was built with a substantially different version from the rest of the code, there could well be problems).&lt;/li&gt;
  &lt;li&gt;To turn on your module, you add a line to the conf.xml file like this:
&lt;pre&gt;
&amp;lt;module uri=&quot;http://hcmc.uvic.ca/ns/usm&quot;                        class=&quot;org.exist.xquery.modules.unisimmetric.UniSimMetricModule&quot; /&amp;gt;
&lt;/pre&gt;
along with the other modules.
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm not yet happy with my module, and I'm still working on it. In particular, I'm not happy with the scores it's generating, and I think this might be something to do with other bits that get included in the GZIP stream, such as a header; if I can figure out how big those are, I can remove them from the calculation. The highest difference I seem to get is around 0.53 with completely dissimilar strings, so it seems as though the results are being compressed into a range much smaller than 0-1.&lt;/p&gt;

</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=wrote_an_exist_module_for_similarity_met&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Meeting and work on page-image-linking</title>
			    <description> (Mins: 240) &lt;p&gt;Team meeting, at which we discussed the use of ISE's facsimile viewer in MoEML (which will be easy enough to do, although it's based on a traditional db, and we'll have to replace that with proper TEI facsimile encoding).&lt;/p&gt;

&lt;p&gt;People also asked me to clarify how the EEBO linking works, so I've done that in the transcriptions documentation file, and I've also implemented the display of little page-images linking to the EEBO pages. Also, during today, &lt;code&gt;&amp;lt;address&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;addrLine&amp;gt;&lt;/code&gt; were added to the schema, with some basic display rendering.&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=meeting_and_work_on_page_image_linking&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  			  <item>
			    <title>Implemented a crude similarity metric in XQuery</title>
			    <description> (Mins: 180) &lt;p&gt;Lucene-based fuzzy matching seems to be very broken in the build of eXist I'm using, and in any case it's based on Levenshtein distance, so I've implemented a crude version of the USM/NCD algorithm in XQuery. It's a long way from ideal, though, because it's using base64 versions of strings rather than compressing the actual strings (this is all I can do with eXist's exposed gzip access); using zip seems to be punitive because it would require creating a file on the filesystem or in the db and compressing that. I think a simpler approach would be to take my Java class and strip out all the command-line stuff it contains, then call that directly from XQuery (see the xqSearchUtils java project and the way it's called from the Despatches XQuery for an example). A jar file with a simple XQuery module interface might be very handy indeed.&lt;/p&gt;</description>
			    <link>http://hcmc.uvic.ca/blogs/index.php?blog=41&amp;title=implemented_a_crude_similarity_metric_in&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
			  </item>
			  	</channel>
</rss>
