Graydon, please post general how-to questions on the dita-users list. This list is for DITA TC use only.
You will get an answer there on how to do what you want to do, as
well as pointers to understanding the constraint mechanism.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
On 7/3/2019 9:26 AM, Graydon Saunders
wrote:
In what way is "example of a constraining a base element's content model from mixed to element-only" insufficiently general?
It's a common thing in a DITA deployment to prefer a content model which insists on li/p or entry/p or that section/text() isn't permitted. It's not obviously improper to want such a constraint. Any such constraint on base elements should be implemented in such a way that any subsequent specializations, whether via pre-existing domains or a domain defined specifically for a particular deployment, can rely on the constraint of the base element to operate throughout the content model without further adjustments.
It's possible that the TC consensus position is that base elements should NOT be constrained and that any desired versions with constrained content models relative to the base version should be specialized via a domain, acquiring different names and longer class attribute values in the process.
If the TC consensus position is that, yes, a DITA deployment ought to be able to constrain the content models of base elements, it would be useful to have examples of how this is expected to be done.
Graydon Saunders |ÂPublishing Solutions DeveloperÂ|ÂPrecision ContentÂ
Direct:Â+1Â(647)265-8500 x106|ÂEmail:Âgraydon@precisioncontent.comÂ|Âwww.precisioncontent.comÂ
Â
Unlock the Knowledge in Your Enterpriseâ
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.ÂPlease notify us by return email if you have received this email in error.ÂÂ2019, Precision Content Authoring Solutions Inc, Mississauga, Ontario, Canada
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Eliot Kimber <ekimber@contrext.com>
Sent: 03 July 2019 08:50
To: dita@lists.oasis-open.org
Subject: Re: [dita] Implementing a constraint with the RNG _expression_ of the DITA 1.3 standardÂPlease ask your how-to question on the DITA Users List. I'm not sure I fully understand your requirement but I suspect you're making it harder than it is.
Cheers,
E.
--
Eliot Kimber
http://contrext.com
Â
ïOn 7/3/19, 7:38 AM, "Graydon Saunders" <dita@lists.oasis-open.org on behalf of graydon@precisioncontent.com> wrote:
ÂÂÂ Do
ÂÂÂÂ we want to simply duplicate these examples in RNG?
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ The example I would like to have in RNG is the one from my original question; constrain a mixed-content base element's content model to be element-only so that the constrained element is generally
ÂÂÂÂ available to domain modules incorporated into a document type without requiring additional work on the constraint if a domain is later added to the document.
ÂÂÂ
ÂÂÂ
 I don't think there's currently an example of that kind of constraint; experience says that this is a reasonably frequent thing to want. I don't think it would hurt to have a The Approved Way
ÂÂÂÂ example of doing so with a DTD, as well as the RNG example.
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ Graydon Saunders | Publishing Solutions Developer | Precision
ÂÂÂÂ Content
ÂÂÂ Direct: +1 (647)265-8500
ÂÂÂÂ x106| Email: graydon@precisioncontent.com | www.precisioncontent.com <https://www.precisioncontent.com>
ÂÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂÂ
ÂÂÂ Unlock the Knowledge in Your Enterpriseâ
ÂÂÂ
ÂÂÂ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
ÂÂÂÂ If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please
ÂÂÂÂ notify us by return email if you have received this email in error. Â2019, Precision Content Authoring Solutions Inc, Mississauga, Ontario, Canada
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ ________________________________________
ÂÂÂ From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Kristen James Eberlein <kris@eberleinconsulting.com>
ÂÂÂ Sent: 02 July 2019 20:04
ÂÂÂ To: dita@lists.oasis-open.org
ÂÂÂ Subject: Re: [dita] Implementing a constraint with the RNG _expression_ of the DITA 1.3 standard
ÂÂÂ
ÂÂÂ The current spec contains examples of the following:
ÂÂÂ
ÂÂÂ * Redefine the content model for the <topic> element (DTD)
ÂÂÂ
ÂÂÂ * Constrain attributes for the <section> element (DTD)
ÂÂÂ
ÂÂÂ * Constrain a domain module (DTD)
ÂÂÂ
ÂÂÂ * Replace a base element with the domain extensions (DTD)
ÂÂÂ
ÂÂÂ * Apply multiple constraints to a single document-type (DTD)
ÂÂÂ
ÂÂÂ * Correct the constraint for the machinery task (DTD)
ÂÂÂ
ÂÂÂ
ÂÂÂ Do we want to simply duplicate these examples in RNG?
ÂÂÂ
ÂÂÂ Best,
ÂÂÂ Kris
ÂÂÂ
ÂÂÂ Kristen James Eberlein
ÂÂÂ Chair, OASIS DITA Technical Committee
ÂÂÂ Principal consultant, Eberlein Consulting
ÂÂÂ www.eberleinconsulting.com <http://www.eberleinconsulting.com>
ÂÂÂ +1 919 622-1501; kriseberlein (skype)
ÂÂÂ
ÂÂÂ
ÂÂÂ On 7/2/2019 5:52 PM, Eliot Kimber wrote:
ÂÂÂ
ÂÂÂ
ÂÂÂ We should definitely have examples of RNG constraints.
ÂÂÂ
ÂÂÂ The constraint modules shipped with DITA 1.3 demonstrate the general techniques.
ÂÂÂ
ÂÂÂ But fundamentally it's the same as for DTDs: you override the base declarations of the patterns.
ÂÂÂ
ÂÂÂ Note that the current (unreleased but committed) state of the RNG to DTD generator automatically translates RNG <notAllowed> into the equivalent DTD entity declaration overrides as required for wholesale constraint of things defined in commonElements or topic.mod. This makes defining this type of constraint much easier since it does a whole bunch of cutting and pasting for you and then automatically omits those things that you've marked as not allowed.
ÂÂÂ
ÂÂÂ Should I ever be able to actually get this code a releasable state it will very convenient...
ÂÂÂ
ÂÂÂ Cheers,
ÂÂÂ
ÂÂÂ E.
ÂÂÂ
ÂÂÂ --
ÂÂÂ Eliot Kimber
ÂÂÂ http://contrext.com
ÂÂÂÂ
ÂÂÂ
ÂÂÂ ïOn 7/2/19, 12:33 PM, "Kristen James Eberlein" <dita@lists.oasis-open.org on behalf of kris@eberleinconsulting.com> <mailto:dita@lists.oasis-open.orgonbehalfofkris@eberleinconsulting.com> wrote:
ÂÂÂ
ÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ Yes, constraints can be expressed in RNG; RNG is the normative
ÂÂÂÂÂÂÂÂÂÂÂÂÂ form of the DITA grammar files. In fact, constraints are easier to
ÂÂÂÂÂÂÂÂÂÂÂÂÂ develop in in RNG than DTD!
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ The spec only contains examples of constraints in DTD, rather
ÂÂÂÂÂÂÂÂÂÂÂÂÂ than RNG, because that is what we had available and the
ÂÂÂÂÂÂÂÂÂÂÂÂÂ information that many people wanted.
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ TC members, should we consider reworking our constraints examples
ÂÂÂÂÂÂÂÂÂÂÂÂÂ to be in RNG rather than DTD? Or adding parallel examples with RNG
ÂÂÂÂÂÂÂÂÂÂÂÂÂ code?
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ Best,
ÂÂÂÂÂÂÂÂÂÂÂÂÂ Kris
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ Kristen James Eberlein
ÂÂÂÂÂÂÂÂÂÂÂÂÂ Chair, OASIS DITA Technical Committee
ÂÂÂÂÂÂÂÂÂÂÂÂÂ Principal consultant, Eberlein Consulting
ÂÂÂÂÂÂÂÂÂÂÂÂÂ www.eberleinconsulting.com <http://www.eberleinconsulting.com> <http://www.eberleinconsulting.com> <http://www.eberleinconsulting.com>
ÂÂÂÂÂÂÂÂÂÂÂÂÂ +1 919 622-1501; kriseberlein (skype)
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ On 7/2/2019 1:26 PM, Graydon Saunders
ÂÂÂÂÂÂÂÂÂÂÂÂÂ wrote:
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ In terms of the mechanics, certainly, and I will go post there.
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ In terms of whether it is possible to support constraints -- as
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ distinct from specializations -- in the RNG implementation, it
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ might be of interest to the technical committee.
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Thanks!
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Graydon Saunders
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ | Publishing Solutions Developer | Precision
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Content
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Direct: +1 (647)265-8500 x106| Email: graydon@precisioncontent.com | www.precisioncontent.com <http://www.precisioncontent.com> <https://www.precisioncontent.com> <https://www.precisioncontent.com>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Unlock the Knowledge in Your
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Enterpriseâ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ This
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ email and any files transmitted with it are
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ confidential and intended solely for the use of
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ the individual or entity to whom they are
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ addressed. If you are not the intended recipient
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ you are notified that disclosing, copying,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ distributing or taking any action in reliance on
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ the contents of this information is strictly
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ prohibited. Please
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ notify us by return email if you have received
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ this email in error. Â2019,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Precision Content Authoring Solutions Inc,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Mississauga, Ontario, Canada
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ ________________________________________
ÂÂÂÂÂÂÂÂÂÂÂÂÂ From:
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ dita@lists.oasis-open.org <dita@lists.oasis-open.org> <mailto:dita@lists.oasis-open.org> <mailto:dita@lists.oasis-open.org> <mailto:dita@lists.oasis-open.org> on
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ behalf of Kristen James Eberlein
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ <kris@eberleinconsulting.com> <mailto:kris@eberleinconsulting.com> <mailto:kris@eberleinconsulting.com> <mailto:kris@eberleinconsulting.com>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Sent: 02 July 2019 13:22
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ To: dita@lists.oasis-open.org
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Subject: Re: [dita] Implementing a constraint with the
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ RNG _expression_ of the DITA 1.3 standard
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Graydon, this is perhaps a better post for the dita-users
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ list. The DITA TC list is for discussing the work of the DITA
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Technical Committee.
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Best,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Kris
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Kristen James Eberlein
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Chair, OASIS DITA Technical Committee
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Principal consultant, Eberlein Consulting
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ www.eberleinconsulting.com <http://www.eberleinconsulting.com> <http://www.eberleinconsulting.com> <http://www.eberleinconsulting.com>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ +1 919 622-1501; kriseberlein (skype)
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ On 7/2/2019 12:35 PM, Graydon
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Saunders wrote:
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Hello --
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Using the RNG
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ implementation of the DITA 1.3 standard, I want to
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ constrain the li element
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ so that its content model permits only a p element.
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ I want to do this in such a way that as domain
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ specializations are added to document definitions,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ those domain specializations will acquire this
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ constraint without any further changes being required.
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ How should I do this?
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Thanks!
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Graydon Saunders
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ | Publishing Solutions Developer | Precision
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Content
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Direct: +1 (647)265-8500
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ x106| Email: graydon@precisioncontent.com | www.precisioncontent.com <http://www.precisioncontent.com> <https://www.precisioncontent.com> <https://www.precisioncontent.com>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Unlock the
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Knowledge in Your Enterpriseâ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ This email and any files
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ transmitted with it are confidential and
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ intended solely for the use of the
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ individual or entity to whom they are
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ addressed. If you are not the intended
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ recipient you are notified that disclosing,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ copying, distributing or taking any action
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ in reliance on the contents of this
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ information is strictly prohibited. Please notify us by return email if
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ you have received this email in error. Â2019, Precision
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Content Authoring Solutions Inc,
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Mississauga, Ontario, Canada
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ
ÂÂÂ ---------------------------------------------------------------------
ÂÂÂ 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
ÂÂÂ
ÂÂÂ
---------------------------------------------------------------------
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
