<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yeah, in the CSV source data I'm just taking as input string values for
any of<br>
<br>
Site, Building, Floor, Room<br>
and if they all exist you end up with room is within floor &
Building, floor is within building, building is within site. And the
URIs are, from the base namespace defined in the config file for each
thing<br>
<br>
$site_ns$site_id<br>
$building_ns$building_id<br>
$floor_ns$building_id-$floor_id<br>
$room_ns$building_id-$room_id<br>
<br>
I am assuming that buildings have unque IDs even over multiple sites,
but that floor & room ID are only unique to the building.<br>
<br>
<br>
Ian Stuart wrote:
<blockquote cite="mid:4E53A430.3090608@ed.ac.uk" type="cite">
<pre wrap="">On 23/08/11 13:39, Nick Gibbins wrote:
</pre>
<blockquote type="cite">
<pre wrap="">That's local usage, certainly - I was suggesting a case at another
institution where the room number to level number mapping isn't as
obvious.
</pre>
</blockquote>
<pre wrap=""><!---->
Room number, really, is just a local code.
Heck - you can't even assume that "1xxx" is ground floor (US version) or
first floor (UK version: the Edinburgh City Chambers (primary offices
for the local council) number from the lowest floor with an outside
window... which means that floor 1 looks out over Cockburn Street, and
the main entrance (off the Royal Mile, or High Street) is on level 5!
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Christopher Gutteridge -- <a class="moz-txt-link-freetext" href="http://id.ecs.soton.ac.uk/person/1248">http://id.ecs.soton.ac.uk/person/1248</a>
You should read the ECS Web Team blog: <a class="moz-txt-link-freetext" href="http://blogs.ecs.soton.ac.uk/webteam/">http://blogs.ecs.soton.ac.uk/webteam/</a>
</pre>
</body>
</html>