[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xml-dev] Best Practice for URI construction?
- To: Michael Kay <mike@...>
- Subject: Re: [xml-dev] Best Practice for URI construction?
- From: Peter Hunsberger <peter.hunsberger@...>
- Date: Mon, 12 Dec 2005 14:36:40 -0600
- Cc: "Costello, Roger L." <costello@...>, XML Developers List <xml-dev@...>
- 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=lDNixwNmY5vKnC8SmM2xVCnC2eu4SISOi5aPOFfgHifCDY9SkMxaLe5Mz+B94wyH+52+kzIPhxsYKTUsF0x1Upih52wAwGFRan5+FPN/lA9EzHrIlZB9iy8xeH6Lq1HoGSzbycgDc1xne9jNqasbD0v5yp9+VMckMuH3LXVLaGo=
- In-reply-to: <439db0dc.12e573d2.62a3.079fSMTPIN_ADDED@...>
- References: <cc159a4a0512120731i45af5891o89f31168501011ef@...> <439db0dc.12e573d2.62a3.079fSMTPIN_ADDED@...>
On 12/12/05, Michael Kay <mike@...> 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 was giving examples of possible results, for any given
implementation it's should never be ambiguous. Eg; without the query
parameters it identifies the search screen (perhaps). With the query
parameters it identifies a single patient (assuming one exists for the
given parameters). An alternate implementation might be that without
query parameters the results is a list.
Or where you worried about something else?
--
Peter Hunsberger
|
