RainOfSteel
SOC-14 1K
So it was. Whereas my comments was about the OTU. So I made a comparison between the two.Originally posted by rancke:
</font><blockquote>quote:</font><hr />Originally posted by RainOfSteel:
I didn't mean by warfare, I meant by politics. They'd go through their superiors for "decisions" of area-assignment. Long-term pressure would work wonders over the centuries.
In any event, that portion was clearly prefixed IMTU.
Come to that, the objections you bring up aren't problems in your TU, are they? In YTU Lanth is a county, and if you decided to 'open that can of worms', you'd be the one who gets to decide which counties are odd and which aren't. So why bring it up unless you thought your objections are valid in connection with the OTU?
Hans </font>[/QUOTE]Well, rather than argue about clarity, how about turning the discussion around onto a couple of new questions?
How do we express such trans-subsector associations on a UWP line?
How would we display them on a map?
Personally, I always thought there should be both a subsector location column and a "managing subsector" column. In most cases, they'd contain the same data, but when they didn't, it would indicate the Jewell subsector situation, where Jewell Imperial worlds would show Regina as the "managing subsector". The trouble with this is, that in a tradition UWP, the subsector's name is a Header Line, and it doesn't take up any space on the UWP line itself. If individual worlds in a subsector can be managed by different adjacent subsectors, this means we'd have to cram space for an entire length subsector name onto the UWP, disrupting its compact nature. Hmmm, it bears thinking on.
This leaves open how it would be displayed successfully on a map.