• To: "'XML Developers List'" <xml-dev@l...>
• Subject: Re: Best Practice for URI construction?
• From: Frank Richards <frank@t...>
• Date: Mon, 12 Dec 2005 15:29:12 -0500
• In-reply-to: <20051212183330.7894C8B501@b...>
• References: <20051212183330.7894C8B501@b...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

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.

Frank

• Follow-Ups:
  • Re: Best Practice for URI construction?
    • From: Peter Hunsberger <peter.hunsberger@g...>

• Prev by Date: RE: Best Practice for URI construction?
• Next by Date: Re: Best Practice for URI construction?
• Previous by thread: RE: Best Practice for URI construction?
• Next by thread: Re: Best Practice for URI construction?
• Index(es):
  • Date
  • Thread