RetroBBS - comp.protocols.dicom - Re: Ambiguity in Standard on first Coded Entry TID-4003

Re: Ambiguity in Standard on first Coded Entry TID-4003

<b022ab12-57fa-46aa-ae21-e7dfc69c6bdcn@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=260&group=comp.protocols.dicom#260

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:620a:4107:: with SMTP id j7mr30617030qko.645.1639353877162;
Sun, 12 Dec 2021 16:04:37 -0800 (PST)
X-Received: by 2002:a05:622a:1a14:: with SMTP id f20mr41598815qtb.294.1639353877006;
Sun, 12 Dec 2021 16:04:37 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Sun, 12 Dec 2021 16:04:36 -0800 (PST)
In-Reply-To: <cd846e37-7d4a-4c5c-a454-102102caf5b6n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=50.32.223.118; posting-account=rKkGZwkAAADOuxQ23uuHnmKt95j-5iL6
NNTP-Posting-Host: 50.32.223.118
References: <cd846e37-7d4a-4c5c-a454-102102caf5b6n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b022ab12-57fa-46aa-ae21-e7dfc69c6bdcn@googlegroups.com>
Subject: Re: Ambiguity in Standard on first Coded Entry TID-4003
From: dclunie@dclunie.com (David Clunie)
Injection-Date: Mon, 13 Dec 2021 00:04:37 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 8

by: David Clunie - Mon, 13 Dec 2021 00:04 UTC

The preferred code meaning would be without the space, i.e., "Individual Impression/Recommendation".

I will fix the standard so that a zero-width space is used consistently in all uses of DCM:111034, which will allow the columns to break after the slash when rendered and not be forced to be excessively wide (which was presumably why I put in the spurious space in TID 4003). The release notes describe that zero-width spaces may be encountered in the DocBook XML source and are intended to be filtered out before use.

Re: Ambiguity in Standard on first Coded Entry TID-4003

<c67e580b-128c-4dac-8a77-ec545dfde2f4n@googlegroups.com>

copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=261&group=comp.protocols.dicom#261

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:622a:4ce:: with SMTP id q14mr9187522qtx.627.1639381585326;
Sun, 12 Dec 2021 23:46:25 -0800 (PST)
X-Received: by 2002:a05:622a:1a1c:: with SMTP id f28mr42775591qtb.308.1639381585119;
Sun, 12 Dec 2021 23:46:25 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Sun, 12 Dec 2021 23:46:24 -0800 (PST)
In-Reply-To: <b022ab12-57fa-46aa-ae21-e7dfc69c6bdcn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=91.173.12.104; posting-account=5syELgoAAABMLWsjbxhk8Wo7CLxGgTPG
NNTP-Posting-Host: 91.173.12.104
References: <cd846e37-7d4a-4c5c-a454-102102caf5b6n@googlegroups.com> <b022ab12-57fa-46aa-ae21-e7dfc69c6bdcn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c67e580b-128c-4dac-8a77-ec545dfde2f4n@googlegroups.com>
Subject: Re: Ambiguity in Standard on first Coded Entry TID-4003
From: mathieu.malaterre@gmail.com (Mathieu Malaterre)
Injection-Date: Mon, 13 Dec 2021 07:46:25 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 20

by: Mathieu Malaterre - Mon, 13 Dec 2021 07:46 UTC

On Monday, December 13, 2021 at 1:04:38 AM UTC+1, dcl...@dclunie.com wrote:
> The preferred code meaning would be without the space, i.e., "Individual Impression/Recommendation".
>
> I will fix the standard so that a zero-width space is used consistently in all uses of DCM:111034, which will allow the columns to break after the slash when rendered and not be forced to be excessively wide (which was presumably why I put in the spurious space in TID 4003). The release notes describe that zero-width spaces may be encountered in the DocBook XML source and are intended to be filtered out before use.

IMHO, it would also be nice to remind the audience about usage of zero-width spaces in each resp. `Conventions` section. Eg. part06 does not describes this use of zero-width spaces:

* https://dicom.nema.org/medical/dicom/current/output/chtml/part06/chapter_5.html

Copy/paste error could happen.

2cts

I just thought of something funny...your mother. -- Cheech Marin

devel / comp.protocols.dicom / Re: Ambiguity in Standard on first Coded Entry TID-4003

Subject	Author
Re: Ambiguity in Standard on first Coded Entry TID-4003	David Clunie
Re: Ambiguity in Standard on first Coded Entry TID-4003	Mathieu Malaterre