Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

May the bluebird of happiness twiddle your bits.


devel / comp.protocols.dicom / Selected character set WADO-RS

SubjectAuthor
o Selected character set WADO-RSMathias Kogler

1
Selected character set WADO-RS

<bb5d0f88-5828-4505-9553-2aec916de0c0n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:5f47:: with SMTP id y7mr2701804qta.601.1642060847586;
Thu, 13 Jan 2022 00:00:47 -0800 (PST)
X-Received: by 2002:a05:622a:509:: with SMTP id l9mr867886qtx.453.1642060847144;
Thu, 13 Jan 2022 00:00:47 -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: Thu, 13 Jan 2022 00:00:46 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=62.245.219.245; posting-account=ibAYIwoAAAB1f6JgamLFct5MoAdQJunR
NNTP-Posting-Host: 62.245.219.245
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <bb5d0f88-5828-4505-9553-2aec916de0c0n@googlegroups.com>
Subject: Selected character set WADO-RS
From: mkogler@gmail.com (Mathias Kogler)
Injection-Date: Thu, 13 Jan 2022 08:00:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 47
 by: Mathias Kogler - Thu, 13 Jan 2022 08:00 UTC

Dear DICOM experts,
I am not sure how to interpret the character set specification for WADO-RS in the DICOMweb standard.

In part 18 section 8.8 the standard states:
"A request without any Character Set Query Parameter or Accept-Charset header field implies that the user agent will accept any character set in the response."[https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.8]

In section 8.8.5 the standard states:
"The origin server shall determine the Selected Character Set(s) as follows:

1. Select the first supported character set in the "charset" parameter(s) of the Selected Media Type.
2. Otherwise, select the highest priority supported charset in the character-set Query Parameter.
3. Otherwise, select the highest priority supported charset in the Accept-Charset header field.
4. Otherwise, if the Selected Media Type has a default character set that is supported, select it.
5. Otherwise, select UTF-8."
[https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.8.5]

And in section 8.7.3.5.3 the default character set is defined as UTF-8.
"All DICOM Media Types have a Default Character Set of UTF-8."
[https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.7.3.5.3]

Questions:
1. If no acceptable character set is sent by the client in which character set shall the response be encoded? UTF-8 or any character set they are available?

2. If a "*" wildcard character set is sent by the client in which character set shall the response be encoded? UTF-8 or any character set they are available?
E.g. for the Transfer Syntax this behavior is defined as "The wildcard value "*" indicates that the user agent will accept any Transfer Syntax. This allows, for example, the origin server to respond without needing to transcode an existing representation to a new Transfer Syntax". [https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.7.3.5.2]

Kind regards,
Mathias

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor