• From: Christophe Marchand <cmarchand@o...>
• To: xml-dev@l...
• Date: Sat, 23 Jun 2018 00:49:08 +0200

Ouahouh !

Is it available on windows desks ?

Christophe


Le 22/06/2018 à 22:02, Peter Flynn a écrit :

On Fri, Jun 22, 2018 at 5:16 PM, Costello, Roger L. <costello@m...>
wrote:

I have a bunch of XML Schema documents. I need a complete list of
elements that are declared to be of type IDREF.

Is there a tool that will search through the XML Schema documents and
report all the elements of type IDREF?

The lxprintf utility from the LTxml2 package (Edinburgh) can be used to
query the XSD files from the command line, eg

$ lxprintf -e '*[@type="xs:IDREF"]' "%s on %s\n" @name
'(ancestor::xs:element|ancestor::xs:attributeGroup)/@name' docbook.xsd
linkend on db.common.linking.attributes
endterm on xref
endterm on link
otherterm on glosssee
otherterm on glossseealso
endterm on biblioref
startref on indexterm
$ lxprintf -e
'xs:element[descendant::xs:attributeGroup[@ref="docbook:db.common.linking.attributes"]]'
"%s\n" @name docbook.xsd
abbrev
abstract
accel
[...]
warning
wordasword
xref
year
$

///Peter

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

• References:
  • A tool that returns a list of the IDREF elements declared in a bunchof XML Schema documents?
    • From: "Costello, Roger L." <costello@m...>
  • Re: A tool that returns a list of the IDREF elementsdeclared in a bunch of XML Schema documents?
    • From: Mukul Gandhi <gandhi.mukul@g...>
  • Re: A tool that returns a list of the IDREF elementsdeclared in a bunch of XML Schema documents?
    • From: Peter Flynn <peter@s...>