search

TEIC / TEI-Simple

Legacy Repository: TEI SimplePrint now merged into TEI Repository. Originally TEI Simple aimed to define a new highly-constrained and prescriptive subset of the Text Encoding Initiative (TEI) Guidelines suited to the representation of early modern and modern books, a formally-defined set of processing model rules that enable web applications to easily present and analyze the encoded texts, mapping to other ontologies, and processes to describe the encoding status and richness of a TEI digital text.
50 stars 12 forks source link

Why `<gi>` and `<att>` but not `<val>`? #19

Closed martindholmes closed 9 years ago

martindholmes commented 9 years ago

I could understand Simple not having any of these three elements, but to have two and not the third seems strange; is there a reason for it? I typically use all three when documenting encoding practices.

sydb commented 9 years ago

It does seem a bit disorganized. I typically use all four (,

, , and ) or none. > I could understand Simple not having any of these three elements, > but to have two and not the third seems strange; is there a reason > for it? I typically use all three when documenting encoding > practices.
lb42 commented 9 years ago

I cannot see any justification for having any of them in simple, unless there has been some mission creep...

martindholmes commented 9 years ago

I think you'd use them in encodingDesc, and Simple's approach has been (I think) largely to leave the header alone. Paul is right, though: <tag> is missing too.

martinmueller39 commented 9 years ago

That seems right to me.

From: Martin Holmes notifications@github.com<mailto:notifications@github.com> Reply-To: TEIC/TEI-Simple reply@reply.github.com<mailto:reply@reply.github.com> Date: Thursday, June 4, 2015 at 5:17 PM To: TEIC/TEI-Simple TEI-Simple@noreply.github.com<mailto:TEI-Simple@noreply.github.com> Subject: [TEI-Simple] Why <gi> and <att> but not <val>? (#19)

I could understand Simple not having any of these three elements, but to have two and not the third seems strange; is there a reason for it? I typically use all three when documenting encoding practices.

Reply to this email directly or view it on GitHubhttps://github.com/TEIC/TEI-Simple/issues/19.

sebastianrahtz commented 9 years ago

I will add these extras to the list of elements only allowed in the header