Subject: RE: [jats-list] how to describe <collab> in multiple languages From: "Kelly, Laura (NIH/NLM/NCBI) [E]" <kelly@xxxxxxxxxxxxxxxx> Date: Tue, 5 Jul 2011 07:50:52 -0400 |
I think mixing collab and name would open the door to tagging that's impossible to decipher. What do you do if you see this: <name-alternatives> <name>...</name> <name>...</name> <collab>...</collab> </name-alternatives> <name>...</name> <name>...</name> <collab>...</collab> How can a collab be an alternative of a name? Yet if we allow it, we're going to see it tagged. Even if we restrict the usage as in Debbie's 2nd model, we're still wrapping collab inside an element called name-alternatives...saying collabs are names, which they're not. We have separate models for them for a reason and I believe we need to keep them separate. I agree with Chris on this one. I think we need collab-alternatives. If I'm trying to parse and index the data, I know I'd much rather see this: <name-alternatives> <name>...</name> <name>...</name> </name-alternatives> <collab-alternatives> <collab>...</collab> <collab>...</collab> </collab-alternatives> <name-alternatives> <name>...</name> <name>...</name> </name-alternatives> lk ________________________ Laura Kelly kelly@xxxxxxxxxxxxxxxx NCBI/NLM/NIH -----Original Message----- From: Bruce Rosenblum [mailto:bruce@xxxxxxxxx] Sent: Monday, July 04, 2011 10:19 PM To: jats-list@xxxxxxxxxxxxxxxxxxxxxx; jats-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [jats-list] how to describe <collab> in multiple languages This is a great question from Soichi, and thanks for the proposed models, Debbie. My instinct is to recommend your first version name-alternatives (collab | name | string-name)+ because there are cases of articles where the author list includes authors, then one or more collabs, and then more authors, and the order is important. Your first version supports this, but not the second, and possibly not the third (depends on how the surrounding model is built) Bruce At 08:09 PM 7/4/2011, Debbie Lapeyre wrote: >Dear All-- > >>Can <name-alternatives> be changed to contain <collab> in it? > >This is an interesting request. I can understand wanting a <collab> >in multiple languages or multiple scripts, but I am a little >uncertain that just adding <collab> is the way to go: > >Can a <name> or a <string-name> ever be an alternative for >a <collab>? Or, if you used multiple collaborations would it always >be with other <collab>s? > >So I ask the group: > > - Would it be better to just allow any mix (these are NOT > enforcing Tag Sets after all): > > name-alternatives (collab | name | string-name)+ > > - Or to try to restrict the usage: > > name-alternatives (collab+ | (name | string-name)+ ) > > - Or to give <collab> its own alternatives: > > collab-alternatives (collab+) > > - Or something else entirely? > >What say you all? > >--Debbie > >-- >====================================================================== >Deborah Aleyne Lapeyre mailto:dalapeyre@xxxxxxxxxxxxxxxx >Mulberry Technologies, Inc. http://www.mulberrytech.com >17 West Jefferson Street Direct Phone: 301/315-9633 >Suite 207 Phone: 301/315-9631 >Rockville, MD 20850 Fax: 301/315-8285 >---------------------------------------------------------------------- >Mulberry Technologies: A Consultancy Specializing in XML, XSLT, & SGML >====================================================================== ------------------------------------------------------------------- Bruce D. Rosenblum Inera Inc. 19 Flett Road Belmont, MA 02478 617-932-1932 (office) bruce@xxxxxxxxx
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] how to describe <co, Bruce Rosenblum | Thread | RE: [jats-list] how to describe <co, Maloney, Christopher |
RE: [jats-list] how to describe <co, Kelly, Laura (NIH/NL | Date | Re: [jats-list] how to describe <co, Soichi Kubota |
Month |