need assistance debugging xslt

[Jim Michaels]

http://Jesusnjim.com/menu7.xml
http://Jesusnjim.com/menu7-2014-09-30.xsd
http://Jesusnjim.com/menu7.xslt

the error I get with the XML file, which has all this stuff linked, varies with browser and XSLT checking technology.
I can't afford a $450 XSLT debugger on my current income, but I need a general XML/XSLT/whatever debugger and editor - I don't need to use predefined data types or anything, I have 1 type priorityType which definition is  borrowed from XML sitemaps 0.9.

the XSLT generates HTML5. I am hoping the FO will also work with printed pages if a person prints it out, but I think that's better handled with <style></style> tags and @page{}, however thefo is in there anyway, and it's apparently causing a problem according to firefox.

IE says:
HTML1300: Navigation occurred.
File: menu7.xml
XML5001: Applying Integrated XSLT Handling.
XSLT8607: The character '<' cannot be used in an attribute value.

File: menu7.xslt, Line: 36, Column: 17
XML5621: Incorrect comment syntax.
File: menu7.xml, Line: 11, Column: 11

however, the line numbers are incorrect, and the error messages are probably incorrect too.

ff says:
XML Parsing Error: not well-formed
Location: http://jesusnjim.com/menu7.xslt
Line Number 36, Column 17:                <fo:region-before
----------------^

chrome and opera don't recognize XML. tsk, tsk...




XML Schema Validator | CoreFiling  says:

CoreFiling XML Schema Validator

Version: 1.2.0.r278285

Well Formed: VALID
Schema Validation: INVALID


The following errors were found:

TYPE	LOC	MESSAGE
Validation	27, 60	src-resolve.4.2: Error resolving component 'xsi:priorityType'. It was detected that 'xsi:priorityType' is in namespace 'http://www.w3.org/2001/XMLSchema', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'xsi:priorityType' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'.
Validation	27, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'type definition' component.
Validation	27, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	35, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	43, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	51, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	59, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	67, 60	src-resolve: Cannot resolve the name 'xsi:priorityType' to a(n) 'simpleType definition' component.
Validation	3, 43	cvc-elt.1.a: Cannot find the declaration of element 'ul'.

Validate another document

but I notices that the first error message gives a null value for a filename, when all my filenames are defined, so it's broken.



I could use some accurate error messages.
I think all of them may be wrong.
sometimes the XML validator gives some good results.
I could use some help.

[Jim Michaels]

it's been updated and man ythings fixed, ff now just says transformartion failed. an error message that doesn't tell me anything about the underlying problem.
but at least ff is on the right track, though a bit cryptic.