Minutes of Con Call 11 June 2010. Approved at 25th June 2010 Meeting

1. Intro:

2. Minutes:

28th May 2010 http://www.oasis-open.org/apps/org/workgroup/tab-internal/email/archives/201005/msg00022.html

Approved w/o Agreed to post to wiki

3. Action Items:

Action-20100430-0: Martin to investigate the current SCA test report template. Ongoing

Action-20100528-0: All to share interop/portability use cases on the mail list. Done. Discuss later

ACTION-20100528-1: Martin to add link to citation draft from TAB wiki. Done

4. Standards Dependency update:

Up to the ebxml stuff. DSS was complicated and a lot was wrong. Lots of repetition. Problems exist. People cite schemas without referencing a spec. This is a practice we shouldn't allow going forward. Collect the bad practices and document them.

This topic also includes citation best practices on the agenda. No need to cover separately.

5. Interop/Testing Policy Update:

http://wiki.oasis-open.org/tab/TestingPolicy

Updates to the wiki summarized in: http://www.oasis-open.org/apps/org/workgroup/tab-internal/email/archives/201006/msg00019.html

Make sure the term reference implementation is put into proper context within oasis.

Martin summarizes his mail: http://www.oasis-open.org/apps/org/workgroup/tab-internal/email/archives/201006/msg00004.html

Jacques reply: http://www.oasis-open.org/apps/org/workgroup/tab-internal/email/archives/201006/msg00018.html

Discission on the two posts

Martin thinks the term process, point 2 in Jacques email, is a term that could easily be confused with processor, and requests that we find a different term.

General agreement about what interop means and what is required for interop testing.

Portability is a bit softer, e.g. rendering of an odf table. Page layout is a specific problem. A lot of portability is due to lack of specificity. Portability testing will highlight lack of conformance criteria. There might be an agreement to tolerate some fuzziness, but these areas must be identified.

Agreed that data arifacts (docs, protocol elements etc) only concern conformance testing.

Interop and portability testing is not layered wrt to each other. You may need a combination depending on your specification/target.

XML is a good case study as well: an xml doc might use UTF-16 encoding, which is legal; a processor may only be able to deal with UTF-8(interop) and if it does handle UTF-16 will it render it correctly (portability).

ACTION 20100611-0: Jacques to update the wiki to capture the discussion on interop and portability.

7 Mojave update.

Martin and Jacques having issues with vpn

Martin has requested that the TAB be allowed to review and comment on any relevant kavi 5 migration documents.

8. AOB

Next call we need to plan F2F meeting.

Meeting adjourned.


Summary of New and Open Action Items:

Action-20100430-0: Martin to investigate the current SCA test report template.

ACTION 20100611-0: Jacques to update the wiki to capture the discussion on interop and portability.

Jun 11th (last edited 2010-06-25 15:48:38 by martin.chapman)