And the "XSD 1.1 feature issues" have
been discussed several times--this was one public disclosure:
https://groups.yahoo.com/neo/groups/dita-users/conversations/topics/16445
Don R. Day
Co-Founder, ContelligenceGroup.com
Founding Chair, OASIS
DITA Technical Committee
LinkedIn: donrday Twitter:
@donrday
About.me: Don R. Day Skype:
don.r.day
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
On 7/8/2014 9:43 AM, Don R Day wrote:
Last week we started discussing the emerging dark reality of XSD's
inability to handle constraints without direct editing, which
mungles the DITA design pattern. So I'm reiterating many past
discussions by suggesting that it's time to add a small statement
into the spec that, besides moving to RNC as the normative
declaration of ongoing DITA design patterns, that we add a new
disclaimer that summarizes our past difficulties with XSD features
needed for DITA (the XSD 1.1 feature issues need to be logged for
historical reasons) and clarifying how to amend/create a one-off
XSD instance that represents modifications that normally would be
supported by RNC/DTD rules. I think we discussed this last week,
but I hope we can get to disposition this week.
--
Don R. Day
Co-Founder, ContelligenceGroup.com
Founding Chair, OASIS
DITA Technical Committee
LinkedIn: donrday Twitter:
@donrday
About.me: Don R. Day Skype:
don.r.day
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
--
Don R. Day
Co-Founder, ContelligenceGroup.com
Founding Chair, OASIS
DITA Technical Committee
LinkedIn: donrday Twitter:
@donrday
About.me: Don R. Day Skype:
don.r.day
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
