manual - meriworks.se€¦ · this document describes how the product should be installed,...

Manual

Meridum AB, Svensknabbevägen 17, 393 51 Kalmar, Sverige, www.meridium.se

SiteValidatorVersion 1.2.0

CopyrightThis manual is protected by international copyright law. No changes of content or reproduction of parts of this publication are allowed without permission from the publisher.

Manual for SiteValidator version 1.1.0Created 19 September, 2008

Last edited 2 July, 2010©Meridium Kalmar

SiteValidator | Manual

Contents 22 1

1

1. Introduction_______________________________________________21.1. Prerequisites______________________________________________ 21.2. Manual conventions_________________________________________ 21.3. W3C_____________________________________________________2

2. Usage____________________________________________________32.1. Validation Jobs____________________________________________32.2. Reports__________________________________________________42.3. Live Validation_____________________________________________ 8

22 4

4

3. Installation och configuration_________________________________93.1. Prerequisities______________________________________________93.2. Installation and upgrading____________________________________93.3. Troubleshooting installation__________________________________ 133.4. Configuration_____________________________________________ 143.5. License_________________________________________________ 163.6. Configure live validation____________________________________183.7. Exclude tests on a page____________________________________18

4. API 194.1. Reporting Accessibility Errors________________________________194.2. Interface_________________________________________________204.3. Configuration of ”More Information” links_______________________20

5. Licenses_________________________________________________21

©Meridium AB 1


1. IntroductionWelcome!SiteValidator is a plug-in module for EPiServer CMS used for validating pages published on a site based on the standards specified by international standards organization W3C.

This document describes how the product should be installed, configured and used in the daily maintenance to ensure the content is correctly formatted.

1.1. PrerequisitesSince SiteValidator is a plug-in module to EPiServer an operating EPiServer installation is required.

To get maximum benefit of this product it is recommended that the website is built to satisfy the requirements defined in the standards mentioned above.

1.2. Manual conventionsCertain typographic conventions are used in this manual.Running text is presented in the Gill Sans font. Notes, tips and warnings are presented in bold.

Note! A note highlights important information.

Tip! A tip contains an advice or an easier way to do something.

Warning! A warning highlights that a problem that might occur and how to avoid it.

1.3. W3C

W3C, World Wide Web Consortium, is arranged as a consortium, was founded in 1994 with over 500 members from businesses, nonprofit organizations, universities, and governmental entities. W3C was created to ensure compatibility and agreement among industry members in the adoption of new standards.

Examples of W3C-standards:CSS, HTML, XHTML och XML

W3C offers a free validation service for HTML, which SiteValidator can be configured to use.http://validator.w3.org/

©Meridium AB 2

http://en.wikipedia.org/wiki/International

http://validator.w3.org/

http://en.wikipedia.org/wiki/Consortium

http://en.wikipedia.org/wiki/Standards_organization


2. UsageAn administration account in EPiServer is required to be able to use SiteValidator.

2.1. Validation JobsSiteValidator is based on a scheduled jobs run at a convenient time. The validation jobs calls the validation service for each page that should be validated. When all pages have been verified a report is presented summarizing the result.

2.1.1. DescriptionThere are two different types of validation jobs. When the primary validation job is started a list with all pages published after the last run and all pages that did not pass validation last time will be created. The pages will be validated and a report is created, see Error: Reference source not found for more information. If any page fail validation a mail will be sent to the person in responsible for the content on the site.

There is also a job that will validate all published pages regardless of how long it was since they were changed.

2.1.2. ConfigurationAccess admin mode in EPiServer to access the configuration settings for the scheduled jobs. Log into admin mode by either using the server address followed by /admin, i.e. www.yourorganisation.com/something/edit, or by pressing the right mouse button followed by selecting Admin Mode on the pop-up menu.

Note! The /admin address is common for admin mode, but an extra search path is normally added for security reasons (i.e. www.yourorganisation.com /something/admin). Refer to site-specific documentation or ask your EPiServer administrator for information on how to enter the admin mode on your server.

Click on “Validation of Changed Pages” to change the settings for the scheduled job.

©Meridium AB 3

Click here


Specify how often and when the scheduled job should execute.

Note! By unchecking the ”Active” checkbox the scheduled job could be turned off.

2.2. ReportsTo access the reports you have to be in admin mode. Log into admin mode by either using the server address followed by /admin, i.e. www.yourorganisation.com/something/edit, or by pressing the right mouse button followed by selecting Admin Mode on the pop-up menu.

Note! The /admin address is common for admin mode, but an extra search path is normally added for security reasons (i.e. www.yourorganisation.com /something/admin). Refer to site-specific documentation or ask your EPiServer administrator for information on how to enter the admin mode on your server.

2.2.1. View reportsEvery time the validation job is executed a report is created, which allows you to go back and look at the result at a later time.

Click on”SiteValidator” under ”Tools” to list all available reports.

©Meridium AB 4

Click here


The reports is sorted after creation date,Date

The date and time when the report was created.

Validated pages

The number of pages that has been validated.

Invalid pages

The number of pages which is invalid, or which could not be validated.

Total number of pages

The total number of pages changed after the last validation and the pages that failed validation last time. This number can be higher than the number of validated pages if there is a limit set for the maximum number of pages that should be validated.

Pages changed after

The date when the last vaildation was executed. Used to determine which pages should be validated.

2.2.2. Detailed reportBy clicking on the link to a report in the list, a more detailed description of all the pages that didn’t pass validation is shown.

©Meridium AB 5


Page name

The name and path to the page that didn’t pass validation.

Changed

The date when the page was changed.

Created/updated by

Which editor have created or edited the page.

Test ResultShows the number of tests executed and how many test that have passed.

Show page

Open the page in EPiServer view mode.

Edit page

Open the page in EPiServer edit mode.

Show validation report

Opens a report from the validation service.

©Meridium AB 6


A description of each error found on the page and links to additional information.

2.2.3. MailInformation corresponding to the detailed report, see 2.2.2, is also sent in a mail to the person responsible for the content on the site. This mail is however only sent if there is pages that fails validation.

Exemple of mail

©Meridium AB 7


2.3. Live ValidationLogged in users can get a live validation of the current page. This requires that the user has one of the roles allowed to use this function and that the function is configured correctly according to 3.4 and 3.6

A status box is shown in the lower corner. Click the link to validate the page. There will be a link to the report if the page contains any warnings or errors.

©Meridium AB 8


3. Installation och configuration

3.1. PrerequisitiesSiteValidator requires EPiServer CMS 5 or EPiServer CMS 6 and .Net Framework 3.5 or above.

3.2. Installation and upgradingSiteValidator is installed/upgraded using a setup application that can be downloaded from http://www.meridium.se.

3.2.1. Introduction

The installation program exists in different versions for EPiServer 5 and 6. Make sure you are running the right one.

©Meridium AB 9

http://www.meridium.se/


3.2.2. License conditions

Read through the conditions and accept to continue.

3.2.3. Select EPiServer installation

Only web sites that have an EPiServer installation of version 5 or 6 will appear in the upper drop-down menu. Select the desired web site and possible virtual folder where you want SiteValidator to be installed or updated.

©Meridium AB 10


3.2.4. License File

Use the Browse button to locate your license file for SiteValidator. If no file is selected, it can later be manually copied to the web sites root directory. If you are upgrading, just click Next. You should already have a license file located in the right folder.

Note! If multiple Meridium products is installed on the same web site the license files has to be merged. This must be done manually if the file is not selected in this step.

©Meridium AB 11


3.2.5. Installation of SiteValidator

By now the Installation program has received all information about where and how SiteValidator is to be installed/upgraded. Click Finish to complete the installation.

©Meridium AB 12


3.3.Troubleshooting installationThe installation will write log messages to a log file during the installation. This log file can be useful if the installation fails for some reason. The log file will be found in the temporary folder that is created when the installation application is executed and the contained files are unpacked.

The temporary folder is found in the users temp folder (like in the example above the folder c:\Users\Admini~1\AppData\Local\Temp\2\RarSFX0 is used).The log file named log4net.txt contains a lot of debugging information that is useful for troubleshooting the installation.This temporary folder will be removed when the installation application is closed, so be sure to backup the log file if you need it for further references.

©Meridium AB 13


3.4. ConfigurationThe following will be added to the web.config file. See below for more detailed description.

<configuration>

<configSections> <sectionGroup name="se.meridium.epiServer.extensions"> <section name="siteValidator" type="SiteValidator.data.SiteValidatorConfigurationSection" /> </sectionGroup> </configSections> <se.meridium.epiServer.extensions> <siteValidator

EmailReciverList="[email protected]" FromEmail="[email protected]" DataPath="C:\SiteValidator\Data\" RootPages="3" MaxNumberOfPages="100" DaysToKeepReports="30" >

<rule name="CheckAreas" typeName="Meridium.Web.Accessibility.Rules.CheckAreas, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckDocumentStructure" typeName="Meridium.Web.Accessibility.Rules.CheckDocumentStructure, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckEmbed" typeName="Meridium.Web.Accessibility.Rules.CheckEmbed, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckFieldsetLegend" typeName="Meridium.Web.Accessibility.Rules.CheckFieldsetLegend, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckForFormattingElements" typeName="Meridium.Web.Accessibility.Rules.CheckForFormattingElements, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckForLanguageInfo" typeName="Meridium.Web.Accessibility.Rules.CheckForLanguageInfo, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckForm" typeName="Meridium.Web.Accessibility.Rules.CheckForm, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckHeading" typeName="Meridium.Web.Accessibility.Rules.CheckHeading, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckImages" typeName="Meridium.Web.Accessibility.Rules.CheckImages, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckInputTypeImg" typeName="Meridium.Web.Accessibility.Rules.CheckInputTypeImg, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckLinkText" typeName="Meridium.Web.Accessibility.Rules.CheckLinkText, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckNestedTables" typeName="Meridium.Web.Accessibility.Rules.CheckNestedTables, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckTables" typeName="Meridium.Web.Accessibility.Rules.CheckTables, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckTitle" typeName="Meridium.Web.Accessibility.Rules.CheckTitle, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" />

©Meridium AB 14


<rule name="CheckValidLanguageCode" typeName="Meridium.Web.Accessibility.Rules.CheckValidLanguageCode, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckW3CValidator" typeName="Meridium.Web.Accessibility.Rules.CheckW3CValidator, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493"> <ruleSettings> <add key="ValidatorUrl" value="http://validator.meridium.se/check" /> </ruleSettings> </rule> <rule name="CheckInlineCss" typeName="Meridium.Web.Accessibility.Rules.CheckInlineCss, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckInlineEvent" typeName="Meridium.Web.Accessibility.Rules.CheckInlineEvent, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckJavaScriptLinks" typeName="Meridium.Web.Accessibility.Rules.CheckJavaScriptLinks, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckNoscript" typeName="Meridium.Web.Accessibility.Rules.CheckNoscript, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> <rule name="CheckTarget" typeName="Meridium.Web.Accessibility.Rules.CheckTarget, Meridium.Web.Accessibility, Version=3.1.9.0, Culture=neutral, PublicKeyToken=01f4840270d48493" /> </rules> </se.meridium.epiServer.extensions></configuration>

EmailReciverListA comma separeted list with email addresses to the users that should be notified when there is pages failing validation.

FromEmailWhich email adress that should be set at the sender for the emails sent.

DataPathSpecifies were the reports and temporary files should be saved. If this value is changed it is important to ensure that the user running the ASP.Net process has rights to read, write and create files in this folder and subfolder. Normally this is the user Network Service, but this can be configured in the application pool.

RootPagesA comma separated list of root pages in the tree where the validation job will start looking for pages to validate.

MaxNumberOfPagesCan be set to limit the amount of pages to validate.

DaysToKeepReportsDetermines for how long the reports should be saved. Set to 0 to always keep the reports.

CustomCssSet the css applied to the mail being sent if validation errors occur.

ExcludePageTypes

©Meridium AB 15


A comma separated list of page types that should not be validated.

LiveValidationRoleListA comma separated list of roles that should be able to use the live validation feature.

RulesContains sub elements of the type Rule, where each Rule element describes an accessibility test that shall be run.

RuleThe Rule element describes an accessibility test that should be used by SiteValidator. To entirely exclude an accessibility test from being run by SiteValidator, remove or comment away its Rule element in the configuration. The Rule elements described in the configuration above are those that normally are delivered with SiteValidator. External additions to the tests are also possible, using the API described in chapter Error: Reference source not found. To add additional accessibility tests, add new elements of this type to the configuration. The attribute typeName refers to the class and assembly that implement the accessibility test.

RuleSettingsContains the specific settings for the rule.

ValidatorUrlThis is the URL to the validation service. Either use Meridium’s validator server or the public one at http://validator.w3.org/check, or set one up locally.

3.5. LicenseThe validation job requires a valid license file to run. The file is named meridiumLicense.config and should be located in the root folder of the web site. Licenses could be ordered and managed at www.meridium.se.

If other Meridium products is inhstalled on the site the license file will already exist. In this case you have to manually copy the license information into the existing file, otherwise the file can just be saved att the right location.

The licens file looks like this:<?xml version="1.0" encoding="utf-8"?><LicenseFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Licenses name="ImageVault" licenseId="xxxx" licenseVersionNumber="4">.....

</Licenses> <Licenses name="ProcessMap" licenseId="yyyy" licenseVersionNumber="1">

..... </Licenses> <Licenses name="SiteValidator" licenseId="zzzz" licenseVersionNumber="1">

..... </Licenses>

</LicenseFile>

©Meridium AB 16

http://www.meridium.se/

http://validator.w3.org/check


To add a new licens open the new license file in notepad.Select and copy the entire section between <Licenses… and </Licenses> including these tags. Then copy this text.Open the existing license file and paste the copied text inside the <LicenseFile>-tag.

©Meridium AB 17

3.6. Configure live validationThe following code must be added to the page.

<%@ Register TagPrefix="Meridium" Namespace="SiteValidatorWeb.SiteValidator.WebControls" Assembly="SiteValidatorWeb" %>

<Meridium:Validator runat="server" />

As the live validation is built to occupy one line on top of the page, this is preferably added directly after the body element in the master page used.

3.7. Exclude tests on a page

SiteValidator provides the function to disable one or more accessibility tests on a particular page. Meridium recommends not using this function except under special circumstances, as its usage risks lowering the sites accessibility.

To disable a particular accessibility test on a page, add the following line of code somewhere on the source of the page:

Example: To disable the test ”CheckTables”, which checks that nested table elements are not used, add the following lines of code:

©Meridium AB 18


4. APISiteValidator supports an API that makes it possible for partners and customers to create and add new accessibility tests to the accessibility tests that are run by SiteValidator. The requirement for creating and adding a new accessibility test is that one class is created per test; the class should implement a special interface, report errors with a special type and be compiled into an assembly that is placed in the web-sites bin folder.

The interface and the error class that should be used are public and found in the library Meridium.Web.Accessibility found in the bin folder of the web-site.

4.1. Reporting Accessibility ErrorsWhen an added test is to report an error found in a page, it shall create an object of the type ExternalValidationError. It is important that added tests use this class for error reporting, there are other error classes but these are for internal usage by SiteValidator.

4.1.1. ExternalValidationError ClassThis class is used to report errors from accessibility tests created by partners and customers. It contains the following properties:

public int ExternalErrorTypeIdThis property is used to identify a certain type of errors. For instance, all discovered errors of the type ”Missing Title” are all created with the same error type-ID. It is important that errors of different types utilize the same ID. The ID must also be greater than 10,000 (the first 10,000 numbers are reserved for internal usage). public string ExternalErrorNameThis property should contain a short describing name for the error type.public string ExternalErrorDescriptionThis property should contain a more elaborate description of the error, and can also contain additional information about for example which element it is that is erroneous in the source, or other information that makes it possible to locate where on the page the error has occurred.public override int ErrorTypeIdThis property is for internal usage and cannot be set. Do not use.public override string ErrorNameThis property is for internal usage and cannot be set. Do not use.public override string ErrorDescriptionThis property is for internal usage and cannot be set. Do not use.public virtual List<HyperLink> LinksThis property is for internal usage and cannot be set. Do not use.

The class also contains a constructor on the form:ExternalValidationError(int errorTypeId, string errorName, string errorDescription)This constructor can be used to easily set the three properties ExternalErrorTypeId, ExternalErrorName and ExternalErrorDescription which should be set in each created error.

©Meridium AB 19


4.2. InterfaceThere are two interfaces that can be chosen between to implement a test class, IGeneralValidationRule and IXPathValidationRule.

4.2.1. IGeneralValidationRule InterfaceThis interface should be implemented if the test should utilize the raw page source as text. The Interface contains one method and one property:List<ValidationError> Validate(string html, string inputNamespace);Dictionary<string,string> Settings { get; set; }

When it is time to evaluate the rule for a given page, this method with be called with the parameter html contain the whole pages source, and the parameter inputNamespace containing the namespace that the page is in (if it is an XHTML valid page it probably is set to http://www.w3.org/1999/xhtml). The settings property is populated with the keys thet are specified in web.config.

The method shall return a list populated with ExternalValidationError objects containing the found errors. If no errors are found, the method can either return null or an empty list.

4.2.2. IXPathValidationRuleThis interface should be implemented if the test should utilize the page source parsed as an XPathDocument object. The test will then get an already created XPathDocument that can be shared between different tests and thus improve performance. The interface contains one method and one property:List<ValidationError> Validate(XPathDocument document, System.Xml.XmlNamespaceManager ns);Dictionary<string,string> Settings { get; set; }

When it is time to evaluate the rule for a given page, this method will be called with the parameter document set to an XPathDocument created from the whole page source, and is set to an XmlNamespaceManager where the key ”a” maps to the namespace the document has (if it an XHTML valid page it probably http://www.w3.org/1999/xhtml). The settings property is populated with the keys thet are specified in web.config.The method shall return a list populated with ExternalValidationError objects containing the found errors. If no errors are found, the method can either return null or an empty list.

4.3. Configuration of ”More Information” linksIf the errors reported by added accessibility tests should provide links to more information when reported, these links can be added to the file SiteValidator\MoreInfoLinks.xml. This is done by adding lines to the file on the following format:

<LinksForError ErrorType="ExternalErrorTypeId"> <HyperLink> <Description>Link text </Description> <Url>Link URL</Url> </HyperLink> </LinksForError>

©Meridium AB 20

http://www.w3.org/1999/xhtml

http://www.w3.org/1999/xhtml


ErrorType contains the errors ID as set when the error is created, Description contains the links describing text and Url contains the links address.

5. LicensesThe solution is partly based on code from the following projects.

http://www.peterkrantz.com/raakt/wiki/------------------------------------Copyright (c) 2007, Peter Krantz (http://www.peterkrantz.com)All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of Peter Krantz nor the names of contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.------------------------------------

http://www.codeplex.com/Wiki/View.aspx?ProjectName=MVPXML------------------------------------Copyright (c) 2005, XMLMVP ProjectAll rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

©Meridium AB 21


* Neither the name of the XMLMVP Project nor the names of its contributors may be used to endorse or promote products derivedfrom this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ------------------------------------

©Meridium AB 22

manual - meriworks.se€¦ · this document describes how the product should be installed,...

Documents