The solution is in there, but sort of
buried. I tried to beef it up in the latest version. Also added some explanations
of why it's limited to metadata attributes (ie exactly how much processing
logic and rules are involved in prepping any given base attribute to become
specializable).
Michael Priestley
"Chris Wong"
<>
07/27/2005 04:49 PM
To
<>
cc
Subject
RE: [dita] Groups - DITA
1.1 Issue #20 (IssueNumber20.html) uploaded
> -----Original Message-----
> From: Paul Grosso [mailto:]
> Sent: Tuesday, July 26, 2005 12:04 PM
> To:
> Subject: RE: [dita] Groups - DITA 1.1 Issue #20 (IssueNumber20.html)
> uploaded
>
> > -----Original Message-----
> > From: [mailto:]
> > Sent: Monday, 2005 July 25 18:52
> > To:
> > Subject: [dita] Groups - DITA 1.1 Issue #20 (IssueNumber20.html)
uploaded
> > ...
> > The document named DITA 1.1 Issue #20 (IssueNumber20.html) has
been
> > submitted by Michael Priestley to the OASIS Darwin Information
Typing
> > Architecture (DITA) TC document repository.
> >
> > Document Description:
> > Extensible metadata attributes for conditional processing (includes
> > proposal to make all attributes specializable)
...
>
> I'm interested in this issue, but I'm unclear on the status.
>
> The above document outlines the issue, but not the proposed
> solution, right?
I second Paul's request. I would very much like to see a concrete proposal.
I'd also like to hear some clarification on why adding attributes is OK
for metadata attributes but not in the general case.
Chris
