I think the old LocationUri is best because a system's URI resolver
may accept a URI as an acceptable de-referenced representation of a
virtual location.
What if, say, one of the locations is a database lookup table?
. . . . . . . . . . . . Ken
At 2007-08-13 11:08 +0100, Anthony B. Coates (Miley Watts) wrote:
>I'm currently editing the genericode Schema to make the public review
>changes. However, while doing so, I noticed that one of the element names
>that I originally chose, "LocationUri", doesn't make a lot of sense, since
>really this has to be a URL. I think it should be called "LocationUrl".
>Would anyone be opposed to this change, or does anyone have any other
>comments about the suggestion? Thanks,
--
Upcoming public training: XSLT/XSL-FO Sep 10, UBL/code lists Oct 1
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:
publicly-available developer resources and training
G. Ken Holman
mailto:
Crane Softwrights Ltd.
http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0
+1(613)489-0999 (F:-0995)
Male Cancer Awareness Jul'07 http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
