Message-ID:

The two most common things in the Universe are hydrogen and stupidity. -- Harlan Ellison

devel / comp.protocols.dicom / Re: STOW-RS doesn't allow "Multi-frame pixel data using a single-frame media type (one frame per message part)" in request

Re: STOW-RS doesn't allow "Multi-frame pixel data using a single-frame media type (one frame per message part)" in request

<21c763d3-7aba-45a7-b11f-281209aa555fn@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:620a:16c2:b0:6fc:aae3:664a with SMTP id a2-20020a05620a16c200b006fcaae3664amr2707865qkn.459.1673758354370;
Sat, 14 Jan 2023 20:52:34 -0800 (PST)
X-Received: by 2002:a05:6902:552:b0:7b9:5bf3:67d7 with SMTP id
z18-20020a056902055200b007b95bf367d7mr3019695ybs.16.1673758354140; Sat, 14
Jan 2023 20:52:34 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Sat, 14 Jan 2023 20:52:33 -0800 (PST)
In-Reply-To: <aa605e8f-00fe-47f8-94ae-c66e7a1b606c@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=159.196.12.6; posting-account=y7VL5goAAADh9WQE6khQ1zwKq12X5JXl
NNTP-Posting-Host: 159.196.12.6
References: <4aa41cad-7ee9-43f4-b63c-c6e22b6abfed@googlegroups.com>
<60eea8bc-9882-4c6a-8e79-4b9b431154e3@googlegroups.com> <bb9da38e-b493-4a6f-8404-e3c3645d3c59@googlegroups.com>
<efe11829-432c-4c22-a804-c877ca062b18@googlegroups.com> <a5efdff2-57f4-4dc2-8b75-4b3bffcd6d80@googlegroups.com>
<aa605e8f-00fe-47f8-94ae-c66e7a1b606c@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <21c763d3-7aba-45a7-b11f-281209aa555fn@googlegroups.com>
Subject: Re: STOW-RS doesn't allow "Multi-frame pixel data using a
single-frame media type (one frame per message part)" in request
From: parnesh.raniga@gmail.com (Parnesh Raniga)
Injection-Date: Sun, 15 Jan 2023 04:52:34 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2561

by: Parnesh Raniga - Sun, 15 Jan 2023 04:52 UTC

Sorry to bring up this old thread. On a cursory look, the current specification has changed so that compressed multi-frame data can only be encoded as multiple single frame parts for both WADO and STOW.

What's still unclear / not explicit , at least to me so apologies in advance, is the how the location URI for multi-frame data should be encoded. I assume this is the same as WADO-RS (BulkdataURI/frames/{framenumber}) but it would be better if it was made explicit.

Cheers

On Friday, April 6, 2018 at 8:43:39 AM UTC+10, dcl...@dclunie.com wrote:
> This sounds like a lot more than a CP.
>
> To add new resources and services you need to define the use case, discuss this with WG 27, create a work item proposal and get it approved by the DSC, draft a supplement and volunteer to edit it if you want anything to actually get done.
>
> David
> On Monday, April 2, 2018 at 3:06:47 AM UTC-4, Jouke Numan wrote:
>
> > I'll write a CP for this.

Subject	Author
Re: STOW-RS doesn't allow "Multi-frame pixel data using a	Parnesh Raniga