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: [entity-resolution] minutes from meeting January 14, 2003


Present: Norm, Normand, Lauren, Paul, David

These seem to be the only issues left; we have discussed most of 
these before so this is the last chance.

1) The TC agreed that those who disagree with the specification on 
this point have not yet made a strong enough case for it to be 
changed.

2) the implementor needs different tables anyway because different 
catalog files may apply. Groups may in fact be superfluous, since 
people tend to put different catalog files in different directories. 
Entries in the catalog will typically apply only to those files in 
that directory, and then people link catalogs with next catalog. We 
probably kept it to support BASE in TR 9401; xml:base and groups 
seems a more XML-friendly way to do this. The TC agreed to leave 
groups in to enable translation of SOCAT into catalogs.

We can't take the prefer attribute off groups because of the SOCAT 
compatibility as well. People may be using them and it does seem to 
be implementable, so we see no reason to disregard SOCAT 
compatibility on this issue.

3) This is the only way to provide public ids for things like 
stylesheets that don't have them. In contrast to David Brownell's 
comment, input system ids constructed using this can match (at least 
in theory). The TC did not come up with a better solution to the 
problem. Nobody on the TC thinks we should take the feature out; Norm 
will attempt some editorial clarifications and add some examples.

4) The TC agrees that it should define a feature flag for this. Norm 
will add this to the spec, perhaps in an appendix. We can't make it 
normative, since we can't force other specifications to take it.

5) We should construct some test cases. We will probably not be 
exhaustive. Norm will contribute some test cases he already has. The 
TC will be appreciative of any test cases that can be contributed 
from other sources.

Norm: make the editorial changes. Due February 18.

Next meeting: Feb 25th at 2 pm Eastern. 
Tel:+1.865.540.8745 with access code: 749667.

Agenda: look at the latest draft and consider whether we can move it 
to committee specification.
Discuss any other issues that may arise between now and then.
Discuss the issue of OASIS standard.

cheers,

Lauren



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


Powered by eList eXpress LLC