Subject: Re: [jats-list] Request to identify each <sec> in an article by a unique DOI From: "Good, Linda linda.good@xxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Thu, 17 Jul 2014 21:31:45 -0000 |
Hi Vincent, Thanks for this suggestion. I think I will. I appreciate everyone's comments to help me think through the possibilities. Also, an intelligent voice raising the same WHY questions I had. It sounds like I wasn't overlooking the obvious solution in the first place:). Lin Linda J. Good Phone: 717-285-6815 Cell: 717-475-5379 Email Address: Linda.Good@xxxxxxxxxx<mailto:Linda.Good@xxxxxxxxxx> From: Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx [mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Thursday, July 17, 2014 10:08 AM To: Good, Linda; jats-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [jats-list] Request to identify each <sec> in an article by a unique DOI Lin, This might be a use case for extending sec-meta to include object-id. For example: <sec> <sec-meta> <object-id pub-id-type="doi">10.0000/acro.4627-13.2014.d</object-id> </sec-meta> ... I would suggest submitting this change to the public comments board, if you're so inclined. Here is the link: http://www.niso.org/apps/group_public/document.php?document_id=10591 The id attribute has restrictions that are intrinsic to the way id attributes are defined in XML, so a different DTD version will still fail validation on this example. The value of an id attribute has to follow the pattern defined in the XML Recommendation, which basically is a letter followed by a series of letters and/or numbers. It's safest to avoid using id attributes as a place to store any user-provided data. Vincent From: Good, Linda [mailto:Linda.Good@xxxxxxxxxx] Sent: Wednesday, July 16, 2014 2:55 PM To: jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: RE: [jats-list] Request to identify each <sec> in an article by a unique DOI Hi Tommie, I was getting this XML error, I think due to the slash and the colon in the value when I tried something like that. When I removed those 2 characters, it validates clean. I haven't tried validating it yet against 1.1d1 journal-publishing. Is it possible it will be valid in that version of the DTD? Error: Warning: on line 216 column 45 of file:/content/enu/default/enu2541.xml: Error reported by XML parser: Attribute value "doi:10.0000/acro.4627-13.2014.d" of type ID must be an NCName when namespaces are enabled. Lin Linda J. Good Phone: 717-285-6815 Cell: 717-475-5379 Email Address: Linda.Good@xxxxxxxxxx<mailto:Linda.Good@xxxxxxxxxx> From: Tommie Usdin btusdin@xxxxxxxxxxxxxxxx<mailto:btusdin@xxxxxxxxxxxxxxxx> [mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 16, 2014 2:39 PM To: jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [jats-list] Request to identify each <sec> in an article by a unique DOI I would put that in the @id attribute on the <sec>. For example: <article dtd-version="1.1d1"> <front> <journal-meta>...</journal-meta> <article-meta> <article-id pub-id-type="doi">10.????/_____</article-id> <sec id="doi:10.????/_____.a> ... </sec> <sec id="doi:10.????/_____.b> ... <sec id="doi:10.????/_____.b2> ... </sec> </sec> </article> (You need the "doi:" on the ids for 2 reasons: they make the type of ID clear and since these are XML IDs they must start with an alpha character.) I am sure there are other ways to do this, but this is the one that came to my mind. - Tommie On Jul 16, 2014, at 2:01 PM, Good, Linda linda.good@xxxxxxxxxx<mailto:linda.good@xxxxxxxxxx> <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list-service@xxxxxxxxxx errytech.com>> wrote: Hello, We've had a customer request to add unique DOI numbers for each <sec> of an article, e.g. if primary DOI is: 10.????/_______, then each sub-item would have 10.????/_____.a, 10.????/_____.b, etc. Is there a preferred method of including this type of functionality in the JATS dtd structure? Thank you in advance for any advice. Lin <image001.jpg><http://www.cenveopublisherservices.com/> Linda J. Good XML Dev. Team Leader / Sr. Content Architect Cenveo Publisher Services 3575 Hempland Rd., Lancaster PA 17601 t. 1.717.285.6815 | e. Linda.Good@xxxxxxxxxx<mailto:Linda.Good@xxxxxxxxxx> c. 1.717.471.6406 w. www.cenveopublisherservices.com<http://www.cenveopublisherservices.com/> Innovate. Automate. Collaborate. <image002.png><http://www.linkedin.com/company/12745?trk=tyah&trkInfo=tas:cen veo%20publisher> <image003.png><https://twitter.com/CenveoPublisher> **** JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/> EasyUnsubscribe<-list/1840> (by email) ====================================================================== B. Tommie Usdin mailto:btusdin@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Phone: 301/315-9631 Suite 207 Direct Line: 301/315-9634 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in XML and SGML ====================================================================== **** JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/> EasyUnsubscribe<-list/249904> (by email) **** **** JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/> EasyUnsubscribe<-list/249904> (by email<>) ****
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] Request to identify, Lizzi, Vincent vince | Thread | Re: [jats-list] Request to identify, Alexander Schwarzman |
Re: [jats-list] Request to identify, Evan Owens eowens@xx | Date | [jats-list] BITS: contrib-group in , Mary McRae mary@xxxx |
Month |