I think this proposed change slipped out of the basket before the guillotine
came down....

Not sure what we should do about this: the solution proposed below seems a bit
ad hoc to me so input from other council members would be much appreciated.




n message <C930740D-9AEF-472E-BAA8-49ED99DC8D8A@loria.fr> Laurent Romary
<laurent.romary@loria.fr> writes:
> Hi Lou,
> Did you manage to implement the proposed content model change for  
> relatedItem: it do not see this in the schemas I get from Roma?
> Best wishes,
> Laurent
> 
> Le 23 oct. 07 à 16:13, Lou Burnard a écrit :
> 
> >
> > This didnt get discussed during our call today, but should have been:
> >
> >>> 1. Use of relatedItem
> >>> By definition relatedItem points to another bibliographical
> >>> description to with the current one may be linked. In particular,
> >>> it can be used to point to a volume from in which a paper has been
> >>> published. Still, it is not possible to add any biblScope
> >>> information in this case (cf. example below). Would it make sense
> >>> to change this?
> >
> > This is the case where we want to say
> >
> > <biblStruct>
> >   <!-- stuff about an article's first appearance -->
> >   <relatedItem>
> >      <!-- link to a journal or somewhere that reprints the article --
> >   </relatedItem>
> > </biblStruct>
> >
> >
> > The problem is that the content model of relatedItem is currently
> >
> > model.biblLike|model.ptrLike
> >
> > so that if you choose to put in a pointer to the journal etc. you  
> > cannot
> > qualify it with a biblScope.
> >
> > The proposed solution is presumably to change the content model to
> >
> > model.biblLike | (model.ptrLike, biblScope?)
> >
> > since biblScope can already appear within members of model.biblLike
> >
> > Anyone disagree with this proposal? I will make the change this  
> > evening
> > otherwise.
> >
> >
> >
> >
> >
> >
> >>>
> >>>             <listBibl>
> >>>                 <biblStruct xml:id="Burnard1999a">
> >>>                     <analytic>
> >>>                         <author>
> >>>                             <forename>Lou</forename>
> >>>                             <surname>Burnard</surname>
> >>>                         </author>
> >>>                         <title level="a">Using SGML for Linguistic
> >>> Analysis: The Case of the
> >>>                         BNC</title>
> >>>                     </analytic>
> >>>                     <monogr>
> >>>                         <title level="j">Markup Languages Theory
> >>> and Practice</title>
> >>>                         <imprint>
> >>>                             <biblScope type="vol">2</biblScope>
> >>>                             <date>1999</date>
> >>>                             <pubPlace>Cambridge, Massachusettes</
> >>> pubPlace>
> >>>                             <publisher>MIT Press</publisher>
> >>>                             <biblScope type="pp">31?51</biblScope>
> >>>                         </imprint>
> >>>                     </monogr>
> >>>                     <idno type="url">http://users.ox.ac.uk/~lou/
> >>> papers/sgml96.sgm</idno>
> >>>                     <relatedItem>
> >>>                         <ref target="Moser2001a">Also published in</
> >>> ref>
> >>>                         <biblScope type="pp">53?72</
> >>> biblScope>       <!-- NOT ALLOWED, but desirable, isn't it? -->
> >>>                     </relatedItem>
> >>>                 </biblStruct>
> >
> >
> >
> >>>                 <biblStruct xml:id="Moser2001a">
> >>>                     <monogr>
> >>>                         <editor>
> >>>                             <forename>Stephan</forename>
> >>>                             <surname>Moser</surname>
> >>>                         </editor>
> >>>                         <editor>
> >>>                             <forename>Peter</forename>
> >>>                             <surname>Stahl</surname>
> >>>                         </editor>
> >>>                         <editor>
> >>>                             <forename>Werner</forename>
> >>>                             <surname>Wegstein</surname>
> >>>                         </editor>
> >>>                         <editor>
> >>>                             <forename>Norbert</forename>
> >>>                             <forename>Richard</forename>
> >>>                             <surname>Wolf</surname>
> >>>                         </editor>
> >>>                         <title level="m">Maschinelle Verarbeitung
> >>> Altdeutscher Texte V (BeitrAdge zum
> >>>                             FA|nften Internationalen Symposion,
> >>> WA|rzburg, 4?6 MAdrz 1997)</title>
> >>>                         <imprint>
> >>>                             <pubPlace>TA|bingen</pubPlace>
> >>>                             <publisher>Niemeyer</publisher>
> >>>                             <date>2001</date>
> >>>                         </imprint>
> >>>                     </monogr>
> >>>                 </biblStruct>
> >>>             </listBibl>
> >>>
> >>> 2. We are missing means to represent all types of affiliation
> >>> information, typically:
> >>>
> >>> 2.a there is neither a "phoneNumber" element nor the possibility to
> >>> type addressLine
> >>> 2.b <email> is not allowed in <address>, nor <affiliation>
> >>>
> >>> See the illustrating example below:
> >>>     <analytic>
> >>>         <author>
> >>>             <forename>Telikepalli</forename>
> >>>             <surname>Kavitha</surname>
> >>>             <affiliation>
> >>>                 <orgName>CSA Department</orgName>
> >>>                 <orgName>Indian Institute of Science</orgName>
> >>>                 <address>
> >>>                     <settlement>Bangalore</settlement>
> >>>                     <postCode>560012</postCode>
> >>>                     <country>India</country>
> >>>                     <addrLine type="phone">+91-80-22932386</ 
> >>> addrLine>
> >>>                     <addrLine type="fax">+91-80-23602911</addrLine>
> >>>                 </address>
> >>>             </affiliation>
> >>>             <email>kavitha@csa.iisc.ernet.in</email>
> >>>         </author>
> >>>   </analytic>
> >>>
> >>>
> >>> 3. It's a pity that we can have <orgName> in affiliation, but not
> >>> <org>, since we may want to add extra information about
> >>> organizations which are not information about the name proper (I
> >>> know Lou will be sensible to this argument). Would we go in this
> >>> direction, it would then be nice to have things like <address> in
> >>> <org>.
> >>> By the way, it seems that <org> and <institution> are highly
> >>> redundant (even if <institution> is limited to manuscripts
> >>> descriptions)
> >>>
> >>> <affiliation>
> >>>     <org type="institution"> <!-- NOT ALLOWED in <affiliation>, but
> >>> desirable, isn't it? -->
> >>>         <orgName>Max-Planck-Gesellschaft</orgName>
> >>>         <address>                   <!-- NOT ALLOWED in <org>, but
> >>> desirable, isn't it? -->
> >>>             <street>Hofgartenstrasse 8</street>
> >>>             <postCode>80539</postCode>
> >>>             <settlement>MA|nchen</settlement>
> >>>             <country>Deutschland</country>
> >>>         </address>
> >>>     </org>
> >>>     <org type="institute">
> >>>         <orgName>Max-Planck-Institut fA|r Informatik</orgName>
> >>>         <address>
> >>>             <street>Stuhlsatzenhausweg 85</street>
> >>>             <postCode>66123</postCode>
> >>>             <settlement>SaarbrA|cken</settlement>
> >>>             <country>Deutschland</country>
> >>>         </address>
> >>>     </org>
> >>>     <org type="department">
> >>>         <orgName>Algorithmen und KomplexitAdt</orgName>
> >>>         <address>
> >>>             <street>Stuhlsatzenhausweg 85, GebAdude E1 4</street>
> >>>             <postCode>66123</postCode>
> >>>             <settlement>SaarbrA|cken</settlement>
> >>>             <country>Deutschland</country>
> >>>         </address>
> >>>     </org>
> >>>
> >>> Too dreadful a practice for this open air.
> >>>
> >>
> >>
> >> --------------------------------------------------------------------- 
> >> ---
> >>
> >> _______________________________________________
> >> tei-council mailing list
> >> tei-council@lists.village.Virginia.EDU
> >> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> >
> > _______________________________________________
> > tei-council mailing list
> > tei-council@lists.village.Virginia.EDU
> > http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>