OASIS Open Mailing List Archives  ·  All Lists  ·  dita  ·  2015-01

dita — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

Normative statements about strong and weak constraints


Is the following what we want to say? Weak and strong constraints Constraints can be classified into two categories: Weak and strong. This classification determines whether processors check and enforce validity during @conref or @conkeyref resolution. Constraints are declared in the @domains attribute on the root element of a document instance. Any constraint declaration can designate a constraint as strong. Processors MAY perform constraint compatibility checking. If processors perform constraint compatibility checking, they SHOULD enforce constraint compatibility for strong constraints. By default, constraints are weak unless one of the following is true: The constraint module explicitly designates that the constraint is a strong constraint. A constraint can be designated as strong by prefixing the letter s to the domains attribute contribution, for example, s(topic task strictTaskbody-c) . The processor has been configured to treat all constraints as strong. 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)

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]