Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoding of ordered lists #2683

Open
rettinghaus opened this issue Feb 15, 2025 · 7 comments
Open

Encoding of ordered lists #2683

rettinghaus opened this issue Feb 15, 2025 · 7 comments

Comments

@rettinghaus
Copy link
Contributor

There seems to be an inconsitency with the encoding of ordered lists. Most are using @rend="numbered", a few @rend="ordered".

What I get from this dated discussion it should be ordered, but couldn't figure out, what the preferred encoding within the Guidelines should be nowadays.

The Stylesheets use list type="ordered" for converting to TEI.

@hcayless
Copy link
Member

My own contention is that all lists are ordered and cannot be otherwise, so to label them as such is silly. But opinions may vary.

@lb42
Copy link
Member

lb42 commented Feb 15, 2025

Hughs contention would be more persuasive if tei offered any way of explicitly encoding unordered aggregates of items. But it doesnt....

@hcayless
Copy link
Member

An item in TEI is defined as a component of a list, so that might be a reason why it doesn't. If you need one, we could create an itemGrp, I suppose. "Unordered" as in HTML ul tags or old-style TEI list @types means "not numbered". They still have an order. They can't help it.

@jamescummings
Copy link
Member

My recollection is that our previous discussion concluded that it wasn't really about whether the items were in an order (as Hugh says they obviously are) but whether that order mattered to the encoder or whether they only put them in that order because one must to encode them as a list.

@lb42
Copy link
Member

lb42 commented Feb 16, 2025

So long As rhe guidelinese are expressed in something like xml, its obviously true that the order of any series of child elements is determined. We do however already provide an @org attribute for encoders wishing to override this behaviour. See its definitions on att.divLike and vColl . Maybe adding list to the att.divLike class would be a good idea?

@cthomasdta
Copy link

Quick question to understand the direction of the discussion, Klaus @rettinghaus

There seems to be an inconsitency with the encoding of ordered lists. Most are using @rend="numbered", a few @rend="ordered".

Does your initial observation include an objection against using @rend="numbered", e.g. for lists that are explicitly numbered (instead of e.g. bulleted) in the manuscript transcribed?

Or are you and is everybody else fine with (most) people using @rend="numbered" (and @rend="bulleted" etc.), and are only wondering if the value "ordered" is reasonable and makes sense for <list>s?

@rettinghaus
Copy link
Contributor Author

I'm a little surprised at the direction the discussion on this simple question has taken. I apologise if I have not made myself clear.
@rend="numbered" explicitly states that every item carries a number, while from my point of view @rend="ordered" only implies it. (Looking at this from the HTML perspective you may come to another conclusion.)
So my original question pointed to the @rend="ordered" still used in AB-About.xml. All other cases use @rend="numbered", and I was just wondering if this should be unified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants