Re: [dita] Re: Discuss list processing expectations

["Gershon L Joseph \[Yahoo\]" <gljoseph@yahoo.com>]

var YAHOO = {'Shortcuts' : {}};
YAHOO.Shortcuts.hasSensitiveText = false;
YAHOO.Shortcuts.sensitivityType = [];
YAHOO.Shortcuts.doUlt = false;
YAHOO.Shortcuts.location = "us";
YAHOO.Shortcuts.document_id = 0;
YAHOO.Shortcuts.document_type = "";
YAHOO.Shortcuts.document_title = "Re: [dita] Re: Discuss list processing expectations";
YAHOO.Shortcuts.document_publish_date = "";
YAHOO.Shortcuts.document_author = "gershon.joseph@tech-tav.com";
YAHOO.Shortcuts.document_url = "";
YAHOO.Shortcuts.document_tags = "";
YAHOO.Shortcuts.annotationSet = {
"lw_1207668561_0": {
"text": "robander@us.ibm.com",
"extended": 0,
"startchar": 1489,
"endchar": 1507,
"start": 1489,
"end": 1507,
"extendedFrom": "",
"predictedCategory": "",
"predictionProbability": "0",
"weight": 1,
"type": ["shortcuts:/us/instance/identifier/hyperlink/mailto"],
"category": ["IDENTIFIER"],
"context": "against the spec.   Gershon   ----- Original Message ---- \x3e From: Robert D Anderson \x3crobander@us.ibm.com\x3e \x3e To: DITA TC List \x3cdita@lists.oasis-open.org\x3e \x3e Sent: Tuesday, April 8, 2008",
"metaData": {
"linkHref": "mailto:robander@us.ibm.com";,
"linkProtocol": "mailto",
"linkYmailto": "mailto:robander@us.ibm.com";
}
 },
"lw_1207668561_1": {
"text": "dita@lists.oasis-open.org",
"extended": 0,
"startchar": 1632,
"endchar": 1656,
"start": 1632,
"end": 1656,
"extendedFrom": "",
"predictedCategory": "",
"predictionProbability": "0",
"weight": 1,
"type": ["shortcuts:/us/instance/identifier/hyperlink/mailto"],
"category": ["IDENTIFIER"],
"context": "Message ---- \x3e From: Robert D Anderson \x3crobander@us.ibm.com\x3e \x3e To: DITA TC List \x3cdita@lists.oasis-open.org\x3e \x3e Sent: Tuesday, April 8, 2008 5:18:01 PM \x3e Subject: RE: [dita",
"metaData": {
"linkHref": "mailto:dita@lists.oasis-open.org";,
"linkProtocol": "mailto",
"linkYmailto": "mailto:dita@lists.oasis-open.org";
}
 },
"lw_1207668561_2": {
"text": "Tuesday, April 8, 2008 5:18:01 PM",
"extended": 0,
"startchar": 1680,
"endchar": 1712,
"start": 1680,
"end": 1712,
"extendedFrom": "",
"predictedCategory": "",
"predictionProbability": "0",
"weight": 1,
"type": ["shortcuts:/us/instance/identifier/date_time"],
"category": ["IDENTIFIER"],
"context": "Robert D Anderson \x3crobander@us.ibm.com\x3e \x3e To: DITA TC List \x3cdita@lists.oasis-open.org\x3e \x3e Sent: Tuesday, April 8, 2008 5:18:01 PM \x3e Subject: RE: [dita] Re: Discuss list processing expectations \x3e  \x3e I\x27d second",
"metaData": {
"isoEndDate": "",
"isoStartDate": "20080408T171801",
"past": "false",
"recurring": "false"
}
 }
};
I'm still against using the same element in both block and inlinecontexts. If DITA provided an <inline-ul> (or whatever) for usein the example Paul gave I'd be OK with it. I still feel that blockelements should be used only in block contexts, and inline elements ininline contexts. Paul's example would then be marked up as follows:

<p>In order to install Acme Pro Plus Plus, your system must
meet the following requirements:
<inline-ul>
  <li>Pentium 4 CPU or later</li>
   <li>1 GB RAM or more</li>
   <li>At least 350 MB free disk space</li>
 </inline-ul>
 unless you are running the Limited version of the product.
 </p>

Obviouslywe're not going to change the DTDs for 1.2, but perhaps we couldconsider an inline unordered list element for a future release, when wecan improve on the current situation where <ul> functions as bothblock and inline.

For 1.2, maybe we should provide Paul'sexample as an exception to the general rule, and maybe even state thata future DITA release may provide a different inline element for thispurpose?

Note also I said the spec should encourage the bestpractice via "should", so users using mixed markup are not goingagainst the spec.
 
Gershon


----- Original Message ----
> From: Robert D Anderson <robander@us.ibm.com>
> To: DITA TC List <dita@lists.oasis-open.org>
> Sent: Tuesday, April 8, 2008 5:18:01 PM
> Subject: RE: [dita] Re: Discuss list processing expectations
> 
> I'd second what Paul says - I know a lot of users who would get upset if
> the spec told them they could not include the samples Paul gives inside a
> single paragraph.