OASIS Darwin Information Typing Architecture (DITA) TC

1. In-line examples: There are some good in-line examples there -- it needs more. A sentence such as, "Such a reference is a reference to the document that contains the reference" needs to be read multiple times to recover sufficient context. A one-sentence or quick in-line example would help.
   
   
2. URI case sensitivity: It's probably worth a mention that some text segments in a URI are case-insensitive while IDs in those URIs are.
   
   
3. Fragility: I do believe that it is worth a mention that URI references are fragile, i.e. any change to any segment in the URI will invalidate the reference.       

Overall, it looks good. I've made a few comments below for consideration.

Conditional processing

https://dita-lang.org/dita/archspec/base/condproc

Both sentences start with "Conditional processing is.." can they be combined?

About conditional processing

https://dita-lang.org/dita/archspec/base/aboutconditionalprocessing

Suggest rewording short description – "Certain concepts are critical..."

Do we want to include information or a link to describe how to specialize conditional processing attributes?

Do we want to mention the commonly used term "profile attributes"?

About the DITAVAL document

https://dita-lang.org/dita/archspec/base/aboutditavaldocuments

Link to exclude all example (Example: Changing the default behavior to "exclude")?

Conditional processing attribute values

https://dita-lang.org/dita/archspec/base/usage-of-conditional-processing-attributes

Why product="" ? When would you use this empty value, versus just removing or not using the attribute?

Conditional processing and subject schemes

https://dita-lang.org/dita/archspec/base/conditional-processing-and-subject-schemes

Add information about how subject schemes can be used by some editors to prepopulate attribute values in drop down menu.

Link for more information?

Filtering based on metadata attributes

https://dita-lang.org/dita/archspec/base/filtering

Still unsure of the use case for product="" vs no attribute at all.

Do we want to include the logic of multiple attributes with multiple values? For example <p product="A B" audience="C">

Example: Setting conditional processing values

https://dita-lang.org/dita/archspec/base/example-setting-condproc-values

Would it be helpful to include different example ditavals and show what rendered output is for each?

Example: Simple DITAVAL document

https://dita-lang.org/dita/archspec/base/example-simple-ditaval

Link to exclude all example (Example: Changing the default behavior to "exclude")?

Example: Filtering and flagging topic content

https://dita-lang.org/dita/archspec/base/evaluating-conditional-processing-attributes

Based on the title I expected this to talk about topic level filtering at the topic root or topicref element.

Example: Simple DITAVAL document

https://dita-lang.org/dita/archspec/base/evaluating-conditional-processing-attributes

What is the purpose of the non-normative section? Why is it near the end of the list?

Thanks,

Leroy