[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Best Practice for URI construction?
On 12/12/05, Michael Kay <mike@s...> 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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|