[tei-council] Fwd: [tei:feature-requests] #452 <group> should be a member of att.typed
Lou Burnard
lou.burnard at retired.ox.ac.uk
Wed Jun 19 11:33:43 EDT 2013
This seems uncontroversial, if a bit weird, to me. Someone like to agree
on the ticket so I can do it?
-------- Original Message --------
Subject: [tei:feature-requests] #452 <group> should be a member of
att.typed
Date: Wed, 19 Jun 2013 15:28:22 +0000
From: Lou Burnard <louburnard at users.sf.net>
Reply-To: [tei:feature-requests] <452 at feature-requests.tei.p.re.sf.net>
To: [tei:feature-requests] <452 at feature-requests.tei.p.re.sf.net>
Thanks for the example. I can see no logical reason why we shouldn't
allow @type on |<group>| in the same way as we do on |<text>| and
|<div|> . However, I am quite curious about the reasons that led you to
treat each chapter as a single text, rather than as a div. To my mind a
chapter is an incomplete object, whereas the definition (admittedly
rather vague) of a |<text>| suggests that it is complete in itself. I
don't know enough (or anything much!) about this material so I cannot
judge how pertinent that distinction is to your work. However, as
aforesaid, I see no problem in adding @type to |<group>|.
------------------------------------------------------------------------
*[feature-requests:#452]
<http://sourceforge.net/p/tei/feature-requests/452/> should be a member
of att.typed*
*Status:* open
*Created:* Fri Apr 19, 2013 11:56 AM UTC by Frederik
*Last Updated:* Wed Jun 19, 2013 12:51 PM UTC
*Owner:* nobody
When grouping texts, and especially with nested group hierarchies, it
would be helpful to assign a type to a group. If one regards <group> as
a means to create hierarchies of texts, just like <div> is a mean to
create hierarchies within texts, the same logic of distinguishing
hierarchical elements by a type applies.
------------------------------------------------------------------------
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/tei/feature-requests/452/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
More information about the tei-council
mailing list