Sorry, hit "send" before I was even done writing, let alone editing, that. Martina -- I don't know if you created a 7.45, 7.46, or 7.47 milestone. You may need to tweak the GiHub milestones or the e-mail to fit.

Dear all, I have added a comment on the doc two days ago. However, it needs further explanations: I have looked to TEI council profiles; from what I understood, you have a lot of knowledge in encoding, more than a lot of digital practitioners who use TEI (and other encoding languages needed to work with TEI) mostly for their investigation in a text/corpus/artefact. This is my case: I use TEI and other languages because I need these tools for investigating my corpus. By saying this, I have not the same background/knowledge (and goal) than most of you. Thus, if you agree, my first remarks will rather be (at least for now) to make sure than beginners or digital practitioners (but no experts in programming languages) will be able to understand not only encoding but also how it can help them to improve their research. In addition, I think we need to take advantage of each opportunity for doing a little pedagogy and the Stylesheets released is a good opportunity. When you did the release of the Guidelines http://www.tei-c.org/release/doc/tei-p5-doc/readme-3.1.0.html (thanks James), you tried to give a few helpful information—although we can always be improved. As for this Stylesheets release, I think we need to give further information regarding the issues resolved--not for all topics since a few of them will not be as much interest for beginners or average level. For example, something like: “Among other issues resolved in the last stylesheets v7.46.0 released: - In order to avoid a schematron [link] processor (in other words rule-based validation language) error regarding @ageAtDeath [link], rather used teidata.count [link] attribute group instead of teidana.numeric [link] (https://github.com/TEIC/Stylesheets/issues/322)”--I don’t know if it was updated on TEI website, but if this is the case, also add the TEI link updated. - …” However, we need to ask ourselves the following question: how the issues resolved can be helpful to beginner and average level practitioners, in order to choose the issues which need more information. Lastly, I’m not convince all readers will understand what is “stylesheets released.” —maybe under bracket something like “improvements according to issues resolved.” I suggest that the message has two sections: one for experts and one for beginners and average levels practitioners. Hope my explanation is clear enough… and that I’m not getting wrong in TEI council goals. Best, Vanessa Le 30 sept. 2018 à 17:19, Scholger, Martina (martina.scholger@uni-graz.atmailto:martina.scholger@uni-graz.at) mailto:martina.scholger@uni-graz.at> a écrit : Ah, thanks. Changed the milestone to 7.46 in Github. Best, Martina -----Ursprüngliche Nachricht----- Von: Tei-council mailto:tei-council-bounces@lists.tei-c.org> Im Auftrag von Syd Bauman Gesendet: Samstag, 29. September 2018 21:56 An: tei-council@lists.tei-c.orgmailto:tei-council@lists.tei-c.org; Martin Holmes mailto:mholmes@uvic.ca> Betreff: Re: [Tei-council] Stylesheets v7.46.0 released Sorry, hit "send" before I was even done writing, let alone editing, that. Martina -- I don't know if you created a 7.45, 7.46, or 7.47 milestone. You may need to tweak the GiHub milestones or the e-mail to fit. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.orgmailto:Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

I added a couple paragraphs to the document, let me know what you think. This conversation we're having echos the worry I expressed in my first email:

I don't know if stylesheets releases need to be announced on TEI-L, especially since we don't assemble a document listing changes besides a generated changelog.

Perhaps the paragraph I added are enough, but it's easy to go down a rabbit hole. The Stylesheets are important, but it's still unclear how much of a responsibility council has towards them since our primary goal is maintaining and improving the TEI Guidelines. All best, Raff On Tue, Oct 2, 2018 at 8:18 AM Peter Stadler wrote:

I agree that the current draft is not very helpful except for saying "there is a new release“. We should add a) the main motivation. It is unusual that we are doing a Stylesheets release out of sync with the Guidelines. AFAIK, the main motivation is Raff’s work on RomaJS and his need for p5subset.json, leading to various changes to odd2json.xsl in the Stylesheets repo. That need to be mentioned. @raff: could you elaborate a little bit on those changes? what’s different now in the resulting p5subset.json? (and what’s the difference to p5subset.js?) b) nothing more. The rest is indeed technical stuff and won’t improve any research.

Best Peter

...

Am 02.10.2018 um 13:01 schrieb Vanessa Bigot-Juloux < vanessa.bigot-juloux@ephe.psl.eu>:

Dear all,

I have added a comment on the doc two days ago. However, it needs further explanations: I have looked to TEI council profiles; from what I understood, you have a lot of knowledge in encoding, more than a lot of digital practitioners who use TEI (and other encoding languages needed to work with TEI) mostly for their investigation in a text/corpus/artefact. This is my case: I use TEI and other languages because I need these tools for investigating my corpus. By saying this, I have not the same background/knowledge (and goal) than most of you. Thus, if you agree, my first remarks will rather be (at least for now) to make sure than beginners or digital practitioners (but no experts in programming languages) will be able to understand not only encoding but also how it can help them to improve their research. In addition, I think we need to take advantage of each opportunity for doing a little pedagogy and the Stylesheets released is a good opportunity. When you did the release of the Guidelines http://www.tei-c.org/release/doc/tei-p5-doc/readme-3.1.0.html (thanks James), you tried to give a few helpful information—although we can always be improved. As for this Stylesheets release, I think we need to give further information regarding the issues resolved--not for all topics since a few of them will not be as much interest for beginners or average level. For example, something like: “Among other issues resolved in the last stylesheets v7.46.0 released: - In order to avoid a schematron [link] processor (in other words rule-based validation language) error regarding @ageAtDeath [link], rather used teidata.count [link] attribute group instead of teidana.numeric [link] (https://github.com/TEIC/Stylesheets/issues/322)”--I don’t know if it was updated on TEI website, but if this is the case, also add the TEI link updated. - …”

However, we need to ask ourselves the following question: how the issues resolved can be helpful to beginner and average level practitioners, in order to choose the issues which need more information. Lastly, I’m not convince all readers will understand what is “stylesheets released.” —maybe under bracket something like “improvements according to issues resolved.”

I suggest that the message has two sections: one for experts and one for beginners and average levels practitioners.

Hope my explanation is clear enough… and that I’m not getting wrong in TEI council goals.

Best, Vanessa

...

Le 30 sept. 2018 à 17:19, Scholger, Martina ( martina.scholger@uni-graz.at) a écrit :

Ah, thanks. Changed the milestone to 7.46 in Github.

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Syd Bauman Gesendet: Samstag, 29. September 2018 21:56 An: tei-council@lists.tei-c.org; Martin Holmes Betreff: Re: [Tei-council] Stylesheets v7.46.0 released

Sorry, hit "send" before I was even done writing, let alone editing, that.

Martina -- I don't know if you created a 7.45, 7.46, or 7.47 milestone. You may need to tweak the GiHub milestones or the e-mail to fit. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

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

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