search

RuleML / reaction-ruleml

Reaction RuleML
http://reaction.ruleml.org
8 stars 4 forks source link

Atom.content is not correct in dr-flat.rnc #74

Open greenTara opened 9 years ago

greenTara commented 9 years ago

Instead of

Atom.content =
  meta-roles.content,
  degree?,
  (# operator optional for frame representation
   element op { op-atom.type }
   | op-atom.content)?,
  Atom-slots.extend1,
  Atom-repo.extend,
  Atom-slots.extend1,
  Atom-slots.extend2

Should be

Atom.content =
  meta-roles.content,
  degree?,
  (# operator optional for frame representation
   element op { op-atom.type }
   | op-atom.content)?,
  Atom-slots.extend1,
  (Atom-repo.extend,
  Atom-slots.extend1)?,
  Atom-slots.extend2
greenTara commented 9 years ago

The convertor from XSD to RNC appears to not handle

<xs:sequence minOccurs="0">

correctly.

There are 6 occurrences of this syntax in dr-flat.xsd

greenTara commented 9 years ago

The following patterns are affect by this issue Atom.content Expr.content Plex.content ReactionRule.content Time.content Spatial.content

greenTara commented 9 years ago

Consider replacing (e.g. by XSLT)

<xs:sequence minOccurs="0">

with

<xs:choice minOccurs="0">
<xs:sequence>
apaschke commented 9 years ago

The replacement of with xs:sequence did not solve the translation problem. The nested xs:sequence gets ignored which leads to a wrong choice content model.