Re: [jats-list] Request to identify each <sec> in an article

"In fact, DOIs are very lax in what characters they permit"

The original DOI specification allowed almost any
character, and CrossRef originally supported
that. After about 5 years of problems due to DOIs
with characters like <, > and # showing up (the <
and > from the SICI standard were especially
problematic), CrossRef set limits on the
characters they allow to "a-z", "A-Z", "0-9" and
"-._;()/" (note however that DOIs are actually
treated case insensitive according to the ISO standard).

So older CrossRef DOIs can have almost any
character, but newer ones are limited to the
rules above. The ISO standard, however, remains
unchanged and still allows almost any character.

Of course, that doesn't solve the slash problem, short of substitution.

You might suggest (via the NISO form) that the
working group add a DOI attribute to sec, or
better might be an id element in sec-meta

Bruce

At 03:38 PM 7/16/2014, Maloney, Christopher
(NIH/NLM/NCBI) [C] maloneyc@xxxxxxxxxxxxxx wrote:

In the XML spec, it says that "Values of type ID
must match the Name production."  That means any

NameStartChar (colon, letter, underscore, or
various non-ascii) followed by any number of NameChars

(colon, letter, underscore, various non-ascii, dash, dot, or digit).

So slashes are out.  In fact, DOIs are very lax
in what characters they permit, so I'm not sure

that this is a good solution.  If you control
the DOIs, and the characters that go into them, then

you could just define some substitution scheme for the slashes.

--

Chris Maloney

NIH/NLM/NCBI (Contractor)

Building 45, 4AN36D-12

301-594-2842

"Good, Linda linda.good@xxxxxxxxxx<mailto:linda.good@xxxxxxxxxx>" wrote:

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 havenbt
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=bdoi:10.????/_____.a>

</sec>

<sec id=bdoi:10.????/_____.b>

<sec id=bdoi:10.????/_____.b2>

</sec>

</sec>

</article>
(You need the bdoi:b 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@xxxxxxxxx

berrytech.com>>

wrote:

Hello,
Webve 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:ce

nveo%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/281881>
(by email<>)


-------------------------------------------------------------------
This email message and any attachments are
confidential. If you are not the intended
recipient, please immediately reply to the sender
or call 617-932-1932 and delete the message from your email system. Thank
you.
-------------------------------------------------------------------
Bruce D. Rosenblum
Inera Inc.
19 Flett Road
Belmont, MA 02478
617-932-1932 (office)
bruce@xxxxxxxxx

<- Previous	Index	Next ->
Re: [jats-list] Request to identify, Maloney, Christopher	Thread	[jats-list] return links from citat, Mike Eden meden@xxxx
Re: [jats-list] Request to identify, Maloney, Christopher	Date	Re: [jats-list] Request to identify, Lizzi, Vincent vince
	Month

<-prev [Thread] next->	<-prev [Date] next->
Month Index \| List Home

Re: [jats-list] Request to identify each <sec> in an article by a unique DOI