On Fri, Mar 4, 2016 at 11:24 AM, James Cummings wrote:

We're only calling it cssClass because that is its most likely usage. I'm agnostic as to whether it would be beneficial to generalise that name (and all the good ones are taken...)

If it's supposed to be more generic / implementation agnostic, should it be called differently? Maybe styleClass? Raff

b) You don't say which HTML you are on about. It is a cssClass which is made available to the processing implementation which it can choose to use or not. In your bootstrap example, my processing implementation can choose to ignore or rename those classes to something completely different on multiple elements or none.

My 2 pence,

-James

On 04/03/16 13:35, Lou Burnard wrote:

...

Does it make any sense at all to use @cssClass on a processing model which is not going to produce HTML? I assume not, since sfaik a CSS class has to be specified on an HTML element. But suppose that my processing generates several different HTML elements for a single TEI element. How do I say which HTML element I am on about?

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

I strongly suspect that most (wo)man hours in this project were spent on naming issues and, as Lou's remark proves, we were still not very successful. Are there some guidelines/conventions for naming things in TEI at all, that could perhaps guide our choice here? On 5 March 2016 at 18:04, Lou Burnard wrote:

Many of the names for procmoddy things are pretty indefensible, starting with "model" itself which means something quite different elsewhere in the TEI. In the case of cssClass, if we dont want to implicitly limit it to CSS, then using some other kind of "class" is only going to confuse things even more -- we already have two varieties of class in the TEI and we really don't need a third. I'd prefer to stick with cssClass until someone proves to me that they have a real use case for something else, at which point I will suggest "label".

On 04/03/16 16:39, Raffaele Viglianti wrote:

...

On Fri, Mar 4, 2016 at 11:24 AM, James Cummings < James.Cummings@it.ox.ac.uk> wrote:

We're only calling it cssClass because that is its most likely usage.

...

I'm agnostic as to whether it would be beneficial to generalise that name (and all the good ones are taken...)

If it's supposed to be more generic / implementation agnostic, should it be called differently? Maybe styleClass?

Raff

b) You don't say which HTML you are on about. It is a cssClass which is

...

made available to the processing implementation which it can choose to use or not. In your bootstrap example, my processing implementation can choose to ignore or rename those classes to something completely different on multiple elements or none.

My 2 pence,

-James

On 04/03/16 13:35, Lou Burnard wrote:

Does it make any sense at all to use @cssClass on a processing model

...

which is not going to produce HTML? I assume not, since sfaik a CSS class has to be specified on an HTML element. But suppose that my processing generates several different HTML elements for a single TEI element. How do I say which HTML element I am on about?

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived