@jroesch and I were talking about this a little. We were thinking of subclassing Span. You’d have SourceSpan which comes from files and then ModelSpan (probably could use a better name) for handling layers/nodes in models. This gets around the issue of having meaningless line fields for spans from models.