[
Lists Home |
Date Index |
Thread Index
]
Here are several off the top of my head:
(1) "feet":
- One occurrence could be a string that contains the anatomical
condition of a foot, perhaps in a list of body parts in a doctor's form;
- Another occurrence could be a distance;
NOTE: I believe that using an element named "feet" is probably not a
good approach, as it is not sufficiently semantically descriptive -
especially in the second case, which really should be "Distance" (or
similar), with an attribute containing the unit of measure.
(2) "title":
- One occurrence could be the title of a book;
- Another occurrence could be a title on a house;
(3) "StateCode" - I think this is the best example of the 3
- One occurrence could be a US state;
- Another occurrence (in a scientific context) could be the state of an
element (gasous, etc. - I don't recally the other possibilities)
This third example could very well occur in a domain such as the US
Environmental Protection Agency (EPA).
Hope that helps,
Joe Chiusano
Booz | Allen | Hamilton
Bill de hÓra wrote:
>
> Does anyone have an example of a collision that can only be solved,
> or even best be solved with XML Namespaces? A neccessary condition
> is ideal, but examples where namespace represents an optimal design
> decision will do. I'm asking for two reasons:
>
> - in my work with XML I've never run across a collision problem
> that seemed to require namespaces. I wondering whether they're rare
> or whether the markup I dela with is unusual.
>
> - I'm looking for markup that I can use for test cases and
> thinking about the matter.
>
> I went looking in the Namepsaces spec and found this example and an
> assertion:
>
> [[[
> <section><title>Book-Signing Event</title>
> <signing>
> <author title="Mr" name="Vikram Seth" />
> <book title="A Suitable Boy" price="$22.95" /></signing>
> <signing>
> <author title="Dr" name="Oliver Sacks" />
> <book title="The Island of the Color-Blind" price="$12.95"
> /></signing>
> </section>
>
> In this example, there are three occurrences of the name title
> within markup, and the name alone clearly provides insufficient
> information to allow correct processing by a software module
> ]]]
>
> It demonstrates no such thing to me. For example, here is the
> sufficient information:
>
> /section/title
> /section/signing/author@title
> /section/signing/book@title
>
> I suspect this particular assertion about the insufficiency of
> traditional namespaces in the spec is false. I believe for it to be
> true, there would need to exist markup for which no keys could be
> computed to dilineate one element or attribute from another.
>
> Bill de hÓra
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
