Fmt IAB session, Tue 23 Jul 14

* The requirements drafts
Julian: xmlv2 draft
Paul:   xmlv3 draft
Joe:    html draft
Nevil:  SVG draft
Tony:   PDF draft
  Larry Masinter asks for feedback
Heather: plain text
  Wants feedback on requirements not already considered
  Microsoft guy: ASCII or UTF-8?  A: UFT-8
Heather: non-ASCII characters
  the html version (on tools page) is the best one to look at
  Need to also write a 'road map' draft  (Geoff?)

* Timeline
Up to IETF 91 (Honolulu)  SoWs out for review
The RFPs, development of tools, testing

Marc?  What kind of testing before go-live
Joe H: Need a wiki to track test plans
Marc:  Lots of people with different work habits will be affected.
       Need feedback from them before we go live.
Larry Masinter: PDF fmts - still lots of open format questions
  Freeze xml, then (slowly) others, before going fully live.
Joe H: Good idea, announce as beta versions?
Julian agrees.  Keep 'test version' docs until things get frozen
Larry: Wait before announcing "the final version of pdf"
       likes staggering "final date" for all o/p formats
Paul H: It's fine to regenerate the non-canonical formats
Robert S: Confirms that the design drafts won't be published until
       we're actually running.  But we need a well-defined community
       comment period before we start coding tools
Joe H: regenerating RFCs?  but when?  want to minimise this
John L: we have little experience with non-text formats.  Need to
        set policy on how stable the non-canonical versions are
H: Lots of communities - authors, implementors, lawyers, archivists, ...
   We're not in too much of a hurry
Paul H: he & Julian are working on a draft showing how to produce xml,
        and what it will look at in html - an 'examples' draft
Jeff Hodges:  Lawyers?  H will write something explaining what aspects concern them

* Pub formats
html and pdf won't look like the plain text format
Larry: pdf locks down the styling
Paul H: hmtl doc says o/p html will have a default CSS embedded in it,
     	you can replace it n your system if you want to
??      problem is that some folk will want a different shade of blue (!)

* Preliminary CSS feedback needed
Marc:  Don't talk about what you like, or how it looks.
       Get a good designer to do it.  But Marc has Pretty RFC format
IAB guy ;  Wants ePub and read it aloud capability.  Would each of
   the styles be the same when read aloud?
Larry: bikeshedding - consider having a contest and letting people 
       vote for the most popular.
Marc:  target audience should be people who are NOT at IETF!
       murmurs of support
Sean:  html/css concern: reflowable text seems a common feature.
       I need more control over line-breaks and word-wrap
       Happy to post one or two of those drafts on rfc-i
Joe Hodges?  Need to frame this discussion as requirements.
       H agrees, her examples are intended to elicit those requirements.
       A list of questions about requirements would help
Julian: text and CSS - rules for text readers.  
Joe H:  Example of need for override - wouldn't want reader to do 
        ASCII art diagrams.
Julian: Keep 'classic' look and feel, or shuffle things around?
	For Shuan: white space in paragraph is a new requirement
Larry question about spanx - element in v2, but bad - combines white-space
      and layout
Eric Burger (jabber) asks 'will people read the xml directly using a
     style sheet?'  Not considered yet.
     Response to Marc.  Conflict in response to design is good.
     We need to find out what the community thinks is interesting
Julian: (I didn't understand his comment)

* Continue discussion on rfc-i