RE: [dita] attribute extensibility - summary

["Grosso, Paul" <pgrosso@ptc.com>]

At this juncture, I have what I hope is a simple question.

I understand that users want to be able to conditionalize
on new attributes and new values, and I understand that
it would be optimal to be able to author those attributes
and values directly into the content.

But for a moment, lets assume there is a transformation
from this optimal markup into one that merely uses our
existing support for otherprops to "encode" the conditional
attribute information using DITA 1.0.1 markup.  We can even
assume a reverse transformation on the other side so that
end users can work in the "augmented conditional attribute"
markup, but the actual preserved markup just uses otherprops.

Is there any underlying conditional processing functionality
that could not be made available to DITA users in this scenario?

paul