Meeting minutes
Import script status
Editorial sections -- is there any help that's needed for the team to write them?
Zack: Wrote something. There is a pretty lengthy term we'll discuss shorthands for it
… We got those initial sections ready to get this PR landed
Zack: We started with a Google Doc and then I translated it into HTML
… I am hopeful that by the end of this week or early next week we could have this term
JamesC: What's the context of PDF thingy?
Zack: As we worked on this we put a placeholder for verbosity sake
… Paul and I have a meeting where we'll be proposing this to the PDF Association
… If we want this to land sooner I could search and replace
Val: Could you say PDF objects?
JamesC: Most readers will understand, but others may ont. I suggest adding "to be named" to make it obvious
… I would lean towards committing this. We can then separate smaller pieces. We can understand this is still ED, not even FPWD
Zack: I can accomplish this here this afternoon
… Later we can come back to convetrting our sheet rows into HTML tables
JamesC: We could do it today. I'll dismiss my blocking review
Daniel: I agree
Val: I am doing this right now
… But we sstill want the change from PDF thingy
JamesC: My comment about normative references in informative sections, is that resolved?
Zack: Yes.
JamesC: The cross-reference is not implemented to HTML and DPUB is not implemented yet
… You had your own mapping of document instead of the core-aam and html-aam
Daniel: Use the class defined per spec and in the href only use the id fragment
[[Work on the PR. Going through pending comments and opening them as separate issues]]
Daniel: #2466 has been merged