Subject: RE: [jats-list] how to describe <collab> in multiple languages From: "Maloney, Christopher (NIH/NLM/NCBI) [C]" <maloneyc@xxxxxxxxxxxxxxxx> Date: Mon, 4 Jul 2011 23:46:57 -0400 |
Hi, > (these are NOT enforcing Tag Sets after all) What does this mean? I like your third alternative: > Or to give <collab> its own alternatives: > collab-alternatives (collab+) <name-alternatives> has the same semantics as <name>. It can be used anywhere a <name> can be used, and means the same thing as a <name>. That is, when you encounter a <name-alternatives>, you know you're going to get a list of alternatives of a person's name. <collab> is something completely different. So if you allow <collab> inside <name-alternatives>, it would conflate the semantics of <name-alternatives>, and make downstream processing much harder, I would think. This seems to me to be one instance of a general problem, since many of these metadata items could potentially have multiple renderings in various languages and scripts. To keep the schema as clean and useful as possible, I would think it would be best to provide a mechanism in each case that has the exact same semantics as the original element. The proliferation of element names could get unwieldy, though. What about, for example, <publisher-name>, <publisher-loc>, etc.? I wonder how the other big publishing schema systems address this question. Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 5AN.24D-22 301-594-2842 -----Original Message----- From: Debbie Lapeyre [mailto:dalapeyre@xxxxxxxxxxxxxxxx] Sent: Monday, July 04, 2011 8:09 PM To: jats-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [jats-list] how to describe <collab> in multiple languages 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 ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [jats-list] how to describe <co, Kelly, Laura (NIH/NL | Thread | RE: [jats-list] how to describe <co, Kelly, Laura (NIH/NL |
Re: [jats-list] how to describe <co, Bruce Rosenblum | Date | RE: [jats-list] how to describe <co, Kelly, Laura (NIH/NL |
Month |