OASIS Darwin Information Typing Architecture (DITA) TC

Here is the updated content: Weak and strong constraints Constraints can be classified into two categories: Weak and strong. This classification determines whether processors enforce strict compatibility during @conref or @conkeyref resolution. Strong constraints Constraints for which processors enforce strict compatibility during @conref or @conkeyref resolution. Weak constraints Constraints for which a processor does not enforce strict compatibility during @conref or @conkeyref resolution. By default, constraints are weak unless they are explicitly designated as strong. Any constraint declaration can designate a constraint as strong. A constraint can be designated as strong by prefixing the letter s to the domains attribute contribution, for example, s(topic task strictTaskbody-c) . Processors also can be configured to treat all constraints as strong. The following behavior is expected of processors: Processors MAY perform constraint compatibility checking. If processors perform constraint compatibility checking, they SHOULD enforce strict compatibility for strong constraints. Processors MAY have an option for configuring whether all constraints are treated as strong constraints. -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype)

That looks good to me. I like the clarity. Bob On Thu, Jan 29, 2015 at 3:00 AM, Kristen James Eberlein < kris@eberleinconsulting.com > wrote: Here is the updated content: Weak and strong constraints Constraints can be classified into two categories: Weak and strong. This classification determines whether processors enforce strict compatibility during @conref or @conkeyref resolution. Strong constraints Constraints for which processors enforce strict compatibility during @conref or @conkeyref resolution. Weak constraints Constraints for which a processor does not enforce strict compatibility during @conref or @conkeyref resolution. By default, constraints are weak unless they are explicitly designated as strong. Any constraint declaration can designate a constraint as strong. A constraint can be designated as strong by prefixing the letter "s" to the domains attribute contribution, for example, "s(topic task strictTaskbody-c)" . Processors also can be configured to treat all constraints as strong. The following behavior is expected of processors: Processors MAY perform constraint compatibility checking. If processors perform constraint compatibility checking, they SHOULD enforce strict compatibility for strong constraints. Processors MAY have an option for configuring whether all constraints are treated as strong constraints. -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting 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 -- Bob Thomas +1 720 201 8260 Skype: bob.thomas.colorado Instant messaging: Gmail chat ( bob.thomas@tagsmiths.com ) or Skype Time zone: Mountain (GMT-7)

Is there language somewhere about what it means to check or enforce a weak constraint? The strict constraints are pretty well described. Cheers, E. ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 1/29/15, 4:00 AM, "Kristen James Eberlein" <kris@eberleinconsulting.com> wrote: > > > > > > > Here is the updated content: > > Weak and strong constraints > > Constraints can be classified into two > categories: Weak and strong. This classification determines > whether processors enforce strict compatibility during @conref or >@conkeyref > resolution. > > Strong constraints > Constraints for which processors enforce strict > compatibility during @conref or @conkeyref resolution. > Weak constraints > Constraints for which a processor does not > enforce strict compatibility during @conref > or @conkeyref resolution. > > By default, constraints are weak unless they are > explicitly designated as strong. > Any constraint declaration can designate a constraint > as strong. A constraint can be designated as strong by prefixing > the letter "s" to the domains attribute contribution, for > example, "s(topic task > strictTaskbody-c)". Processors also can be configured > to treat all constraints as strong. > The following behavior is expected of processors: > > >* Processors MAY > perform constraint compatibility checking. > >* If processors perform constraint compatibility > checking, they SHOULD > enforce strict compatibility for strong constraints. > >* Processors MAY > have an option for configuring whether all constraints are > treated as strong constraints. > > > > > -- > 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 > >

Looks very understandable to me.   I almost think this sentence "Processors also can be configured to treat all constraints as strong." is unnecessary in the penultimate paragraph. Its information is duplicated in the final bullet at the end. But perhaps the duplication is not a bad thing.   mag     From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org] On Behalf Of Kristen James Eberlein Sent: Thursday, January 29, 2015 2:01 AM To: DITA TC Subject: [dita] Updated topic about "Weak and strong constraints"   Here is the updated content: Weak and strong constraints Constraints can be classified into two categories: Weak and strong. This classification determines whether processors enforce strict compatibility during @conref or @conkeyref resolution. Strong constraints Constraints for which processors enforce strict compatibility during @conref or @conkeyref resolution. Weak constraints Constraints for which a processor does not enforce strict compatibility during @conref or @conkeyref resolution. By default, constraints are weak unless they are explicitly designated as strong. Any constraint declaration can designate a constraint as strong. A constraint can be designated as strong by prefixing the letter "s" to the domains attribute contribution, for example, "s(topic task strictTaskbody-c)" . Processors also can be configured to treat all constraints as strong. The following behavior is expected of processors: Processors MAY perform constraint compatibility checking. If processors perform constraint compatibility checking, they SHOULD enforce strict compatibility for strong constraints. Processors MAY have an option for configuring whether all constraints are treated as strong constraints.   -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting 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