[oXygen-user] XSpec problems

2021-07-02 Thread Gary Gapinski
Title: Gary Gapinski's contact information

  
  
Hello, all:
I have found creation of XSPec unit tests for Schematron
  assertions a bit puzzling. I frequently manage to create
  Schematron which works correctly for instance document validation
  but related XSpec scenarios produce incorrect results. I may be
  repeatedly doing something erroneous but have yet to determine
  what.
I am using  XML Editor 23.1, build 2021061407
  which includes an XSpec 1.6.0 framework.
An exemplar of my problem can be seen at
https://github.com/18F/fedramp-automation/commit/d023c719754ee5ed14dfc8a8991fbfafb82ff18b.
  The Schematron (media-type.sch) works correctly with an
  instance document (media-type.xml) but both XSpec
  scenarios (in media-type.xspec) fail when the inbuilt
  "Run XSpec Test" translation scenario is used.

Any and all suggestions are welcome.
Best regards,
Gary

-- 
  
  
Gary Gapinski
℡ +1 216 820 1849
℡ g...@garygapinski.com
✉ g...@garygapinski.com
  

  

___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user


Re: [oXygen-user] How to inform the tool that generates sample instances which subtype to use for elements have abstract types?

2021-07-02 Thread Oxygen XML Editor Support (Radu Coravu)

Hi Roger,

There is a "Type alternative strategy" setting in the "Options" tab. But 
I'm not sure if it helps or not. If you send us (supp...@oxygenxml.com) 
a small  sample XML Schema and some details maybe we can consider this 
for a future version.


Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 7/1/21 18:12, Roger L Costello wrote:

Hi Folks,

I really, really like the tool that generates sample XML files from an XML 
Schema.

But, ..

It has a problem ..

I have an element that is declared to have a type that is a complexType and the 
complexType is abstract. There are multiple concrete subtypes of the abstract 
complexType.

When the Oxygen tool gets to the element, it realizes that its type is an 
abstract complexType, so it randomly (?) picks one of the subtypes. And it 
almost always picks the wrong subtype.

So the generated XML instance document is wrong 

Is there a way to tell the Oxygen tool, "Hey, when you encounter this element, with 
this parent, then use this subtype"?

/Roger
___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

___
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user