I believe Hivemind id's are mapped to java namespaces more than anything
else, following package name and class syntax. For one it allows
shortcutting service interface names (new addition in 1.1) when the module
is declared to be in the same namespace as the interface. No need to type
the fully qualified class name for it in the descriptor.
Cheers,
Johan
On Wed, 16 Feb 2005 12:55:25 -0700, Dave Smith <[EMAIL PROTECTED]> wrote:
My reading of the XML spec is that IDs must be a "Name" production.
Specifically see section 3.3.1, validity constrains on ID:
"Values of type ID must match the Name production."
And from section 2.3 of the spec:
"[Definition:] 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."
All of the above would imply that hivemind is being unnecessarily
strict on what IDs may be. Or is there some piece of functionality in
Hivemind that requires a particular format on those ids?
D.
On Wed, 16 Feb 2005 14:45:09 -0300, Marcus Brito <[EMAIL PROTECTED]>
wrote:
> So, why does Hivemind require that IDs only have alphanumeric
> characters? Is there something I'm missing here?
Not hivemind per se, but the XML specification. "id" attributes are
declared in the DTD as ID types, which, according to the XML
specification, should be a string composed only from letters and
numbers.
-- Marcus Brito
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
