[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [relax-ng] Minutes for RELAX NG TC Meeting 2002-02-28
Michael> -Key/keyref? Michael> Michael> James: key/keyref is a missing piece in RELAX NG. We need a streaming Michael> solution. What we discussed before 1.0 was a bit of a hack. We need a fully Michael> baked proposal, coming as a spark of inspiration from someone on the list. Michael> David: We should build a list of use cases, then figure out what we want to Michael> do. Michael> Mike: It seems important enough that we do it right. Michael> John: Important but not imperative. Michael> James: RELAX NG will survive without it but... I said: I do not think that key/keyref as a committee specification is mandatory. I think that people can use Schematron or their own mechanisms. I also think that identity constraints are too difficult or immmature at this stage of the game. Furthermore, as Kohsuke said, design by committee is not a good idea for such specs. -- MURATA Makoto (FAMILY Given) <EB2M-MRT@asahi-net.or.jp>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC