<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/30/13 4:57 PM, Paul Johnson
wrote:<br>
</div>
<blockquote
cite="mid:CAMPM96piKG5uoA-0h6NCVjaPwqZUhWdhurX5OCeDGP-+jGUTfA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Nov 30, 2013 at 12:57 PM,
James Mast <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rickmastfan67@hotmail.com" target="_blank">rickmastfan67@hotmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">Peter, it would just be for
the relations. It would stay the current status-quo for
the ways using at all times the "ref & unsigned_ref"
tags (see I-394 example below).</blockquote>
</div>
<br>
I can't wait until we can finally kill this dinosaur. Refs,
as they're presently tagged on ways, almost always apply to
the route instead of the way. And not to mention they're just
a pain in the butt to maintain properly where multiplexes
exist, something that works cleanly in relations.</div>
</div>
<br>
</blockquote>
we're kind of stuck with ref on the ways until the data<br>
and data consumers come up to speed. there are a lot<br>
of route relations still to be built in the US.<br>
<br>
richard<br>
<br>
<br>
</body>
</html>