Hi Lou,
Only that it is a change that has been approved for quite awhile and been waiting to be implemented. Since source was an existing attribute there isn't much prose to add and I can do so today.
James
--
Dr James Cummings, Academic IT Services, University of Oxford
On 27 Nov 2016 09:49, Lou Burnard wrote:
Why is this release blocking? We have been getting along quite well without a global @source for ages. Seems to me that if the prose isn't written and the testing hasn't been done then this isn't going to be ready for the next release. No big deal imho.
Sent from my Honor Mobile
-------- Original Message --------
Subject: [tei-council] att.global.source branch for issue #536
From: James Cummings
To: TEI Council
CC:
Hiya,
I believe I've done the schema-related changes for
release-blocking issue #536 (there are still bits of prose to
change). Since this was adding a @source attribute in a new
global class I did the various changes in a branch. I've not done
anything about the testing which I'm sure the changes to classes
(att.source and att.readFrom) will break. (But then again, I've
never understood the testing and expected results as well as I
should.) I'd appreciate someone looking at the changes and seeing
if you see anything I've forgotten to do (other than prose
updates in the chapters), and also to give me some advice on
merging the branch in (or go ahead and do it if it looks good)
and/or fixing the needed tests.
See most recent change at
https://github.com/TEIC/TEI/tree/att.global.source namely
https://github.com/TEIC/TEI/commit/69d00eb5b1f762eded61ad836a723c4ad0e4bc5d
This changes 37 files with 96 additions and 119 deletions github
tells me.
-James
--
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
