> Whatever really, as long as uniqueness is guaranteed!).
>
> OTOH, in order to properly support evolution of the application the ID
> should perhaps be prefixed with a vendor tag (e.g. "com.iona.12").
> Otherwise there are some insert-link-remove-insert-link scenarios that
> will cause faulty/stale links. For example: element is inserted, then
> linked to giving it ID "12", element is removed, and then one element is
> added and linked to, which gives it the ID "12" which is free. The first
> link is now faulty. Using prefixes will make it easier, or rather will
> make it *possible*, for vendor tools to determine which ID's are free to
> use. Blah, etc, you get the picture..
>
One thing to be aware of is the constraints placed on the value of an ID tag
in XML. It must conform to a "Name":
>From http://www.w3.org/TR/PR-xml.html:
Section 3.3.1
Validity Constraint - ID:
Values of this type must be valid Name symbols. A name must not appear more
than once in an XML document as a value of this type; i.e., ID values must
uniquely identify the elements which bear them.
Section 2.3
A Name is a token beginning with a letter or one of a few punctuation
characters, and continuing with letters, digits, hyphens, underscores,
colons, or full stops, together known as name characters. Names beginning
with the string "xml", or any string which would match (('X'|'x') ('M'|'m')
('L'|'l')), are reserved for standardization in this or future versions of
this specification.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
