                        
                     !!!!!!!!!    UPDATE WARNING     !!!!!!!!!
The service descriptions validation rules have changed in version 1.0.4: to 
correct some bugs in the portal interface, parameter names are now restricted,
and some values for parameter names are now forbidden.

1- What does this mean for me?
==============================
As a Mobyle server owner, you will have to update the service descriptions to
correct parameter names that are invalid, either by updating "external" definitions
(e.g., update pasteur-programs to version 3.0 if you use them), or by correcting
yourself the definitions you authored. Otherwise, *invalid service description won't
deploy successfully anymore*.

2- What are the forbidden values?
=================================
There are several, but most of them are mostly improbable in your descriptions. Some
will be likely, like name, length but we doubt you named one of your parameters
"insertAdjacentHTML". We will however tell you if you did. Here is a complete list
of the forbidden values:

acceptCharset,action,autocomplete,elements,encoding,enctype,length,method,name,
noValidate,checkValidity,dispatchFormChange,dispatchFormInput,item,namedItem,
submit,reset,attributes,baseURI,baseURIObject,childElementCount,childNodes,children,
classList,className,clientHeight,clientLeft,clientTop,clientWidth,contentEditable,
dataset,dir,firstChild,firstElementChild,id,innerHTML,isContentEditable,lang,
lastChild,lastElementChild,localName,name,namespaceURI,nextSibling,nextElementSibling,
nodeName,nodePrincipal,nodeType,nodeValue,offsetHeight,offsetLeft,offsetParent,
offsetTop,offsetWidth,ownerDocument,parentNode,prefix,previousSibling,
previousElementSibling,schemaTypeInfo,scrollHeight,scrollLeft,scrollTop,scrollWidth,
spellcheck,style,tabIndex,tagName,textContent,title,addEventListener,appendChild,blur,
click,cloneNode,compareDocumentPosition,dispatchEvent,focus,getAttribute,
getAttributeNS,getAttributeNode,getAttributeNodeNS,getBoundingClientRect,
getClientRects,getElementsByTagName,getElementsByTagNameNS,getFeature,getUserData,
hasAttribute,hasAttributeNS,hasAttributes,hasChildNodes,insertBefore,
isDefaultNamespace,isEqualNode,isSameNode,isSupported,lookupNamespaceURI,
lookupPrefix,mozMatchesSelector,normalize,querySelector,querySelectorAll,
removeAttribute,removeAttributeNode,removeChild,removeEventListener,replaceChild,
scrollIntoView,setAttribute,setAttributeNS,setAttributeNode,setAttributeNodeNS,
setCapture,setIdAttribute,setIdAttributeNS,setIdAttributeNode,setUserData,
insertAdjacentHTML,onbeforescriptexecute,onafterscriptexecute,oncopy,oncut,
onpaste,onbeforeunload,onblur,onchange,onclick,oncontextmenu,ondblclick,onfocus,
onkeydown,onkeypress,onkeyup,onmousedown,onmousemove,onmouseout,onmouseover,
onmouseup,onresize,onscroll

3- What do I have to correct in case I used one of these forbidden values?
==========================================================================
* the parameter name,
* any reference to it you might have added in the python code which is
embedded in the XML (precond or ctrl tags),
* any reference in the datatype references,
* and any reference you might have done to it in a workflow description that
uses your service as a task (in the link tags).

4- What can I do to check if I have any existing incompatible service description?
==================================================================================
grep and mobvalid are your friends ;)

5- I want to learn more about the fascinating cause of this technical incompatibility!
======================================================================================
Please refer to:
https://projets.pasteur.fr/issues/show/708
https://projets.pasteur.fr/issues/show/683

5- Questions
============

If you have some questions about this problem, feel free to post on 
the mobyle-users@pasteur.fr list, or to email us at mobyle-support@pasteur.fr

The Mobyle Team