#149 introduce locusGrp and change msItem definition accordingly

AMBER
closed
nobody
5
2009-02-01
2008-11-08
No

In order to be allowed to supply more than one range of locus information in the beginning of a msItem we would like to see a <locusGrp> element which would contain more than one locus element.

Example:
Bl. 13--26, 37--58, 82--96 Stücke von Daniel Ecklin’s Reise ins h. Land; [...]

would result in
<msItem>
<locusGrp>
<locus>Bl. 13--26</locus>
<locus>37--58</locus>
<locus>82--96</locus>
</locusGrp>
<note>Stücke von Daniel Ecklin’s Reise ins h. Land<note>
</msItem>

Accordingly, the definition of msItem has to be changed:

(
(locusGrp | locus)?,
(
model.pLike+
| ( model.titlepagePart | model.msItemPart | model.global )+
)
)

Note: locusGrp might be useful in other places like decoNote but probably not everywhere.

Discussion

  • Lou Burnard

    Lou Burnard - 2008-11-08

    The @target attribute allows you to specify each folio individually (<locus target="#f1 #f2 #f5"/> for example)
    If this proposal is accepted, it would seem to overlap with the existing facility. Should the @target attribute therefore be removed (or made into a single pointer?)

     
  • James Cummings

    James Cummings - 2008-11-10

    I think Lou is misunderstanding the intent here. @target "supplies a link to one or more transcriptions of the specified range of folios." What people want to do is record in a structured way that this one msItem goes from folios 13-26 and 37-58 and 82-92. They may _not_ have a transcription to point to. This is metadata descriptions not editions of transcriptions.

    I would strongly oppose any removal of @target since the two functions (pointing to transcriptions and recording the locations are different things). @from and @to cannot be used in this manner because they are (properly in my mind) defined as data.word and so don't allow whitespace.

    -James

     
  • Lou Burnard

    Lou Burnard - 2009-01-14
    • milestone: --> 871208
     
  • Peter Boot

    Peter Boot - 2009-01-14

    The definition of locus says ‘usually as a (possibly discontinuous) sequence of folio references.’ The text of the Guidelines repeats this: ‘Locations are conventionally specified as a sequence of folio or page numbers, but may also be a discontinuous list, or a combination of the two.’

    The example that Thorsten gives ‘Bl. 13--26, 37--58, 82--96’ could therefore be encoded as <locus> Bl. 13--26, 37--58, 82—96</locus>

    So why do we need a locusGrp? Will we then also recommend not to use discontinuous loci? Will we provide guidance on when to use one locus, when multiple?

    I’m not against introducing the element but I would like to see a proposed text of the Guidelines before assenting to this one.

     
  • Torsten Schassan

    Dear Peter, within one <locus> there is exactely one possibility to express a sequence with @from and @to. How would you deal with this, other than with more than one <locus>?

    Speaking of the guidelines the locus element may be defined as "a sequence of folio references" and in case of "discontinuity" of such a sequence the use of locusGrp should be recommended.

     
  • Lou Burnard

    Lou Burnard - 2009-01-15
    • milestone: 871208 --> AMBER
     
  • Peter Boot

    Peter Boot - 2009-01-15

    Thorsten, your answer provides what I was asking for: the reason why you need locusGrp. The Guidelines could then say that in case of discontinuity, if you want to formally indicate beginning and endpoints using @from and @to, you should use locusGrp; if not, you can just use locus.

     
  • Lou Burnard

    Lou Burnard - 2009-01-24

    Presumably the <locusGrp> element should be repeatable? and it should have a @scheme attribut which its child <locus> elements will all inherit? Then you can have a discontinuous sequences of pages with two different foliations:
    <locusGrp scheme="#a">
    <locus from="f1" to "f4"/>
    <locus from="f8" to "f9"/>
    </locusGrp>
    <locusGrp scheme="#b">
    <locus from="p3" to "p5"/>
    <locus from="p44" to "p48"/>
    </locusGrp>

     
  • Arianna Ciula

    Arianna Ciula - 2009-01-28

    To be honest, after Torsten's clarification, it seems clear why we need a <locusGrp>. So I would be in favour of this.

     
  • Arianna Ciula

    Arianna Ciula - 2009-01-28

    I think it would be a good thing to have <locusGrp> not only for expressing one case of grouping discontinuous ranges, but also, eventually, to group various loci in different ways according to the scope of the analysis.

    The example in the guidelines about foliation may be one case:
    <locusGrp target="#item1">
    <locus scheme="#original">XCIII</locus>
    <locus scheme="#modern">135</locus>
    </locusGrp>

    So what I am saying is that may be it will be too limiting to allow the use of <locusGrp> ONLY for discontinuous ranges.

    Torsten suggests it may also be useful within <decoNote> and I would say, what about <handNote> too then?

    See for instance the example at http://www.diamm.ac.uk/jsp/Source.jsp?navToggle=1&sourceKey=805

    The fourth paragraph contains some notes on a specific scribe who contributed to other manuscripts too.

    This is just to say that I am in favour of this new element, but may be we need to think more of where else it would be useful and what attributes to supply it with.

     
  • Lou Burnard

    Lou Burnard - 2009-02-01

    Implemented at release 1.3.0 (svn revision 5596)

     
  • Lou Burnard

    Lou Burnard - 2009-02-01
    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks