[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Review #2 comments: DITAVAL elements
I'm conflicted. There's an implicit 'include' for things that don¹t have an explicit 'exclude' and I think that intuitively makes sense. I don't have any objection to a particular processor calling out when that situation happens, but suggesting that *all* processors should act that way strikes me as very unnecessary. Chris Chris Nitchie (734) 330-2978 chris.nitchie@oberontech.com www.oberontech.com <http://www.oberontech.com/> Follow us: <https://www.facebook.com/oberontech> <https://twitter.com/oberontech> <http://www.linkedin.com/company/oberon-technologies> On 11/1/14, 10:18 AM, "Eliot Kimber" <ekimber@contrext.com> wrote: >I agree with Robert: I don't think the requirement has any particular >value. > >I can see the utility, as a processor-supplied option, of reporting values >that don't have explicit actions, if you're concerned about overlooked >conditions, but I would see that as a debugging utility you'd turn on >occasionally, not something processors should be expected to do all the >time. Nothing in the spec precludes processors from reporting any >information they want during processing. But there's no need to require it >in this case. > >Personally, I find the messages the OT puts out both annoying (because I >know that I intentionally didn't set actions for those values by taking >advantage of the ability to set the default action) and, even though they >are flagged as informational, I still initially read them as warnings or >errors and I'm sure many other users do too. > >Cheers, > >E. >‹‹‹‹‹ >Eliot Kimber, Owner >Contrext, LLC >http://contrext.com > > > > >On 11/1/14, 9:06 AM, "Kristen James Eberlein" ><kris@eberleinconsulting.com> wrote: > >> >> >> >> >> >> >> Referring another comment to the TC for discussion: >> >> Topic = DITAVAL elements >> DITAweb URL: >> http://ditaweb.com/oasis-dita/#/00074601-DA$00074098-DB$DITAVAL >> elements >> >> Prose in question: >> >> Notes on ditaval messages >> Conditional processing code should provide a report of any attribute >> values encountered in content that do not have an explicit action >> associated with them. >> >> Comments: >> >> >>* Eliot Kimber: "I think this needs to clarify that specifying >> an attribute with no value constitutes an explicit action. >> Currently the OT will report attribute values that are defaulted >> to exclude via prop elements. It should not." >> >>* Robert Anderson: "I'm finding this whole sentence somewhat >> questionable. I'm not sure the spec should be forcing >> applications to do this. Referring to TC for thoughts." >> >> >> >> -- >> Best, >> Kris >> >> Kristen James Eberlein >> Chair, OASIS DITA Technical Committee >> Principal consultant, Eberlein Consulting >> www.eberleinconsulting.com <http://www.eberleinconsulting.com> >> +1 919 682-2290; kriseberlein (skype) >> >> >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe from this mail list, you must leave the OASIS TC that >>generates this mail. Follow this link to all your TCs in OASIS at: >>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. Follow this link to all your TCs in OASIS at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]