[OASIS Issue Tracker] Commented: (LEGALRULEML-1) Missing PenaltyStatement element. It is defined Penalty element.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/LEGALRULEML-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35498#action_35498 ] 

Tara Athan commented on LEGALRULEML-1:
--------------------------------------

The change from Penalty to PenaltyStatement has already been made in the Relax NG schemas, but has not yet been propagated to the XSD schemas.
All example files include two instructions regarding validation - one for the Relax NG schema and one for the XSD schema.
The example files of concern here validate successfully under the Relax NG schema, but, naturally, they will not validate against the XSD schema until that is updated.

There are several ways to deal with this:
1. set up validation scenarios in oXygen, and select the appropriate scenario for the development stage
  Scenario A. performs validation against the Relax NG schema only
  Scenario B. performs validation against both Relax NG and XSD schemas

Now, oXygen does allow you to select Relax NG validation while at the same time having the particular schema (compact or normal) detected from the xml-model processing instruction. That means there would need to be a separate validation configuration for each example file, which makes it inconvenient to switch back and forth between Scenario A and Scenario B. It would be easier to accomplish this if all the compact examples were in one directory and the normal-form examples in another directory. Then the validation configuration could be changed at the directory level, making it easy to switch back and forth.
This option would also allow the xml-model PI and schemaLocation attributes to be deleted from the example files, so that users could maintain a different relative location for schemas and examples, according to their preference. 

2. set up duplicate example directories, one with only the xml-model processing instruction for the Relax NG schemas, the other having also the schemaLocation attribute that triggers XSD validation. Lack of validation of the second set of examples files could be ignored if the XSD schemas had not yet been updated. This is the least desirable option, because it violates the DRY (don't repeat yourself) principle.

3. Create a script that automates the generation of the XSD schemas from the Relax NG schemas, so that it is easy to keep the XSD schemas in synch with the Relax NG schemas. This is the best option long-term, but requires an investment of effort to create this script.

> Missing PenaltyStatement element. It is defined Penalty element.
> ----------------------------------------------------------------
>
>                 Key: LEGALRULEML-1
>                 URL: http://tools.oasis-open.org/issues/browse/LEGALRULEML-1
>             Project: OASIS LegalRuleML TC
>          Issue Type: Bug
>         Environment: XMLSpy 
>            Reporter: Monica Palmirani
>            Assignee: Tara Athan
>
> <lrml:PenaltyStatement key="pen1">
> it seems that PenaltyStatement  is not a valid element. 
> With Penalty the validation is ok. 
> Take a look to this example:
> https://tools.oasis-open.org/version-control/browse/wsvn/legalruleml/trunk/examples/approved/ex2.1.2-deontic-compact.lrml?rev=88&sc=1

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira