Minutes of small-group call about multimedia domain Present: Eliot Kimber, Carlos Evia, Chris Nitchie, Keith Schengili-Roberts, Mark Giffin (joined for last 5 minutes) We used Chris Nitchie's stage 2 proposal as the starting point for our discussion. Element names Chris outlined that he had name-spaced elements names, to avoid potential collisions. General agreement. Preference for hyphens Did we as a TC decide on conventions for element names moving forward? If so, we need to follow it. Discussion of <video> Leave <fallback> out of the early preview release . Add <fallback> to <object> for DITA 2.0 Add specializations of <param> for <autoplay>, <loop>, and <muted>. These are of authoring concern; the other HTML5 attributes are more focused on rendering concern. Discussion of <audio> Leave <fallback> out of the early preview release . Add <fallback> to <object> for DITA 2.0 Add specializations of <param> for <autoplay>, <loop>, and <muted>. These are of authoring concern; the other HTML5 attributes are more focused on rendering concern. There is no HTML5 @volume, so we don't need to deal with it. DITA implementations that use multimedia/people with strong interest Radu Coravu, SyncroSoft SAP? Dan Dan Ziagos at FICO presented at CMS/DITA NA about their interest in multimedia. Action items Kris: Find minutes where we discussed conventions for element names Chris: Update DTDs and proposal based on discussion; build DITA-OT plug-in Kris: Help Carlos with an update to the LwDITA committee note draft Everyone: Continue with discussion online between now and next TC meeting. How can we best move forward with the multimedia domain committee note? We have an action item from the 15 August 2017 to assess whether the LwDITA committee note can move forward. What do folks think? Closed at 11:58 AM ET. Decision: @xml-lang on <media-track> -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting
www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype)