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


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

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

Subject: RE: locating schemas via public ids

>Norm Walsh wrote on Wednesday, January 24, 2001 3:16 PM
>I think there needs to be some way to distinguish public
>identifiers from system identifiers in the schema hints list.

I agree with this suggestion.  However, does that mean something other than
the way that SYSTEM and PUBLIC identifiers are mentioned in

'An example of an XML document with a document type declaration:

<?xml version="1.0"?> <!DOCTYPE greeting SYSTEM "hello.dtd">
<greeting>Hello, world!</greeting> 

The system identifier "hello.dtd" gives the address (a URI reference) of a
DTD for the document.'

If the portions [lines 52 -56 ?] of TR9401 that read (as follows below) are
written as a positive requirement, then it appears that, if we follow
TR9401, we will have our hint?

'Valid FSIs include unpathed, relative, and absolute file names and URLs as
well as FSIs with explicit storage managers (as defined in the SGML General
Facilities). Most of the examples in this resolution will show s.o.i.s, but
this resolution allows FSIs as the right hand side of most catalog entries.
For example, the following are possible catalog entries that associate a
public identifier with an s.o.i.:

PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN" "iso-lat1.gml"
PUBLIC "-//USA/AAP//DTD BK-1//EN" "aapbook.dtd"
PUBLIC "-//ACME//DTD Report//EN" "http://acme.com/dtds/report.dtd"'

David Leland
-----Original Message-----
From: Norman Walsh [mailto:ndw@nwalsh.com]
Sent: Wednesday, January 24, 2001 3:16 PM
To: entity-resolution@lists.oasis-open.org
Subject: Re: locating schemas via public ids

/ Paul Grosso <pgrosso@arbortext.com> 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


| Many implementors and users have found public ids and entity
| management catalogs to be very usefulness in practical situations


| [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,

Norman.Walsh@East.Sun.COM    | Someone has changed your life. Save?
Technology Development Group | (y/n)
Sun Microsystems, Inc.       | 

This electronic transmission and any files attached to it are strictly
confidential and intended solely for the addressee.  If you are not 
the intended addressee, you must not disclose, copy or take any action
in reliance of this transmission.  If you have received this 
transmission in error, please notify us by return and delete the same.
Further enquiries/returns can be posted to postmaster@informa.com
Thank you.

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

Powered by eList eXpress LLC