LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  September 2007

TEI-L September 2007

Subject:

Re: encodingDesc inconsistency?

From:

Syd Bauman <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 17 Sep 2007 12:38:48 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (27 lines)

Good catch, Elena.

> Is the current state of the Guidelines/Schema as they are supposed
> to be or there is something wrong?

I can confidently say that something is wrong here, and that it will
be fixed in the next few weeks. What I can't say is whether it will
be fixed by changing the prose to describe the model of "any number
of any of these special elements in any order OR a sequence of
paragraphs", or the content model will be changed to more closely
match the prose (and what P4 had), which not only had the special
elements in a particular order, but also allowed both special
elements and paragraphs.


Personally, I lean towards changing the content model to

element encodingDesc {
   att.global.attributes,
   ( model.encodingPart_sequenceOptionalRepeatable, model.pLike* )
}

This would very closely match the kind of model P4 supported. The
main difference would be the addition of the new elements (<appInfo>,
<charDecl>, <geoDecl>, <ab>) and that <tagsDecl> would be repeatable,
whereas it wasn't in P4.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager