OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [entity-resolution-comment] Some queries on the XMLCatalogsspec


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ Richard Tobin <richard@cogsci.ed.ac.uk> was heard to say:
|> | Step 3 of 7.1.2 does not mention that the rewriteSystem entry with the
|> | longest systemIdStartString is the only one used.  This is stated in
|> | 6.5.5, but it should be explicit in the description of the algorithm.
|> 
|> Fixed.
|
| ... and the same for rewriteURI in 7.2.2.

Fixed.

|> | Is there a recommended way to handle external identifiers when parsing
|> | catalog files themselves?  Obviously they cannot be looked up in the
|> | catalog.  Is it reasonable to have a copy of catalog.dtd built-in to
|> | the parser and special-case its system and public identifiers?
|> 
|> This is a *really* good point and one that I stumbled over just
|> recently myself.
|> 
|> (Lauren, I'd like to discuss this at the next meeting.)
|> 
|> Richard, what do you think the right answer is?
|
| For RXP, I use a special entity resolver while reading catalog files.
| If an entity has either the system ID or the public ID of the catalog
| DTD, it uses a compiled-in copy of the DTD, otherwise it just uses the
| system ID as a URI in the normal way without any catalog processing.
| I suppose a schema processor that uses a catalog to fetch schemas
| might do the same sort of thing.

Makes sense. At the telcon today, we agreed to make a note of this in
the spec.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | The common excuse of those who bring
XML Standards Architect | misfortune on others is that they desire
Web Tech. and Standards | their good.--Vauvenargues
Sun Microsystems, Inc.  | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+pZFnOyltUcwYWjsRAtbyAJsFsUIiFL6wQihnpPjPkeHWkFjpIgCfd3L6
ka7AnAEkF84byLxW5CMZtj8=
=q+OL
-----END PGP SIGNATURE-----


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]