[
Lists Home |
Date Index |
Thread Index
]
- To: Frank Richards <frank@therichards.org>
- Subject: Re: [xml-dev] Best Practice for URI construction?
- From: Peter Hunsberger <peter.hunsberger@gmail.com>
- Date: Mon, 12 Dec 2005 15:04:21 -0600
- Cc: XML Developers List <xml-dev@lists.xml.org>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qqZhUSEJ81aLU6T3P0qWYFv9sib/RG0VVcdiO3S45wXry7gdNFx5jyCfqBgdvSFSWjAaDPuuZT95ZHkp5I1yHoiaxsFdnCNe0yNdQZeuPno+luy1/K6Yn9N815+RRRmLIzC93yjiS92+Aami0ypc4Auyn3t+Op64XiiU/ISXreQ=
- In-reply-to: <439DDD98.2080604@therichards.org>
- References: <20051212183330.7894C8B501@bunter.therichards.org> <439DDD98.2080604@therichards.org>
On 12/12/05, Frank Richards <frank@therichards.org> wrote:
> Michael Kay wrote:
>
> >> org/stjude/cris/totxv/patient
> >>
> >>might identify the class of patients enrolled on the TOTXV protocol
> >>here at St. Jude. Whether this in itself returns something useful is
> >>up to the implementer. In our case, if no specific instance is
> >>identifiable, we might default to bringing up a search screen (or a
> >>list) allowing one to find (or pick) an instance.
> >>
> >>
> >
> >Either it identifies a class of patients or it identifies a search screen.
> >If it identifies both then it's ambiguous, which we surely can't tolerate.
> >
> >I get the feeling this whole edifice is built on sand.
> >
> >
> I read the statement as saying that the search screen is an error
> response if an appropriate patient list isn't found. Actually that
> sounds like good design to me.
Yes. To be explicit: most of the time we will choose to implement a
search screen for the case where no query parameters are supplied.
This screen will also be returned if the query parameters result in an
error (with an appropriate error message attached).
--
Peter Hunsberger
|
