[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: FW: [legalxml-econtracts] grammatical paras necessary for "linking and retrieval mechanisms"?
>for the record, i still don't see why its a "good thing". it might be, >but its certainly not clear. it has some advantages, but the costs are >considerable in terms of ease of authoring. the jury is still out on this. Jason. Actually, I think the opposite. Ease of authoring is improved by restricting the choices pertinent to key moments during content entry. In a separate note, I proposed a strict XHTML 2.0 application that does not allow lists, tables, or images within the <section> element. A <section> requires an <h> element, and any combination of <p> and <section> elements -- just TWO CHOICES for the user to ponder at that key moment. [In the SP model, once a <section> has been entered, it seems the user then chooses among <section>, <p>, <table>, <image>, list elements, and (maybe) inline elements -- to this reader that would be more confusing to an unenthusiastic author]. Under strict XHTML 2.0, only within the <p> element would there be access to list, inline, image, and table elements. A section is nothing but a captioned container for grammatical paragraphs and or subsections. A paragraph is nothing but an uncaptioned container for text and graphic content, whether represented as flowing content, tabular content, list content, or image content. Your beef seems to be that an author cannot slide almost imperceptibly between <section> and <ol> element entry, nor between inline enumeration and a block list entry -- these 2 items underlie your concern about "ease of authoring". By interjecting that <ol> elements must reside within a <p>, then the author's desire or mistake of using <ol> rather than a <section> is completely extinguished. Insofar as block list vs enumerations, I believe not only are these two items conceptually divergent (though they share the display behavior of automatic numbering), but that that infrequent need is met more appropriately by applications as they solve more general copy/paste problems; it is suboptimal to address this issue in the markup language. Anyway, the <p> element is the container for text, images, lists, and tables within the section, so of course it's an item that's going to be referenced by people and by software, for any of the reasons I've mentioned (linking, display, libraries, metadata). Thanks, John
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]