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: Catalog Requirements

Paul wrote, in part:
| If you want to map the thing in a stylesheet PI, then we should
| add a STYLESHEET entry type.  That is functional/contextual.  We
| are not mapping arbitrary URIs (which I still think is out of scope).

Not to argue with the issue of scope, but I kinda want an example
of why calling out these functional/contextual classes makes a 
difference (except for DELEGATE, perhaps).  I observed before that
it's rare that the same entity gets used in two contexts.  Am I

| Maybe an example would help explain what I'm saying.

It needs to be fixed; try filling in some real identifiers.

| document instance
| -----------------
| <?xml version="1.0"?>
| <!DOCTYPE foo PUBLIC "xxx" "yyy" [
| <!ENTITY bar SYSTEM "xxx">
| <?xml-stylesheet href="xxx" type="text/css"?>
| ]>
| <foo xmlns="xxx">
| &bar;
| </foo>

regards, Terry

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

Powered by eList eXpress LLC