ZedAI ContentModel Issues

From zedwiki

Jump to: navigation, search

Contents

Elements

section

What about epigraphs, quotes, images, etc. that occur before the heading? Markus: this is allowed as far as I can tell. What exact version of section are you referring to (which profile, which context)?

section

The section content model is unnecessarily complex.

Deal with this at a later stage.

list

list semantics are unclear - what does it mean when @type isn't provided?

@markus: remove inline list (leave the define in the rng, but dont contribute it to Phrase.class) DONE

@markus: add after:"... by numeric values." → If the type attribute is absent, then there is no default formatting. DONE

article

Doesn't appear in schemadoc. Not yet included? Markus: not in book schema by intent.

bibliography

biblio sections may be entirely prose (esp. when talking about web sites consulted). Currently not allowed.

bodymatter

Braille volumes normally include the book title at the start of the body content (even when a frontmatter proceeds). An optional h tag may be useful.

Markus: Matt advises us to look at this as a Braille post process thing.

cover

Do we need to specify the order of the children, or should they be &'ed?

Markus: keep as is.

frontcover/backcover/flaps

Previously mentioned case about standard use for section/block would apply here. An author bio on the covers has to be a block but in the content would be a section.

Without section allowed there's no way to define outside/inside for covers.

table of contents

Confusing right now what label is for (i.e., only the line that corresponds with the leader). More a documentation issue.

@Matt change TOC entry content model to: {Phrase.model, block?, entry*}

@Matt explain blocks auxilliary nature in the doc of entry instead of creating a variant of block.

lngroup

I just hate this name in verse. It should be stanza. But can leave for a specialized module.

Markus: note that a term like stanza isn't necessarily good to force here (other terms are used in traditional japanese, persian, etc meters).

Markus: as we already have Issue 28, I am delling this one out.

aside

Requires h? They can be documents within documents.

@Markus note as an issue in the tracker DONE

caption/citation

Are we being inconsistent in having block and phrase captions but only phrase citations?

@Matt: remove phrase caption

@Matt: add block citation to Block.core.class

note

Lists rend.prefix in its content model but doesn't require the rend feature as a dependency? Markus: fixed. note.rend.prefix is now contributed from the feature.

annotation

Should be allowed in head, just like definition and expansion, to allow adding annos that are not part of the document content

@Markus add annotation to head

sel:select for repeated content

Especially in the case of content that is repeated, the current content selection feature is very verbose. By adding a sel:select attribute (IDREF) and allowing <sel:select> in head, we allow the reuse of selection clauses.

Example:

<del>body: 

<p>I <char sel:select=”sym_001”>♥</char> NY</p>

head: 

 <sel:select id="sym_001">
	<sel:when test="outputformat(BRAILLE)">**</sel:when>
	<sel:otherwise>♥</sel:otherwise>
 </sel:select>

Note that the symbol appears in both places here; could perhaps be done other ways, but the idea would be to have the body symbol be on body primarily in order to provide a fallback for PAs that dont support the content selection feature (and generally, to keep the document content "intact").

Markus: wait with this, maybe revisit later

pagebreak

Should @value be required? Thinking there may be instances where only the marker is required without explicitly setting a value for it. Markus: agree, made it optional.


rend:indent

The prose for @rend:intent does not reserve a value to use for "no indent" as suggested in http://code.google.com/p/zednext/issues/detail?id=126#c2.

(Also, @rend:indent defines its own datatype locally, these should per convention be in Datatypes.rng (CSS.length-unit.datatype))


  • @Matt highlight the boolean-ness as a second sentence "To enable use in non-CSS-aware environments (such as certain Braille processors), two values are reserved to mean zero indent..."
  • @Matt Drop ex, em and px remain
  • @Matt restrict value to zero or positive (negative values for em and px not allowed)

rend:prefix

the item and note rend contribs do not include the possibility to reference an image (compare separator)

Markus: ignore this for now: real CSS can be used where this is needed.

colgroup

currently requires at least one child col

The content model is: a choice of either @span or one or more of col

char

@Matt add to schemas, and a snippet with the gothic example

Retrieved from "http://www.daisy.org/zw/ZedAI_ContentModel_Issues"
Personal tools