Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Actually, I am somewhat interested in where they came from. In our library > of medical records, we have annotations on sentences attesting to codes that > are justified by that sentence. I would want to identify the source of the > code [one of several software modules, human review, et cetera]. That's > actually not terribly difficult. If I can get to the element, then I can > get to it's parent or ancestor which could tell me that information. This is what makes me think your use case is much different from that of, say data type annotations or XForms properties. I think your use case is better addressed at application level. When I've run into such need before, I've used RDF. XLink could be another option. I think topic maps would be as well: No reason I can imagine why a subject couldn't be a particular node in an XML docuemnt. -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://4Suite.org http://fourthought.com Python&XML column: 2. Introducing PyXML - http://www.xml.com/pub/a/2002/09/25/p y.html The Past, Present and Future of Web Services 1 - http://www.webservices.org/ind ex.php/article/articleview/663/1/24/ The Past, Present and Future of Web Services 2 - 'http://www.webservices.org/in dex.php/article/articleview/679/1/24/ Serenity through markup - http://adtmag.com/article.asp?id=6807 Tip: Using generators for XML processing - http://www-106.ibm.com/developerwork s/xml/library/x-tipgenr.html
|
