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: Issues V0.3

Here is the revised issues list.

Title: Issues Document

Issues Document

OASIS Entity Resolution Technical Committee

Edited by

Norman Walsh

$Id: issues.xml,v 1.3 2001/01/08 23:16:57 ndw Exp $

$Date: 2001/01/08 23:16:57 $

Revision History
Revision 0.3 8 Jan 2001 ndw
Additional issues from 8 Jan 2001 telcon.
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.

  1. Which schema language is normative?

  2. 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.)

  3. 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?

  4. Do we want to allow the catalog to map entity names to URIs?

  5. What is the extensibility mechanism? Elements from another namespace?

  6. Can an extension element change the semantics of an element from the catalog (non-extension) namespace.

  7. 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.

  8. Do we want to allow delegation based on system identifiers (in addition to public identifiers). See the semantics thread.

  9. Should the override attribute on catalog have a default value or be required?

  10. Should the nextCatalog directive be required to occur only at the end of the catalog.

                                        Be seeing you,

Norman.Walsh@East.Sun.COM | Don't limit your child to your own
XML Technology Center     | learning, for he was born in another
Sun Microsystems, Inc.    | time.--Rabbinic Saying

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

Powered by eList eXpress LLC