Issues Document
OASIS Entity Resolution Technical
Committee
Edited by
Norman Walsh
$Id: issues.xml,v 1.2 2000/12/11
23:00:09 ndw Exp $
$Date: 2000/12/11 23:00:09 $
Revision
History |
Revision 0.2 |
11 Dec 2000 |
ndw |
Additional issue from 11
Dec 2000 telcon. |
Revision 0.1 |
27 Nov 2000 |
ndw |
First draft; constructed
from conversations at the 27 Nov 2000 telcon. |
This document tracks open issues in the OASIS Entity
Resolution Technical Committee.
-
Which schema language is
normative?
-
Should our requirements
state explicitly that we require XML 1.0 + Namespaces?
(As opposed to the more vague statement "XML" from
which someone might conclude that XML Schemas or RELAX
or XInclude or some other specification was
relevant.)
-
What do we do about
delegate? Do we need to have a delegate for public
identifiers, a delegate for system identifiers, etc.
This is the functional class versus syntax issue again.
URNs where?
-
Do we want to allow the
catalog to map entity names to URIs?
-
What is the extensibility
mechanism? Elements from another namespace?
-
Can an extension element
change the semantics of an element from the catalog
(non-extension) namespace.
-
The TR9401 BASE declaration
had a scope that we've lost in the transition to
xml:base. We could attack this problem by allowing the
root element to be recursive. We could also attack this
by adding a distinct grouping element.