Ok-I’ve read and digested Jon’s reply. I think that their support for Dublic Core metadata offers an interesting possibility. I note that the guidance for web publishers page at hypothesis suggests that “Publishing metadata about your content is a useful thing to do. We encourage you to publish what makes sense in your context, and to let us know if there are types of metadata that would like us to support.” It sounds like we might propose that they add support for our proposed isBasedOn property so that the various URLs can be associated with a Uniform Resource Name? In the case of pure cloning (not the production of derivative texts), what would be the downside of adding a
<meta name=”dc.identifier” content=”foo″><meta name=”dc.relation.ispartof” content=”foo”>
to the head of the texts on our dev site before cloning them to production, @ned? Could this get us where we need to go in the short term?