Schema reporting tools - XQuery use case?

[George Cristian Bina]

Rick Jelliffe published a number of articles on this, the last one is
http://broadcast.oreilly.com/2009/08/converting-xml-schemas-to-sche-1.html

Best Regards,
George
-- 
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

Vyacheslav Sedov wrote:
> i am very seriously thinking about XSLT-based convertor from XSD to
> Schematron rules - i have opinion that Schematron power underestimated
> in XML world
> 
> On Wed, Sep 9, 2009 at 11:55 AM, ricardo
> queiros<http://x-query.com/mailman/listinfo/talk> wrote:
>> Hi,
>> I develop a tool for browsing XML Schema files in a easy way.
>> The tool calls http://x-query.com/mailman/listinfo/talk and can be downloaded as open source
>> at http://www.dcc.fc.up.pt/schemaDoc/.
>> It is based on a XSLT file that transforms the schema file in XHTML code to
>> be interpreted in a general browser.
>> So the only requirement is a web browser.
>> At this moment the tool don't support a few elements of the W3C XML Schema
>> specification (e.g. field, key, keyref, redefine, selector, unique elements
>> and abstract, substitutionGroup attributtes). It supports Schematron.rules
>> embeded in the schema file.
>> Best regards.
>>
>> 2009/9/9 Hans-Juergen Rennau <http://x-query.com/mailman/listinfo/talk>
>>> Hello People,
>>>
>>> XQuery is _the_ language for agile and efficient evaluation of XML
>>> resources (who would contradict me?). But there is another important
>>> technology, of course, XML Schema: though its use is often reduced to
>>> document validation or data binding, schemas offer a great wealth of static
>>> information about (valid) documents. I am sometimes amazed how merrily this
>>> information is ignored, especially in projects that have to deal with very
>>> complex schemas.
>>>
>>> Unfortunately, schemas are difficult to read and, worse, difficult to use
>>> as input for further processing, as the schema language allows to express
>>> the (essentially) same information in so many ways, what with model groups,
>>> attribute sets, type derivations, etc. Example: some configuration contains
>>> a data path, and one has the appropriate schema files available - how can
>>> one implement an automatic check of the path string against that schema?
>>>
>>> In consequence, I believe creating "schema reporting" tools may be an
>>> important use case for XQuery.Here, schema reporting is understood as
>>> transforming schema files into a different serialized representation of all
>>> or some information the schema contains. (I am _not_ thinking of graphical
>>> representations as offered by XML IDEs unless they are accompanied by
>>> serialized versions appropriate to serve as input for further processing.)
>>> Some examples were: a tree representation of document structure, a list of
>>> valid data paths, a mapping of element and attribute names to the governing
>>> type, a mapping of type names to data paths.
>>>
>>> Well - would anyone like to comment on the statement about such schema
>>> reporting being an important use case for XQuery?
>>>
>>> In this context it is of course important to know what is already
>>> available (commercial or open source). Would anyone like to speak about
>>> available schema reporting tools (in the sense defined above)?
>>>
>>> Thank you very much,
>>> with kind regards -
>>>
>>> Hans-Juergen Rennau
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> http://x-query.com/mailman/listinfo/talk
>>> http://x-query.com/mailman/listinfo/talk
>>
>>
>> --
>> Ricardo Queirós
>>
>> _______________________________________________
>> http://x-query.com/mailman/listinfo/talk
>> http://x-query.com/mailman/listinfo/talk
>>
> 
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk