• To: "'Peter Hunsberger'" <peter.hunsberger@g...>,"'Costello, Roger L.'" <costello@m...>
• Subject: RE: Best Practice for URI construction?
• From: "Michael Kay" <mike@s...>
• Date: Mon, 12 Dec 2005 17:18:10 -0000
• Cc: "'XML Developers List'" <xml-dev@l...>
• In-reply-to: <cc159a4a0512120731i45af5891o89f31168501011ef@m...>
• Thread-index: AcX/Mkt/DegMDAqqQnyTJa97myHSZAADTvnw

> 
>    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.

Michael Kay
http://www.saxonica.com/

• References:
  • 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: XML and email
• Previous by thread: Re: Best Practice for URI construction?
• Next by thread: Re: Best Practice for URI construction?
• Index(es):
  • Date
  • Thread