rng-users : Messages : 1011-1040 of 1479

CALL FOR PROPOSALS
==================

Text encoding in the era of mass digitization: 2009 Annual Meeting of
the TEI Consortium
------------------------------------------------------------------------

http://www.lib.umich.edu/spo/teimeeting09/

The Program Committee of the 2009 Annual Meeting of the Text Encoding
Initiative Consortium invites individual paper proposals, panel
sessions, poster sessions, and tool demonstrations particularly, but
not exclusively, on the theme "Text encoding in the era of mass
digitization".

SUBMISSION TOPICS

Topics might include but are not restricted to:

    * In-depth encoding vs. mass digitization
    * Is text encoding sustainable?
    * Is text encoding scalable?
    * Using TEI to create:
       - scholarly editions
       - hybrid publications (digital and print)
       - databases and other resources
    * Tools that create and process TEI data
    * TEI used in conjunction with other technologies and standards
    * TEI as:
       - metadata standard
       - interchange format: sharing, mapping, and migrating data
    * TEI and its contribution to digital scholarship
    * TEI and markup theory
    * Learning the TEI
    * The future of the TEI
    * When not to use the TEI

In addition, we are seeking P5 micropaper proposals for 5 minute
presentations on the topic "How I've customized TEI encoding to meet
my needs".

SUBMISSION TYPES

Individual paper presentations will be allocated 30 minutes: 20
minutes for delivery, and 10 minutes for questions & answers.

Panel sessions will be allocated 1.5 hours and may be of varied
formats, including:

    * three paper panels: 3 papers on the same or related topics
    * round table discussion: 3-6 presenters on a single theme. Ample
      time should be left for questions & answers after brief
      presentations.

Posters (including tool demonstrations) will be presented during the
poster session. The local organizer will provide flip charts and
tables for poster session/tool demonstration presenters, along with
wireless internet access. Each poster will have the opportunity to
participate in a slam immediately preceding the poster session.

P5 micropapers will be allocated 5 minutes.

SUBMISSION PROCEDURE

All proposals should be submitted at http://www.tei-c.org/conftool/
by 15 May 2009. The system is not yet ready to accept submissions but
will be ready to accept submissions in mid-April.

You will need to create an account (i.e., username and password) in
order to file a submission. For each submission, you may upload files
to the system after you have completed filling out demographic data
and the abstract.

    * Individual paper or poster session proposals (including tool
      demonstrations):
       - Please submit a brief abstract (no more than 500 words) in
         the "Abstract" field.
       - Supporting materials (including graphics, multimedia, etc.,
         or even a copy of the complete paper) may be uploaded after
         the initial abstract is submitted.

    * P5 micropaper:
       - The procedure is the same as for an individual paper except
         that the abstract should be no more than 300 words.

    * Panel sessions:
       - The panel organizer submits an abstract for the entire
         session, listing the proposed papers, and explaining the
         organizing theme and rationale for the inclusion of the
         papers in no more than 500 words in the "Abstract" field.
       - The panel members each submit a separate complete individual
         paper proposal; see above. The program committee reserves the
         right to accept papers submitted as part of a panel without
         accepting the whole panel.

All proposals will be reviewed by the program committee and selected
external reviewers.

Those interested in holding working paper sessions outside the
meeting session tracks should contact the meeting organizers at
tei-meeting-2009@... to schedule a room.

Please send queries to tei-meeting-2009@... .

Conference submissions will be considered for a conference
proceedings. Further details on the submission process will be
forthcoming.

#1012

From: "mr_xsive" <mr_xsive@...>
Date: Wed Apr 8, 2009 12:50 pm
Subject: Any way to subtype JING Validators?

mr_xsive

Hi,

I have an XML file which I'd like to validate. I also want to populate a hash
table based on the contents of the document -- ideally at the same time.

Long story short: I've setup a validation routine similar to JING's
ValidationDriver. What I now want to do is this: if an element is valid, I'd
like to perform some application logic based on its contents and populate my
hash table.

However, I can't extend the Validator object because it gets created by my
Schema object and there's no (easy) way I can tell it to construct a different
validator.

If I try to construct my own Validator it turns into a real nightmare as I then
need a Pattern object for the constructor and understanding how to build one of
those requires diving into the internals of JING (I spent an hour or so tracing
through the code but eventually gave up).

So I thought, OK, no problem. I'll just create a new proxy ContentHandler which
encapsulates one of JING's Validators and pass that to my XMLReader. I figured
each time one of my ContentHandler methods is invoked I can invoke the JING's
Validator method of the same name and thus check if the element is valid before
I perform my stuff.

But I'm foiled again because JING's Validators implement not just the
ContentHandler interface but also ErrorHandler so I never know if there was an
error or not because the startElement method (for instance) calls directly to
the error method.

Since there's no separation of concerns between handling the content and dealing
with errors I'm left with no real option except to parse the document once for
validity and then parse it again with a custom ContentHandler to do my stuff.

Is there any way out of this mess?

Reply | Messages in this Topic (2)

#1013

From: James Clark <jjc@...>
Date: Thu Apr 9, 2009 2:59 am
Subject: Re: Any way to subtype JING Validators?

james_j_clark

The implementation of NVDL does something very similar to what you want to do: it uses the RELAX NG schema to validate the NVDL schema while at the same time building its internal representation of the schema.

Let's call your ContentHandler that populates the hash-table B.� Le'ts call your error handler that reports errors E. First of all you create a wrapper E' around E.� E' just keeps track of whether there's been an error before forwarding the error event on to E.� Now create a Validator V that uses E' as it's ErrorHandler.

Now create a ContentHandler C, that has references to B, V, and E'.� This forwards each event to V. It then checks E' to see whether there's been an error. If there hasn't been an error, it then forwards the event also to B.

Hope this helps.

James

On Wed, Apr 8, 2009 at 7:50 PM, mr_xsive <mr_xsive@...> wrote:

Hi,

I have an XML file which I'd like to validate. I also want to populate a hash table based on the contents of the document -- ideally at the same time.

Long story short: I've setup a validation routine similar to JING's ValidationDriver. What I now want to do is this: if an element is valid, I'd like to perform some application logic based on its contents and populate my hash table.

However, I can't extend the Validator object because it gets created by my Schema object and there's no (easy) way I can tell it to construct a different validator.

If I try to construct my own Validator it turns into a real nightmare as I then need a Pattern object for the constructor and understanding how to build one of those requires diving into the internals of JING (I spent an hour or so tracing through the code but eventually gave up).

So I thought, OK, no problem. I'll just create a new proxy ContentHandler which encapsulates one of JING's Validators and pass that to my XMLReader. I figured each time one of my ContentHandler methods is invoked I can invoke the JING's Validator method of the same name and thus check if the element is valid before I perform my stuff.

But I'm foiled again because JING's Validators implement not just the ContentHandler interface but also ErrorHandler so I never know if there was an error or not because the startElement method (for instance) calls directly to the error method.

Since there's no separation of concerns between handling the content and dealing with errors I'm left with no real option except to parse the document once for validity and then parse it again with a custom ContentHandler to do my stuff.

Is there any way out of this mess?

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
� �http://groups.yahoo.com/group/rng-users/

<*> Your email settings:
� �Individual Email | Traditional

<*> To change settings online go to:
� �http://groups.yahoo.com/group/rng-users/join
� �(Yahoo! ID required)

<*> To change settings via email:
� �mailto:rng-users-digest@yahoogroups.com
� �mailto:rng-users-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
� �rng-users-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
� �http://docs.yahoo.com/info/terms/

Reply | Messages in this Topic (2)

#1014

From: "tw33zer" <mstoef@...>
Date: Thu Apr 9, 2009 2:26 pm
Subject: trang converting rng to XML schema issue

tw33zer

I have a rng file that is redefining patterns in a core rng file.  So, in the
included rng I have

  <define name="att.res">
     <choice>
       <value type="integer">75</value>
       <value type="integer">200</value>
       <value type="integer">300</value>
     </choice>
   </define>


and in the including rng I have

<include href="core.rng">
         <define name="att.res">
             <choice>
                 <value type="integer">75</value>
                 <value type="integer">300</value>
             </choice>
         </define>

</include>

When I run trang conversion on including rng file and generate XSD, the output
is

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
   <xs:include schemaLocation="core.xsd"/>
   <xs:simpleType name="att.res">
     <xs:restriction base="xs:integer">
       <xs:enumeration value="75"/>
       <xs:enumeration value="300"/>
     </xs:restriction>
   </xs:simpleType>
</xs:schema>


To me, this XSD should be invalid, because there are essentially two simpleType
definitions with the same name.  But when I then run validation inside Oxygen
10.1 against an instance with the generated schema, it parses just fine.  Is
there something about this that I don't understand?  Is the schema really valid,
or is the validation not parsing the schema properly.

Also, if I wanted to output in this example to be one XSD schema--essentially
printing out the resolved, flat schema--is there any way to do that?

Thanks much.

#1015

From: "tw33zer" <mstoef@...>
Date: Thu Apr 9, 2009 3:34 pm
Subject: Re: trang converting rng to XML schema issue

tw33zer

Oh, I totally missed that trang ripped the redefined pattern from the generated
core.xsd.  That is embarrasing.

Still interested in something that could output the compiled, flat schema.




--- In rng-users@yahoogroups.com, "tw33zer" <mstoef@...> wrote:
>
> I have a rng file that is redefining patterns in a core rng file.  So, in the
included rng I have
>
>  <define name="att.res">
>     <choice>
>       <value type="integer">75</value>
>       <value type="integer">200</value>
>       <value type="integer">300</value>
>     </choice>
>   </define>
>
>
> and in the including rng I have
>
> <include href="core.rng">
>         <define name="att.res">
>             <choice>
>                 <value type="integer">75</value>
>                 <value type="integer">300</value>
>             </choice>
>         </define>
>
> </include>
>
> When I run trang conversion on including rng file and generate XSD, the output
is
>
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
>   <xs:include schemaLocation="core.xsd"/>
>   <xs:simpleType name="att.res">
>     <xs:restriction base="xs:integer">
>       <xs:enumeration value="75"/>
>       <xs:enumeration value="300"/>
>     </xs:restriction>
>   </xs:simpleType>
> </xs:schema>
>
>
> To me, this XSD should be invalid, because there are essentially two
simpleType definitions with the same name.  But when I then run validation
inside Oxygen 10.1 against an instance with the generated schema, it parses just
fine.  Is there something about this that I don't understand?  Is the schema
really valid, or is the validation not parsing the schema properly.
>
> Also, if I wanted to output in this example to be one XSD schema--essentially
printing out the resolved, flat schema--is there any way to do that?
>
> Thanks much.
>

#1016

From: George Cristian Bina <george@...>
Date: Thu Apr 9, 2009 7:23 pm
Subject: Re: Re: trang converting rng to XML schema issue

george_bina

Hi,

  > Still interested in something that could output the compiled, flat
  > schema.

In oXygen try on the XML Schema file

Document -> Refactoring -> Flatten Schema

or you can invoke it from the contextual menu, right click on
Windows/CTRL+Click on Mac -> Refactoring -> Flatten Schema.

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


tw33zer wrote:
> Oh, I totally missed that trang ripped the redefined pattern from the
generated core.xsd.  That is embarrasing.
>
> Still interested in something that could output the compiled, flat schema.
>
>
>
>
> --- In rng-users@yahoogroups.com, "tw33zer" <mstoef@...> wrote:
>> I have a rng file that is redefining patterns in a core rng file.  So, in the
included rng I have
>>
>>  <define name="att.res">
>>     <choice>
>>       <value type="integer">75</value>
>>       <value type="integer">200</value>
>>       <value type="integer">300</value>
>>     </choice>
>>   </define>
>>
>>
>> and in the including rng I have
>>
>> <include href="core.rng">
>>         <define name="att.res">
>>             <choice>
>>                 <value type="integer">75</value>
>>                 <value type="integer">300</value>
>>             </choice>
>>         </define>
>>
>> </include>
>>
>> When I run trang conversion on including rng file and generate XSD, the
output is
>>
>> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
>>   <xs:include schemaLocation="core.xsd"/>
>>   <xs:simpleType name="att.res">
>>     <xs:restriction base="xs:integer">
>>       <xs:enumeration value="75"/>
>>       <xs:enumeration value="300"/>
>>     </xs:restriction>
>>   </xs:simpleType>
>> </xs:schema>
>>
>>
>> To me, this XSD should be invalid, because there are essentially two
simpleType definitions with the same name.  But when I then run validation
inside Oxygen 10.1 against an instance with the generated schema, it parses just
fine.  Is there something about this that I don't understand?  Is the schema
really valid, or is the validation not parsing the schema properly.
>>
>> Also, if I wanted to output in this example to be one XSD schema--essentially
printing out the resolved, flat schema--is there any way to do that?
>>
>> Thanks much.
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

#1017

From: "tw33zer" <mstoef@...>
Date: Fri Apr 10, 2009 12:47 pm
Subject: Re: trang converting rng to XML schema issue

tw33zer

I don't suppose there is an API that allows one to do this programmatically?

m./


--- In rng-users@yahoogroups.com, George Cristian Bina <george@...> wrote:
>
> Hi,
>
>  > Still interested in something that could output the compiled, flat
>  > schema.
>
> In oXygen try on the XML Schema file
>
> Document -> Refactoring -> Flatten Schema
>
> or you can invoke it from the contextual menu, right click on
> Windows/CTRL+Click on Mac -> Refactoring -> Flatten Schema.
>
> Best Regards,
> George
> --
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
>
> tw33zer wrote:
> > Oh, I totally missed that trang ripped the redefined pattern from the
generated core.xsd.  That is embarrasing.
> >
> > Still interested in something that could output the compiled, flat schema.
> >
> >
> >
> >
> > --- In rng-users@yahoogroups.com, "tw33zer" <mstoef@> wrote:
> >> I have a rng file that is redefining patterns in a core rng file.  So, in
the included rng I have
> >>
> >>  <define name="att.res">
> >>     <choice>
> >>       <value type="integer">75</value>
> >>       <value type="integer">200</value>
> >>       <value type="integer">300</value>
> >>     </choice>
> >>   </define>
> >>
> >>
> >> and in the including rng I have
> >>
> >> <include href="core.rng">
> >>         <define name="att.res">
> >>             <choice>
> >>                 <value type="integer">75</value>
> >>                 <value type="integer">300</value>
> >>             </choice>
> >>         </define>
> >>
> >> </include>
> >>
> >> When I run trang conversion on including rng file and generate XSD, the
output is
> >>
> >> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
> >>   <xs:include schemaLocation="core.xsd"/>
> >>   <xs:simpleType name="att.res">
> >>     <xs:restriction base="xs:integer">
> >>       <xs:enumeration value="75"/>
> >>       <xs:enumeration value="300"/>
> >>     </xs:restriction>
> >>   </xs:simpleType>
> >> </xs:schema>
> >>
> >>
> >> To me, this XSD should be invalid, because there are essentially two
simpleType definitions with the same name.  But when I then run validation
inside Oxygen 10.1 against an instance with the generated schema, it parses just
fine.  Is there something about this that I don't understand?  Is the schema
really valid, or is the validation not parsing the schema properly.
> >>
> >> Also, if I wanted to output in this example to be one XSD
schema--essentially printing out the resolved, flat schema--is there any way to
do that?
> >>
> >> Thanks much.
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

#1018

From: "MURATA Makoto (FAMILY Given)" <EB2M-MRT@...>
Date: Fri Apr 10, 2009 4:55 pm
Subject: Extending RELAX NG

mktmurata

Dear users of RELAX NG,

SC34/WG1 has started a new project for extending RELAX NG.

This project is intended to provide better modularization mechanisms and
some other minor enhancements.  Suggested extensions are summarized at:

http://wiki.oasis-open.org/relax-ng/FutureRequirements

The official resolution of SC34 and the project subdivision proposal are
available at:

http://www.itscj.ipsj.or.jp/sc34/open/1188.htm#Res6

http://www.itscj.ipsj.or.jp/sc34/open/1181.htm

Cheers,

--
Makoto <EB2M-MRT@...>

#1019

From: "al_shopov" <al_shopov@...>
Date: Fri Apr 24, 2009 5:05 am
Subject: Converting W3 schemas to RelaxNG ones

al_shopov

Hi everyone,
It seems to me that trang cannot convert xsd schemas to RelaxNG ones. Are there
any plans to add this feature in the future or are there reasons not to do this?
If yes, can anyone suggest a tool for such a conversion?
Kind regards:
al_shopov

#1020

From: Florent Georges <darkman_spam@...>
Date: Fri Apr 24, 2009 12:36 pm
Subject: Re : Converting W3 schemas to RelaxNG ones

darkman_spam

al_shopov wrote:

> It seems to me that trang cannot convert xsd schemas to
> RelaxNG ones. Are there any plans to add this feature in the
> future or are there reasons not to do this? If yes, can
> anyone suggest a tool for such a conversion?

   You can look for rngconv from MSV.

   Regards,

--
Florent Georges
http://www.fgeorges.org/

#1021

From: "nico_debeissat" <ndebeiss@...>
Date: Sat Apr 25, 2009 5:37 pm
Subject: Re: Re : Converting W3 schemas to RelaxNG ones

nico_debeissat

--- In rng-users@yahoogroups.com, Florent Georges <darkman_spam@...> wrote:
>
>
> al_shopov wrote:
>
> > It seems to me that trang cannot convert xsd schemas to
> > RelaxNG ones. Are there any plans to add this feature in the
> > future or are there reasons not to do this? If yes, can
> > anyone suggest a tool for such a conversion?
>
>   You can look for rngconv from MSV.
>
>   Regards,
>
> --
> Florent Georges
> http://www.fgeorges.org/
>

Try that, it is web based, no installation needed :
http://debeissat.nicolas.free.fr/XSDtoRNG.php
I do not think that works with another explorer that firefox.
Fill an issue at http://code.google.com/p/xsdtorngconverter/ if it does not
work.

nico

#1022

From: Alexander Shopov <al_shopov@...>
Date: Mon Apr 27, 2009 11:28 am
Subject: Re: Re : Converting W3 schemas to RelaxNG ones

al_shopov

Thank you very much, It worked like a charm.

I also found another tool for the job: http://www.brics.dk/schematools/
However rngconv's output was much, much more understandable.
I had only one difficulty with rngconv, but solved it via the following advice:

http://relaxng.org/pipermail/relaxng-user/2004-May/000528.html
Thanx for the advice.
Kind regards:
al_shopov

From: Florent Georges <darkman_spam@...>
To: rng-users@yahoogroups.com
Sent: Friday, April 24, 2009 3:36:57 PM
Subject: Re : [rng-users] Converting W3 schemas to RelaxNG ones

al_shopov wrote:

> It seems to me that trang cannot convert xsd schemas to
> RelaxNG ones. Are there any plans to add this feature in the
> future or are there reasons not to do this? If yes, can
> anyone suggest a tool for such a conversion?

You can look for rngconv from MSV.

Regards,

--
Florent Georges
http://www.fgeorges.org/

#1023

From: Alexander Shopov <al_shopov@...>
Date: Mon Apr 27, 2009 11:34 am
Subject: Re: Re : Converting W3 schemas to RelaxNG ones

al_shopov

I found that tool but had great trouble using it. Will post via the bug track.
Kind regards:
al_shopov

From: nico_debeissat <ndebeiss@...>
To: rng-users@yahoogroups.com
Sent: Saturday, April 25, 2009 8:37:00 PM
Subject: Re: Re : [rng-users] Converting W3 schemas to RelaxNG ones

--- In rng-users@yahoogrou ps.com, Florent Georges <darkman_spam@ ...> wrote:
>
>
> al_shopov wrote:
>
> > It seems to me that trang cannot convert xsd schemas to
> > RelaxNG ones. Are there any plans to add this feature in the
> > future or are there reasons not to do this? If yes, can
> > anyone suggest a tool for such a conversion?
>
> You can look for rngconv from MSV.
>
> Regards,
>
> --
> Florent Georges
> http://www.fgeorges.org/
>

Try that, it is web based, no installation needed :
http://debeissat. nicolas.free. fr/XSDtoRNG. php
I do not think that works with another explorer that firefox.
Fill an issue at http://code. google.com/ p/xsdtorngconver ter/ if it does not work.

nico

#1024

From: Norman Walsh <ndw@...>
Date: Wed Apr 29, 2009 6:08 pm
Subject: NVDL support in Jing?

normwalsh

Hi folks,

At XML Prague, I was reminded (IIRC) that there's support for NVDL in
current builds of Jing. A couple of days ago, I managed to integrate
Jing into my XProc implementation, so now I'm curious about providing
an NVDL extension step.

Pointers to the NVDL APIs or a little example app that does NVDL
validation with the Jing API would be most appreciated.

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@...> | The things we have most longed for do
http://nwalsh.com/            | not happen; or if they do, it is never
                               | at the time nor under the circumstances
                               | when they could have made us
                               | happiest.--La Bruyère

#1025

From: Norman Walsh <ndw@...>
Date: Thu Apr 30, 2009 12:02 pm
Subject: DTD default value annotations?

normwalsh

Hello again,

In private mail, I got some API examples and now I have a working NVDL
step. Very cool.

Thinking about the options for the NVDL step reminded me that I hadn't
hooked up all the RELAX NG options. I figured out how to enable (and
not enable) ID/IDREF checking, but is there any way to get Jing to
report the augmented infoset for a document that is validated with a
schema that uses DTD compatibility and provides default attribute
values?

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@...> | It is good to have an end to journey
http://nwalsh.com/            | toward; but it is the journey that
                               | matters, in the end.--Ursula K. LeGuin

#1026

From: John Cowan <cowan@...>
Date: Thu Apr 30, 2009 1:38 pm
Subject: Re: DTD default value annotations?

johnwcowan

Norman Walsh scripsit:

> Thinking about the options for the NVDL step reminded me that I hadn't
> hooked up all the RELAX NG options. I figured out how to enable (and
> not enable) ID/IDREF checking, but is there any way to get Jing to
> report the augmented infoset for a document that is validated with a
> schema that uses DTD compatibility and provides default attribute
> values?

Jing only checks that IDs are unique and that IDREF and IDREFS attributes
don't refer to unknown IDs.  It doesn't report ID-type information to
its caller, and it doesn't implement default-attribute processing, so
there is no augmented infoset of any kind.  Indeed, I don't know of any
RNG validator that does any more than Jing does.

--
John Cowan  <cowan@...>  http://www.ccil.org/~cowan
         Raffiniert ist der Herrgott, aber boshaft ist er nicht.
                 --Albert Einstein

#1027

From: Norman Walsh <ndw@...>
Date: Thu Apr 30, 2009 6:03 pm
Subject: Re: DTD default value annotations?

normwalsh

John Cowan <cowan@...> writes:
> Jing only checks that IDs are unique and that IDREF and IDREFS attributes
> don't refer to unknown IDs.  It doesn't report ID-type information to
> its caller, and it doesn't implement default-attribute processing, so
> there is no augmented infoset of any kind.  Indeed, I don't know of any
> RNG validator that does any more than Jing does.

I was under the impression that MSV did more, but I'll have to double-check.

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@...> | Life is a great bundle of little
http://nwalsh.com/            | things.--Oliver Wendell Holmes

#1028

From: John Cowan <cowan@...>
Date: Thu Apr 30, 2009 6:30 pm
Subject: Re: DTD default value annotations?

johnwcowan

Norman Walsh scripsit:

> I was under the impression that MSV did more, but I'll have to double-check.

The commandline.html file bundled with MSV says it supports all three
features at level 1 only (no infoset modification).  Consequently, it's
only checking that a:defaultValue and a:documentation are used according
to the rules; they still don't do anything.

--
The experiences of the past show                John Cowan
that there has always been a discrepancy        cowan@...
between plans and performance.                  http://www.ccil.org/~cowan
         --Emperor Hirohito, August 1945

#1029

From: Syd Bauman <Syd_Bauman@...>
Date: Sat May 2, 2009 1:32 am
Subject: CFP: Text encoding in the era of mass digitization (due 15 May 2009)

syd_bauman

CALL FOR PROPOSALS
	   Text encoding in the era of mass digitization
      2009 Conference and Members' Meeting of the TEI Consortium
             http://www.lib.umich.edu/spo/teimeeting09/
       November 11-15, 2009 -- University of Michigan, Ann Arbor

The Program Committee of the 2009 Conference and Members' Meeting of
the Text Encoding Initiative Consortium invites individual paper
proposals, panel sessions, poster sessions, and tool demonstrations
particularly, but not exclusively, on the theme "Text encoding in the
era of mass digitization."

== Submission Topics ==

Topics might include but are not restricted to:

  * In-depth encoding vs. mass digitization
  * Is text encoding sustainable?
  * Is text encoding scalable?
  * Using TEI to create:
    - scholarly editions
    - hybrid publications (digital and print)
    - databases and other resources
  * Tools that create and process TEI data
  * TEI used in conjunction with other technologies and standards
  * TEI as:
    - metadata standard
    - interchange format: sharing, mapping, and migrating data
  * TEI and its contribution to digital scholarship
  * TEI and markup theory
  * Learning the TEI
  * The future of the TEI
  * When not to use the TEI

In addition, we are seeking P5 micropaper proposals for 5 minute
presentations on the topic "How I've customized TEI encoding to meet
my needs."

== Submission Types ==

Individual paper presentations will be allocated 30 minutes: 20
minutes for delivery, and 10 minutes for questions & answers.

Panel sessions will be allocated 1.5 hours and may be of varied
formats, including:

  * three paper panels: 3 papers on the same or related topics
  * round table discussion: 3-6 presenters on a single theme. Ample
    time should be left for questions & answers after brief
    presentations.

Posters (including tool demonstrations) will be presented during the
poster session. The local organizer will provide flip charts and
tables for poster session/tool demonstration presenters, along with
wireless internet access. Each poster will have the opportunity to
participate in a slam immediately preceding the poster session.

P5 micropapers will be allocated 5 minutes.

== Submission Procedure ==

All proposals should be submitted at http://www.tei-c.org/conftool/
by 15 May 2009.

You will need to create an account (i.e., username and password) in
order to file a submission. For each submission, you may upload files
to the system after you have completed filling out demographic data
and the abstract.

  * Individual paper or poster session proposals (including tool
    demonstrations):
    - Please submit a brief abstract (no more than 500 words) in the
      "Abstract" field.
    - Supporting materials (including graphics, multimedia, etc., or
      even a copy of the complete paper) may be uploaded after the
      initial abstract is submitted.

  * P5 micropaper: The procedure is the same as for an individual
    paper except that the abstract should be no more than 300 words.

  * Panel sessions:
    - The panel organizer submits an abstract for the entire session,
      listing the proposed papers, and explaining the organizing theme
      and rationale for the inclusion of the papers in no more than
      800 words in the "Abstract" field.
    - The panel members each submit a separate complete individual
      paper proposal; see above.
    The program committee reserves the right to accept papers
    submitted as part of a panel without accepting the whole panel.

All proposals will be reviewed by the program committee and selected
external reviewers. Conference submissions will be considered for a
conference proceedings. Further details on the submission process for
the conference proceedings will be forthcoming.

#1030

From: "tw33zer" <mstoef@...>
Date: Mon May 4, 2009 1:22 pm
Subject: RNG to XSD conversion issue

tw33zer

I have a conversion issue when going from RNG to XSD that I don't understand.  I
have a flat RNG with several simple element patterns  defined thusly ...

<define name="admin">
     <oneOrMore>
         <element name="p">
             <ref name="p.content"/>
         </element>
     </oneOrMore>
  </define>

     <define name="p.content">
         <optional>
             <attribute name="content-type">
                 <ref name="att.content-type"/>
             </attribute>
         </optional>
         <text/>
     </define>
     <define name="att.content-type">
         <data type="string"/>
     </define>


When I convert this to XSD, the resulting model for the p element is 'mixed',
but that's not what I was after...


  <xs:element name="p">
         <xs:complexType mixed="true">
             <xs:attributeGroup ref="p.content"/>
         </xs:complexType>
     </xs:element>

<xs:attributeGroup name="p.content">
         <xs:attribute name="content-type" type="xs:string"/>
     </xs:attributeGroup>

Anyway to avoid this outcome?

#1031

From: John Cowan <cowan@...>
Date: Mon May 4, 2009 2:13 pm
Subject: Re: RNG to XSD conversion issue

johnwcowan

tw33zer scripsit:

> When I convert this to XSD, the resulting model for the p element is
> 'mixed', but that's not what I was after...

Actually, it is.  Because your element has an attribute, it must be
modeled in XSD with a complex type, and the way to indicate that a complex
type may contain character content is with "mixed='true'".  It sounds a
little strange to call something "mixed content" when no child elements
are allowed, but that's just how it's done in the wacky world of XSD.

--
You escaped them by the will-death              John Cowan
and the Way of the Black Wheel.                 cowan@...
I could not.  --Great-Souled Sam                http://www.ccil.org/~cowan

#1032

From: "tw33zer" <mstoef@...>
Date: Mon May 4, 2009 2:32 pm
Subject: Re: RNG to XSD conversion issue

tw33zer

--- In rng-users@yahoogroups.com, John Cowan <cowan@...> wrote:
>
> tw33zer scripsit:
>
> > When I convert this to XSD, the resulting model for the p element is
> > 'mixed', but that's not what I was after...
>
> Actually, it is.  Because your element has an attribute, it must be
> modeled in XSD with a complex type, and the way to indicate that a complex
> type may contain character content is with "mixed='true'".  It sounds a
> little strange to call something "mixed content" when no child elements
> are allowed, but that's just how it's done in the wacky world of XSD.

I thought the preferred way to do this in XSD was

  <xs:complexType name="p.content">
         <xs:simpleContent>
             <xs:extension base="xs:string">
                 <xs:attributeGroup ref="att.content-type"/>
             </xs:extension>
         </xs:simpleContent>
     </xs:complexType>










>
> --
> You escaped them by the will-death              John Cowan
> and the Way of the Black Wheel.                 cowan@...
> I could not.  --Great-Souled Sam                http://www.ccil.org/~cowan
>

#1033

From: Norman Walsh <ndw@...>
Date: Mon May 4, 2009 2:40 pm
Subject: Re: DTD default value annotations?

normwalsh

John Cowan <cowan@...> writes:
> Norman Walsh scripsit:
>
>> I was under the impression that MSV did more, but I'll have to double-check.
>
> The commandline.html file bundled with MSV says it supports all three
> features at level 1 only (no infoset modification).  Consequently, it's
> only checking that a:defaultValue and a:documentation are used according
> to the rules; they still don't do anything.

Hmmm. Rats. I wonder if this will make getting XProc out of CR a
problem. The p:validate-with-relax-ng step includes an option to
support the attribute value modifications, but maybe since it's an
optional step it won't be a problem. Time will tell, I guess.

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@...> | Consistency requires you to be as
http://nwalsh.com/            | ignorant today as you were a year
                               | ago.--Bernard Berenson

#1034

From: John Cowan <cowan@...>
Date: Mon May 4, 2009 3:35 pm
Subject: Re: DTD default value annotations?

johnwcowan

Norman Walsh scripsit:

> Hmmm. Rats. I wonder if this will make getting XProc out of CR a
> problem. The p:validate-with-relax-ng step includes an option to
> support the attribute value modifications, but maybe since it's an
> optional step it won't be a problem. Time will tell, I guess.

The obvious approach is to whomp up an XSLT script that takes a
RELAX NG schema with a:defaultValue annotations and generates another
XSLT script that can process a document to add them.

--
That you can cover for the plentiful            John Cowan
and often gaping errors, misconstruals,         http://www.ccil.org/~cowan
and disinformation in your posts                cowan@...
through sheer volume --that is another
misconception.  --Mike to Peter

#1035

From: Norman Walsh <ndw@...>
Date: Mon May 4, 2009 3:53 pm
Subject: Re: DTD default value annotations?

normwalsh

John Cowan <cowan@...> writes:
> Norman Walsh scripsit:
>> Hmmm. Rats. I wonder if this will make getting XProc out of CR a
>> problem. The p:validate-with-relax-ng step includes an option to
>> support the attribute value modifications, but maybe since it's an
>> optional step it won't be a problem. Time will tell, I guess.
>
> The obvious approach is to whomp up an XSLT script that takes a
> RELAX NG schema with a:defaultValue annotations and generates another
> XSLT script that can process a document to add them.

That may be the obvious approach, but I'm not sure the XSLT script is
obvious, unless implementing a RELAX NG validator in XSLT seems
obvious to you, in which case, please feel free :-)

I suppose it doesn't actually have to do all of validation,
but...unless I'm being unusually thick on a Monday morning, it has to
do most of it in order to get the patterns right.

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@...> | If you're strong enough, there *are* no
http://nwalsh.com/            | precedents.--Scott Fitzgerald

#1036

From: John Cowan <cowan@...>
Date: Mon May 4, 2009 4:43 pm
Subject: Re: DTD default value annotations?

johnwcowan

Norman Walsh scripsit:

> That may be the obvious approach, but I'm not sure the XSLT script
> is obvious, unless implementing a RELAX NG validator in XSLT seems
> obvious to you, in which case, please feel free :-)

The problem's a little harder than I thought, but not as hard as you
think, and fortunately, Eric VdV has done the heavy lifting on it.

There is a strong semantic restriction on a:defaultValue that makes
it equivalent in power (modulo namespaces) to DTD default attributes.
For any given element-name/attribute-name combination, there can be at
most one distinct value of a:defaultValue in a schema, independent of
exactly which pattern matched them.  That is, there can be more than
one a:defaultValue in the schema, but they must all declare the same
value for that element-name/attribute-name combination.  Consequently,
all we have to do is find the a:attributeValue attributes and examine
their (extremely) local context in the schema.

Eric's script at
http://downloads.xmlschemata.org/relax-ng/utilities/simplification.xsl
converts ordinary XML-syntax RNG into simple-syntax RNG, which eliminates
random defines, includes, syntax variations, etc.  You'll have to patch
it not to discard a:defaultValue attributes, as currently it throws
away anything outside the rng: namespace.  So run the patched script
over the schema as the first step.

In the next step, look for this sort of thing in the output:

<element>
   <name ns="{NS name for foo}">bar</name>
   ...
   <attribute a:defaultValue="grault">
     <name ns={NS name for baz}">quux</name>
     ...
   </attribute>
   ...
</element>

and generate XSLT that will look for all foo:bar elements that don't
have attributes named baz:quux and generate them with the value grault.

> I suppose it doesn't actually have to do all of validation,

It doesn't have to validate at all.  If the use of a:defaultValue is
incompatible (which is the DTD Compatibility jargon for "invalid"),
the above may produce funny results, but if not, all will be well.

--
John Cowan            http://www.ccil.org/~cowan     cowan@...
                 if if = then then then = else else else = if;

#1037

From: John Cowan <cowan@...>
Date: Mon May 4, 2009 6:59 pm
Subject: Re: Re: RNG to XSD conversion issue

johnwcowan

tw33zer scripsit:

> I thought the preferred way to do this in XSD was
>
>  <xs:complexType name="p.content">
>         <xs:simpleContent>
>             <xs:extension base="xs:string">
>                 <xs:attributeGroup ref="att.content-type"/>
>             </xs:extension>
>         </xs:simpleContent>
>     </xs:complexType>

That's subtly different: it's a complex type whose content is a string,
as opposed to its content being text.  The validation will be the same,
just as the RELAX NG validation of <string/>, <xsd:string/>, and <text/>
are all the same (though not all are allowed in all contexts), but in
XSD the PSVI will be different.

--
John Cowan            http://www.ccil.org/~cowan     cowan@...
Uneasy lies the head that wears the Editor's hat! --Eddie Foirbeis Climo

#1038

From: "al_shopov" <al_shopov@...>
Date: Thu Apr 23, 2009 9:22 pm
Subject: Converting W3 schemas to RelaxNG ones

al_shopov

Hi everyone,
As far as I can see currently trang cannot convert xsd schemas to relax ng. Are
there any plans to add this in future? If there are no plans for this could
anyone suggest another tool for this?
Kind regards:
al_shopov

#1039

From: "veenaonnet" <veena_sarolkar@...>
Date: Thu May 7, 2009 1:22 pm
Subject: To validate "required" , unordered elements with same name

veenaonnet

Hi,

I want to validate an XML file containing following section. Requirement is to
validate "required", unordered fields with same name.

<Metadata>
         <App_Data App="Appl" Name="Version" Value="Version1" />
         <App_Data App="Appl" Name="Tier" Value="Tier1" />
          ---
</Metadata>

Here, Version and Tier are the required fields(Name attribute value is
pre-defined and fixed) and there can be other optional fields. Order of these
elements can change. As these elements have same name(App_Data), I am not able
to use "interleave" construct. Below is the part of rng file I am using.

In such a scenario. is there any way to validate the required field?
I am very new to Relax NG and just started working on it.

Waiting for a positive reply.

<define name="Metadata_Elements">
     <interleave>
	 <element name="App_Data">
		 <attribute name="App">
			 </text>
		 </attribute>
		 <attribute name="Name">
			 <value>Version</value>
		 </attribute>
		 <attribute name="Value">
			 <data type="string">
				 <param name="minLength">1</param>
			 </data>
		 </attribute>
	 </element>
         <element name="App_Data">
		 <attribute name="App">
			 </text>
		 </attribute>
		 <attribute name="Name">
			 <value>Tier</value>
		 </attribute>
		 <attribute name="Value">
			 <data type="string">
				 <param name="minLength">1</param>
			 </data>
		 </attribute>
	 </element>
	 <optional>
		 ----
	  </optional>
      </interleave>
</define>

#1040

From: Dave Pawson <dave.pawson@...>
Date: Thu May 7, 2009 5:59 pm
Subject: Re: Converting W3 schemas to RelaxNG ones

dpawson2000

2009/4/23 al_shopov <al_shopov@...>:
>
>
> Hi everyone,
> As far as I can see currently trang cannot convert xsd schemas to relax ng.
> Are there any plans to add this in future? If there are no plans for this
> could anyone suggest another tool for this?

Not unless you want to try?
Sun MSV is the tool I use.
https://msv.dev.java.net/

FILE FOR THE SUN RELAX NG CONVERTER
                         version 20060319
               Copyright (c) Sun Microsystems, 2001-2006
Document written by Kohsuke Kawaguchi (kohsuke.kawaguchi@...)
======================================================================

Sun RELAX NG Converter is a tool to convert schemas written in various
schema languages to their equivalent in RELAX NG.

It supports schemas written in XML DTD, RELAX Core, RELAX namespace,
TREX, W3C XML Schema, and RELAX NG itself.

This release includes software developed by the Apache Software
Foundation (http://www.apache.org/).

----------------------------------------------------------------------
USAGE
----------------------------------------------------------------------

To convert a schema written in either RELAX Core, RELAX namespace, TREX,
or W3C XML Schema, enter the following:

$ java -jar rngconv.jar myschema.xsd > result.rng

The converter detects the schema language automatically (except for XML
DTDs) and writes the result to "result.rng".

To convert an XML DTD, enter the following:

java -jar rngconv.jar -dtd myschema.dtd > result.rng

Note that you need the -dtd option.





HTH



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk