/ Paul Grosso <> was heard to say:
| My suggested answers: Lauren should tell Laura what we're doing and
| we should plan to cc her on the email we send. We (Lauren or her
| designate--I'm willing if designated) should inform the XML CG and
| cc them on the email to XML Schema.
Sounds like a plan.
| The OASIS Entity Resolution Technical Committee (OERTC) [1] is
| chartered to developed an entity resolution catalog format in XML
develop
[...]
| Many implementors and users have found public ids and entity
| management catalogs to be very usefulness in practical situations
useful
[...]
| [7] Not to presume to constrain a solution to the problem, but
| even something such as the following might be acceptable:
| Say that each member--that is currently a URI--is optionally
| delimited by quotes and consists of either a SystemLiteral
| (production 11 in XML 1.0) OR the second half of the
| disjunction in production 75, to wit:
| 'PUBLIC' S PubidLiteral S SystemLiteral
| (which, since it contains spaces, would necessarily be quoted).
I'm not sure this is sufficient, unless you mean to assert that
if-and-only-if it's quoted, it's to be assumed to be a public
identifier. I think there needs to be some way to distinguish public
identifiers from system identifiers in the schema hints list.
Be seeing you,
norm
--
| Someone has changed your life. Save?
Technology Development Group | (y/n)
Sun Microsystems, Inc. |
