[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [cgmopen-members] draft completed Viewer proforma
CGM Open member -- Here is my first completed draft of a viewer ICS pro-forma (ICS = Implementation Conformance statement). Please comment. I know that there needs to be some sort of page title/header, and I need to put the Disclaimer wording and link (I have circulated that and asked for comments -- none so far). I have been thinking of another change. Since "2." in the table encompasses Symbol Libraries and Extensions, I was thinking of splitting it into 2. and 3.: 2. Supports all standard static functionality -- for all modules below, passes all (~225) tests. 3. Supports extended static functionality -- no tests, see verdict criteria links. What do you think? -Lofton.Title: Viewer ICS pro-forma
Product(Blank pro-forma for Implementation Conformance Statement [ICS]: fill in at least product name, release/version, platform) IntroductionThe checklist below describes the conformance of the subject viewer product to the WebCGM specification, according to its performance on the WebCGM Test Suite. The functionality is coarsly divided with two questions: static graphics and dynamic behavior. Static graphics conformance is possible for all viewers. However, some viewers -- e.g., printers, or standalone interactive viewers in an environment without a Web browswer -- are inherently incapable of executing the dynamic tests. For each of the categories, dynamic and static, there is a small number of more detailed questions which summarize the basic functional categories or modules. Each category links to a specific list of tests.. "Yes" means all tests are passed, "No" means at least one test is not passed for that module. "Comments" link to a section of optional product-supplier comments (following the table) about the product's behavior on the module. Disclaimer(LH note. I think we should have a l-line terse version of the CGMO disclaimer, with link to full version. Agreed?) WebCGM viewer checklist table
Comments from table(Put a key with attached anchor here, and in Comments field of the table, put the key with link to this anchor. Example: 2.7-HSI: BlahView 2.3 passes all listed tests. It has Unicode support for UTF8 only. It supports the ISOLatin1 subset of UTF8 characters..) Test listsDynamic test listThe referenced tests are those in the WebCGM 1.0 Test Suite, Release 1.0. 1.1-tests: linking-basicH2C-BE-01, linking-basicC2H-BE-02, linking-basicC2C-BE-03, linking-basicC2P-BE-04, linking-selectId-BE-05, linking-selectName-BE-06, linking-anyURI-BE-07, linking-multiLink-BE-08 1.2-tests: behavior-picBlankC2C-BE-01, behavior-picReplaceC2C-BE-02, behavior-picBlankC2H-BE-03, behavior-picTargetC2H-BE-04, behavior-objHighlight-BE-05, behavior-objHighlightAll-BE-06, behavior-objViewContext-BE-07 1.3-tests: fragment-idC2H-BE-01, fragment-multiPic-BE-02, fragment-fiveForms-BE-03, fragment-browserBug-BE-04* 1.4-tests: interact-pick-BE-01, interact-pickRegion-BE-02, interact-screenTip-BE-03 1.5-tests: otherAPS-para-BE-01, otherAPS-para-BE-02, otherAPS-subPara-BE-03*, otherAPS-subPara-BE-04*, otherAPS-layer-BE-05*, otherAPS-contentModel-BE-06* Static test listThe referenced tests are those in the WebCGM 1.0 Test Suite, Release 1.0. 2.1-tests: 2.2-tests: 2.3-tests: 2.4-tests: 2.5-tests: 2.6-tests: 2.7-tests: Unicode: there are no Unicode tests yet. If product has capability in both UTF8 and UTF16 requirements, answer "yes", else "no". Link to vendor comments, and describe the degree of support (i.e., languages and/or Unicode subsets supported).. 2.8-tests: 2.9-tests: 2.10-tests: 2.11-tests:
2.12-tests:
If product has full capability, answer "yes", else "no". Link to vendor comments suggested. References |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC