Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interpolations in “Wandering Rocks” #23

Open
yellwork opened this issue Feb 23, 2017 · 1 comment
Open

Interpolations in “Wandering Rocks” #23

yellwork opened this issue Feb 23, 2017 · 1 comment

Comments

@yellwork
Copy link
Collaborator

@yellwork asks:

Would we be able to use <div> (or something else) to thread the various interpolations back to their “parent” <div>, where appropriate? I like the idea of making explicit in the markup some of the internal connections and reiterations of the book.

@c-forster responds:

I think marking this up would be a good idea--but I think it would require a different strategy. The divs are not granular enough (you want to be able to the interpolated/reiterated text, not just the section from which it came, right? Would something like this work, using and refs?

<lb n="100201"/>raised his cap abruptly: <span xml:id="l100201">the young woman 
abruptly bent and with slow care
<lb n="100202"/>detached from her light skirt a clinging twig.</span>

And, later in the same file:

<p><lb n="100440"/><ref target="#l100201">The young woman with slow care detached from
 her light skirt a 
<lb n="100441"/>clinging twig.</ref>

There is, in "Wandering Rocks" a clear "original," and "reference" structure I think. It would be nice if were bidirectional (that the source pointed to where it was later interpolated), but off the top of my head I can't think of an obvious and semantic way of doing it. (Simply adding more ptrs/links--as folks do when they make HTML footnotes, with links back to the text seems wrong here.) I'd like to hear others thoughts on the best approach, but once there is consensus I'm happy to hop in and add the appropriate markup. (Note also, I've just created a rather weak id for the source span using the line number... I don't think that's a very good idea.)

@yellwork
Copy link
Collaborator Author

What about using a combination of <seg> and <span>?

The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing.
<span> associates an interpretative annotation directly with a span of text.

For example:

<lb n="100314"/><said who="Blazes Boylan">―Can you send them by tram? Now?</said></p>
<p><seg xml:id="100315"><lb n="100315"/>A darkbacked figure under Merchants' arch scanned books on the
<lb n="100316"/>hawker's cart.</seg>
<lb n="100317"/><said who="Thornton's girl">―Certainly, sir. Is it in the city?</said>
<p><lb n="100520"/>They went up the steps and under Merchants' arch. <seg xml:id="100520">A darkbacked
<lb n="100521"/>figure scanned books on the hawker's cart.</seg>
<lb n="100522"/><said who="Lenehan">―There he is,</said> Lenehan said.

And then elsewhere in the XML file:

<spanGrp type="interpolations">
     <spanGrp n="*">
           <span from="#100315">reiteration</span>
           <span from="#100520">original</span>
     </spanGrp>
     <spanGrp n="*+1">
           <!---->
     </spanGrp>
     <!---->
</spanGrp>

Would we want to include the @n values from the surrounding <div type="section" n="*"> nesting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant