> Example:
> <molecule>
> <price currency="USD" unit="litre">1.0</price>
> <atomArray builtin="element">O H H</atomArray>
> </molecule>
>
> This does NOT break my software because it simply scans for things it knows
> about in content (e.g. <atomArray>).
This is the perfect application of namespaces, since your module that
understands molecules wants to process only "C:molecule" elements, where
C is any prefix that is proxied to its namespace URI. Other random
"molecule" elements created by other people for other reasons should
not get processed.
> This is perhaps cleaner, but it's a lot more complicated and not many
> people (with 2-3 honourable exceptions) seem to be interested in developing
> XLink applications or software.
Part of the trouble is that the XLink WDs are old, and we keep hearing
rumors of massive changes in the next draft --- which has not yet
been forthcoming. Until that happens, I for one will shy away from
XLink.
(I'm also piqued because I sent 8 or 9 well-drafted defect reports
to the XLink/XPointer editors and heard nothing except "Thanks for
sending, we'll reply soon." That was in June. A later ping got
no reply.)
-- John Cowan http://www.ccil.org/~cowan cowan@ccil.org You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)