Re: 7 May 2001 Draft Specification

[Norman Walsh <ndw@nwalsh.com>]

/ Rob Lugt <roblugt@elcel.com> was heard to say:
| ElCel Technology is working on implementing an XML Catalog based on your
| draft specification of 7th May 2001.

Cool.

| In the section titled "Common Entries", you describe the two independent
| ways that the catalog may be used:-
|     1) Entity replacement text location
|     2) URI location
| 
| However, the proposed catalog format does not seem to provide a means of
| specifying entity replacement text and the ability to specify replacement
| text does not appear in your requirements statement.  Has this alternative
| use of the catalog been dropped?  Perhaps you see this as being a vendor
| extension?

I'm not sure I understand your question.

Given an entity of the form

  <!ENTITY foo PUBLIC "pubid" "sysid">

in your source document, the catalog-based entity resolution process
can identify the resource to associate with 'foo' based on either its
public or system identifiers.

In a purely URI-based scenario, such as this one:

  <xsl:import href="http://www.example.com/stylesheets/test.xsl"/>

the catalog-based URI resolution process can identify the resource
to import based on the specified URI.

If you're asking about entities of this form:

  <!ENTITY bar "some replacement text">

catalog-based resolution (and in fact resolution in general) has never
been a relevant part of the process. However, all entities of this
form can be transformed into entities of the former type by putting
"some replacement text" in an external file and using public and/or
system identifiers to locate it.

Does that description help?

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | Sites disappear; others are created. That
XML Standards Engineer | nasty little railway station, devoid of taste
Technology Dev. Group  | and style, becomes an element of beauty in the
Sun Microsystems, Inc. | landscape which first made it ugly.--R\'emy De
                       | Gourmont

------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: entity-resolution-comment-request@lists.oasis-open.org