[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Questions arising from the DITAVAL elements review
Typing up an answer in case I'm really late on Tuesday.
I definitely think we should emphasize that "conditional processing" includes filtering and flagging.
I think I like conditional processing better than "profiling", which is the other term that folks seem to use. I honestly never understood the definition of "profiling". (I wonder if "profiling" may end up on an avoid list for inclusive writing, as well)
Potentially, "filtering and flagging" may be the better phrase, but it's still a mouthful. "Conditional processing and flagging" is also a mouthful, but clear.
I think I prefer Gershon's revision without the parenthesis.
I also wonder if that same rewrite needs to be added to all the flagging-specific elements (<alt-text>, <endflag>, <startflag>, <style-conflict>).
Thanks,
Zoë
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of kris eberleinconsulting.com <kris@eberleinconsulting.com>
Sent: Sunday, March 20, 2022 2:18 PM To: dita <dita@lists.oasis-open.org> Subject: [dita] Questions arising from the DITAVAL elements review There are some comments in the current DITAweb review that we want to bring to the TC for discussion:
The term “conditional processing”
How can we best be clear that DITA supports both filtering and flagging? Do we stress that conditional processing = filtering + flagging? Change the terminology that we use?
How we handle definitions for the “flagging” attributes on <prop> and <revprop>
We have conflicting comments about this format:
What do we want to do with these definitions? The attributes are @backcolor, @color, @outputclass, and @style.
Best, Kris |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]