January 9, 2017
- Kevin S. Hawkins
- Elli Mylonas
- Syd Bauman
Elli said she finished it and the related issue 31 this morning but that we should discuss when we get to issue 31.
Syd said that this morning he finally got the build process fixed and can now move forward with this.
Elli explained that the last comment on the issue is the only one to consult. We discussed the suggested values for `@type` and agreed to include all of them in the prose and in the ODDs for levels 2-4 except:
We also agreed to add "foreword" and change "bibliogr" to "bibliography".
Kevin said he'd take over the issue to finish implementation.
Before discussing the issue, Syd said that he thought we should create a new issue for updating the ODDs to use Pure ODD syntax. After some discusion, Kevin agreed but suggested that it be added to the "Postpone" category in the BP revision ticket triage. Syd asked him to create the issue and assign it to him.
Syd said that now that a new version of P5 has been released, he would return to this issue.
Syd confirmed that this is still on his list.
Kevin said this was still on his list.
Syd said he recalled implementing this but would need to check. He agreed to do so.
Kevin said he would nudge his colleague again.
Elli confirmed that this is still on her list.
Elli said she would review what Kevin wrote.
After briefly reviewing, we accepted Kevin's proposed solution. He said he would implement.
We discussed the issue and agreed to:
- Add a row to the table of header elements for `<schemaRef>` (a child of `<editorialDec>`). For this element, say that you should use syntax like `key="BPTL-L3-v3.1.0"` to record that you are following a certain level of encoding in a certain version of the BPTL. You can also use `@url` to point to your own schema, whether a copy of one that follows the the BPTL exactly or a local customization.
- Remove the discussion of using `@n` on `<editorialDecl>`.
Elli will still implement.
Elli summarized her latest comment on the issue, but Kevin responded that currently <pb/> is discussed in the element recommendations for Level 1, and <lb/> and <cb/> are discussed in the element recommendations for Level 3.
Elli said that she then thinks that everything is set with this issue and issue 21, but she asked Kevin to check over the changes that she committed.
Kevin asked whether we should hold our next meeting on the first or second Monday of the month. Since the Technical Council will have a face-to-face meeting the first week of February, we decided to meet next on Feb. 13. Kevin said he would announce this to teilib-l.