There were some other people who had built things on top of it.... I don't remember what though. I remember us getting some questions about it at some point though. What are the kinds of changes you want to make? As long as not drastic then I don't see why not. We don't claim it is a perfect serialization to JSON. π
Best wishes,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________
From: tei-council-bounces@lists.tei-c.org
I do not know what, if anything else, reads it. (In fact, I didn't realize Byzantium did.) But my instinct is to change change said XSLT in a branch (or some other way it's easy to revert), and don't worry about it until if & when there's a problem. JC> There were some other people who had built things on top of JC> it.... I don't remember what though. I remember us getting some JC> questions about it at some point though. What are the kinds of JC> changes you want to make? As long as not drastic then I don't see JC> why not. We don't claim it is a perfect serialization to JSON. π RV> Does anyone know if p5subset.json is used for anything except RV> Byzantium at the moment? In short, can I change the XSLT that RV> generates it as I please?
Most changes would bring in more data, so I wouldn't worry about those, but others would be drastic. For example, elementSpec allows for multiple desc and gloss elements, but p5subset only carries over one of each -- I assume the first, and therefore in English. Changes would be needed to deal with multiple languages. I'm also considering storing some XML as string in order to allow people to edit prose content (e.g. of desc) as XML in RomaJS (eventually). The json gets built at every release and stored on the Vault; I'm counting on being able to retrieve that file from RomaJS, so changing the XSLT on a branch won't do. Making changes also means that RomaJS won't be able to change older versions of TEI with an outdated p5subset.json, but I don't think that's a huge deal: it strikes me as an advanced use that the UI doesn't need to support. On Thu, Sep 28, 2017 at 11:50 AM, James Cummings < James.Cummings@newcastle.ac.uk> wrote:
There were some other people who had built things on top of it.... I don't remember what though. I remember us getting some questions about it at some point though. What are the kinds of changes you want to make? As long as not drastic then I don't see why not. We don't claim it is a perfect serialization to JSON. π
Best wishes,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________ From: tei-council-bounces@lists.tei-c.org
on behalf of Raffaele Viglianti Sent: 28 September 2017 16:16:45 To: tei-council@lists.tei-c.org Subject: [tei-council] p5subset.json Hi all,
Does anyone know if p5subset.json is used for anything except Byzantium at the moment? In short, can I change the XSLT that generates it as I please?
Raff -- 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
I honestly donβt think we should worry about it too much. I know of only one project besides Byzantium that used it, and I was part of it, and itβs dead. :-) I think having a more expressive JSON representation would be very useful. Hugh
On Sep 28, 2017, at 12:07 , Raffaele Viglianti
wrote: Most changes would bring in more data, so I wouldn't worry about those, but others would be drastic. For example, elementSpec allows for multiple desc and gloss elements, but p5subset only carries over one of each -- I assume the first, and therefore in English. Changes would be needed to deal with multiple languages. I'm also considering storing some XML as string in order to allow people to edit prose content (e.g. of desc) as XML in RomaJS (eventually).
The json gets built at every release and stored on the Vault; I'm counting on being able to retrieve that file from RomaJS, so changing the XSLT on a branch won't do. Making changes also means that RomaJS won't be able to change older versions of TEI with an outdated p5subset.json, but I don't think that's a huge deal: it strikes me as an advanced use that the UI doesn't need to support.
On Thu, Sep 28, 2017 at 11:50 AM, James Cummings < James.Cummings@newcastle.ac.uk> wrote:
There were some other people who had built things on top of it.... I don't remember what though. I remember us getting some questions about it at some point though. What are the kinds of changes you want to make? As long as not drastic then I don't see why not. We don't claim it is a perfect serialization to JSON. π
Best wishes,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
School of English Literature, Language, and Linguistics, Newcastle University
________________________________ From: tei-council-bounces@lists.tei-c.org
on behalf of Raffaele Viglianti Sent: 28 September 2017 16:16:45 To: tei-council@lists.tei-c.org Subject: [tei-council] p5subset.json Hi all,
Does anyone know if p5subset.json is used for anything except Byzantium at the moment? In short, can I change the XSLT that generates it as I please?
Raff -- 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 -- 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
participants (4)
-
Hugh Cayless
-
James Cummings
-
Raffaele Viglianti
-
Syd Bauman