[Xml-sg-cmt] XML citation library - bibxml7: non-ASCII found in XML elements that should not contain it (Issue #261)

Sandy Ginoza <sginoza@amsl.com> Wed, 10 August 2022 18:43 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <57596c04-18d8-1628-0967-96db9f3e32bb@amsl.com>
Date: Wed, 10 Aug 2022 11:43:22 -0700
Cc: Jean Mahoney <jmahoney@amsl.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <46931C92-61FD-4F1A-A899-F30F3342EE75@amsl.com>
References: <ietf-tools/bibxml-service/issues/261/1210634090@github.com> <57596c04-18d8-1628-0967-96db9f3e32bb@amsl.com>
To: "xml-sg-cmt@ietf.org" <xml-sg-cmt@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/5oi27-ORMjU4NXSTyTWmwtLFTno>
Subject: [Xml-sg-cmt] XML citation library - bibxml7: non-ASCII found in XML elements that should not contain it (Issue #261)
Precedence: list

Hi CMT,

We previously talked about possibly a) allowing non-ASCII everywhere and b) normalizing the XML.  Based on our discussion yesterday, I believe these items may eventually be handled by the RSWG.  In the meantime, we intend to request that bib.ietf.org use ASCII equivalents in <refcontent>.  We believe this mostly impacts punctuation (e.g., em dash, smart quotes) at this time, so as Jean notes below, using ASCII equivalents would be consistent with current practice.  

Thanks,
Sandy 

> On Aug 10, 2022, at 6:38 AM, Jean Mahoney <jmahoney@amsl.com> wrote:
> 
> Hi Sandy,
> 
> Please see below. The developers are suggesting either using <u> elements or replacing unicode with ASCII equivalents to handle non-ASCII in reference elements that can't contain it (like <refcontent>). I lean toward using ASCII equivalents because that's what we've been doing internally, but let me know what you think.
> 
> Thanks!
> Jean
> 
> 
> -------- Forwarded Message --------
> Subject:	Re: [ietf-tools/bibxml-service] bibxml7: non-ASCII found in XML elements that should not contain it (Issue #261)
> Date:	Wed, 10 Aug 2022 05:54:26 -0700
> From:	Ronald Tse <notifications@github.com>
> Reply-To:	ietf-tools/bibxml-service <reply+ACENAES2O64SVD7FLBQVIV6BADOQFEVBNHHE66NMB4@reply.github.com>
> To:	ietf-tools/bibxml-service <bibxml-service@noreply.github.com>
> CC:	Jean Mahoney <jmahoney@amsl.com>, Mention <mention@noreply.github.com>
> 
> 
> Thank you @ajeanmahoney for raising this.
> 
> DOI CrossRef data allows Unicode, so in order to achieve the strict subset of XML elements, the BibXML Service will be required to "normalize" or "strip" non-compliant characters.
> 
> According to your link, these elements can contain Unicode directly:
> 
> 	• <author>, <contact>, <organization>, <street>, <city>, <region>, <city>, <country> and <email>
> However, <refcontent> does not support Unicode.
> 
> There are two ways to handle this.
> 
> @ajeanmahoney any thoughts?
> 
> Wrapping with <u> element
> 
> According to the link:
> 
> Other than in the resricted elements, non-ASCII characters must be wrapped by the <u> element with the format attribute specifying how it is represented.
> 
> Sanitization of symbols
> 
> We could implement a sanitization mapping for converting Unicode characters to their equivalents in ASCII, e.g. :
> 
> "—": "-"
> "’": "'"
> 
> ...
> 
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you were mentioned.
>

[Xml-sg-cmt] XML citation library - bibxml7: non-… Sandy Ginoza
Re: [Xml-sg-cmt] XML citation library - bibxml7: … Robert Sparks
Re: [Xml-sg-cmt] XML citation library - bibxml7: … Sandy Ginoza