Actually, I think there are both use cases for section sharing (or
merging) and resource sharing. That being said, I don't have a good
solution for either just yet.
Nate
Rich Thompson wrote:
OF2E9E2F6E.F1D6825B-ON85257394.006A7D19-85257394.006AF4D8@us.ibm.com"
type="cite">
I turned on track changes to suggest
a bunch of editorial level changes.
I haven't had time to dig into the
type
definitions yet, but will try to get to them in a separate pass.
My biggest concern is with section 11.3.2.4
as it sets up sharing at a
section
level while providing an example of sharing at a resource level. This
seems
like a mismatch that we ought to address though I do not have a
suggestion
on how to address it at the moment. Perhaps a variant on Mike's earlier
proposal would make sense.
Rich
Here’s my latest crack at
it.
Nate
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities,
that may be confidential, proprietary, copyrighted and/or legally
privileged,
and is intended solely for the use of the individual or entity named in
this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then
delete it.[attachment "multiSectionRendering-singleRequest.doc"
deleted by Rich Thompson/Watson/IBM] ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
This body part will be downloaded on demand.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. |