You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Elena Litani <hl...@jtcsv.com> on 2001/02/21 16:30:58 UTC
Notations in schema (readme!)
Hi, all,
We are planning to implement support for schemas <notation> in upcoming
Xerces Release [see
http://www.w3.org/TR/2000/CR-xmlschema-1-20001024/#declare-notation].
However, DOM & SAX don't provide APIs for exposing Schema notations to
applications. Note that schema notations are different from DTD
notations, because they have a namespace.
Questions:
----------
1) Is anybody using schema notations or plan to use those? Can people
live for a couple of months without notations? DOM level 3 should
(hopefully) take this into consideration in CM models specs.
2) Otherwise we can try the following:
Exposing schema notations via DOM: use doctype.getNotations().
Exposing schema notations via SAX: yourDTDHandler.notationDecl(name,
pubid, sysid).
For SAX & DOM, the information application can get is: notation_name,
systemId, publicId. However, you won't be able to get NAMESPACE, nor
differentiate between notations from different namespaces. That might
mean that if you have multiple notations with same name but from
different namespaces - parser will choke.
Let us know what do you think.
Elena
Timeline for nullable feature..??
Posted by René Jensen <lu...@tbkol.dk>.
Hi there
I´m new to this list, and have looked in the archives (witch isn´t quite new).
And I haven't found anything about this...
I was trying to validate a dokument using the nullable feature and it didn't
work, after a while a saw is on the "feature NOT supported"-list. My question
is, are there plans for implementing this feature in the near future(next
release) or is it something that I have to make some kind of workaround for
myself.
(I was thinking of making every type a string restricted by a regular
expression, grouping it all and give it a "?" like: (([A-Fa-f]{2}\.){5}[A-Fa-
f])? for a MAC-adress element that can be empty....)
_\|/_
(@ @)
---oOOo-(_)-oOOo---
René Jensen
lundeman@tbkol.dk
Re: Notations in schema (readme!)
Posted by Andy Clark <an...@apache.org>.
Ted Leung wrote:
> Could you e-mail me a zip of the site and I'll see what I can do?
> I was kind of putting off learning Stylebook for C2. But C2 seems
> to be quite far behind schedule....
The Xerces2 design docs are in CVS on the "xerces_j_2" branch
in the java/design directory.
--
Andy Clark * IBM, TRL - Japan * andyc@apache.org
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Hey all,
I hate to be redundant here :-), but I am hoping the key to getting feedback
is persistence. :-) In looking through the source code, I am not seeing
where the SAXParser is being closed when an exception is thrown out of the
parsing of the XML file. (i.e. the parse(String uri) method in the
XMLReader class is interrupted by the throwing of an Exception). This is
directly causing a problem in my application because the XMLReader is not
letting go of the file when this Exception is thrown, which prevents further
file operations (like moving the file). If I am wrong in this observation,
if someone would please correct me, I would be greatly appreciative. If I
am right, then the file either needs to be closed when the Exception is
thrown, OR there needs to be a method available that allows explicit closing
of the XML file.
Thanks!
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Tuesday, February 27, 2001 11:04 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
Has anyone been able to verify this problem, or have any ideas on the
solution?
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 7:48 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Hey all,
I hate to be redundant here :-), but I am hoping the key to getting feedback
is persistence. :-) In looking through the source code, I am not seeing
where the SAXParser is being closed when an exception is thrown out of the
parsing of the XML file. (i.e. the parse(String uri) method in the
XMLReader class is interrupted by the throwing of an Exception). This is
directly causing a problem in my application because the XMLReader is not
letting go of the file when this Exception is thrown, which prevents further
file operations (like moving the file). If I am wrong in this observation,
if someone would please correct me, I would be greatly appreciative. If I
am right, then the file either needs to be closed when the Exception is
thrown, OR there needs to be a method available that allows explicit closing
of the XML file.
Thanks!
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Tuesday, February 27, 2001 11:04 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
Has anyone been able to verify this problem, or have any ideas on the
solution?
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 7:48 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Has anyone been able to verify this problem, or have any ideas on the
solution?
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 7:48 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Has anyone been able to verify this problem, or have any ideas on the
solution?
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 7:48 PM
To: xerces-j-user@xml.apache.org; xerces-j-dev@xml.apache.org
Subject: RE: Explicit file closing
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Blank Namespaces Prefix
Posted by Arnaud Le Hors <le...@us.ibm.com>.
Brad is correct.
--
Arnaud Le Hors - IBM Cupertino, XML Strategy Group
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
RE: Blank Namespaces Prefix
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Haneef,
I believe the behavior you are seeing is accurate according to the XML
specification. What you are actually referring to by "blank" name spaces is
actually namespace defaulting. Default namespaces apply to the element
where declared and all elements with no prefix within the content of that
element. However, quoting from section 5.2 of the "Namespaces in XML" W3C
recommendation, "Note that default namespaces do not apply directly to
attributes." Therefore, I believe the "version" element in your second
example isn't associated with the "urn:uddi-org:api" namespace, and hence
the result with the getAttributeNS method.
If you want to check this out in a little more detail, here's a link:
http://www.w3.org/TR/1999/REC-xml-names-19990114/
Enjoy!
BradO
-----Original Message-----
From: Haneef Ali [mailto:haneef_ali@rgellx30.rgv.hp.com]
Sent: Friday, February 23, 2001 8:32 PM
To: xerces-j-user@xml.apache.org
Subject: Blank Namespaces Prefix
Hi all,
Looks like java parser is not handling blank name spaces.
Eg:
<X:discard_authToken generic="1.0" X:version="1.0"
xmlns:X="urn:uddi-org:api">
<X:authInfo> token </X:authInfo>
</X:discard_authToken>
Element.getAttributeNS("urn:uddi-org:api" , "version") -- works
but
<discard_authToken generic="1.0" version="1.0" xmlns="urn:uddi-org:api">
<authInfo> token </authInfo>
</discard_authToken>
Element.getAttributeNS("urn:uddi-org:api" , "version") -- doesn't work.
Iam I missing some thing here. Please let me know
Thanks
Haneef
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Blank Namespaces Prefix
Posted by Haneef Ali <ha...@rgellx30.rgv.hp.com>.
Hi all,
Looks like java parser is not handling blank name spaces.
Eg:
<X:discard_authToken generic="1.0" X:version="1.0"
xmlns:X="urn:uddi-org:api">
<X:authInfo> token </X:authInfo>
</X:discard_authToken>
Element.getAttributeNS("urn:uddi-org:api" , "version") -- works
but
<discard_authToken generic="1.0" version="1.0" xmlns="urn:uddi-org:api">
<authInfo> token </authInfo>
</discard_authToken>
Element.getAttributeNS("urn:uddi-org:api" , "version") -- doesn't work.
Iam I missing some thing here. Please let me know
Thanks
Haneef
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
RE: Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
I was looking through the source on this in the
org.apache.xerces.framework.XMLParser class, and it appears that the
parse(String systemId) method does not close the InputSource if an Exception
is thrown -- it appears parsing has to end gracefully for this to happen.
This would also be consistent with the results I am getting below (if an
Exception, the file is locked, if it ends gracefully, the file is free).
Perhaps I am overlooking something, but the parse method isn't inside a
try-catch. If I have read this correctly, I would throw the call to the
parse(InputSource is) that resides inside the parse(String systemId) method
inside a try-catch block with a finally that closes the InputSource. Let me
know if this seems right -- perhaps I missed something.
Thanks in advance,
BradO
-----Original Message-----
From: Brad O'Hearne [mailto:cabodog@megapathdsl.net]
Sent: Friday, February 23, 2001 6:55 PM
To: xerces-j-user@xml.apache.org
Subject: Explicit file closing
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Explicit file closing
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Hello all,
I ran into an interesting problem tonight. I am using a SAX2 parser. My
app moves my xml file to a new directory immediately following parsing, or
if parsing is aborted after a SAXException is thrown. I am getting an
access conflict on the file trying to move my file following a SAXException
being thrown and parsing being aborted. I have checked the XMLReader
interface and noticed that there are no methods declared for explicitly
closing the underlying file. Is there some way for the app to explicitly
control the closing of the file, and if not, should this be added? (I guess
another question is when exactly is the file being closed now?)
Thanks in advance for help!
BradO
Re: Notations in schema (readme!)
Posted by Ted Leung <tw...@sauria.com>.
----- Original Message -----
From: "Andy Clark" <an...@apache.org>
To: <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 11:52 PM
Subject: Re: Notations in schema (readme!)
> Ted Leung wrote:
> > I could have sworn there was a part of XNI for the grammar. I
> > just tried to go to your pages from xml.apache.org and couldn't
> > find the link. Is this another website mess up?
>
> Currently, I'm only thinking of XNI as the information set
> communicated by the interfaces. So that's only document and
> DTD information, not grammar information. However, there are
> grammar related definitions grouped in with the Xerces2
> design.html file but these are just implementation details.
> The grammar object defined as part of this is a compiled
> form and doesn't care too much about the differences
> between DTD and Schema notations.
Okay, this sounds reasonable.
> My Xerces2 pages are off of my personal Apache web site so
> you won't find them on xml.apache.org. Someone said that
> they were going to work on moving those pages over but it
> hasn't happened. Do you want to setup the Xerces2 section
> of the site and move that material over?
Could you e-mail me a zip of the site and I'll see what I can do?
I was kind of putting off learning Stylebook for C2. But C2 seems
to be quite far behind schedule....
> --
> Andy Clark * IBM, TRL - Japan * andyc@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
Re: Notations in schema (readme!)
Posted by Andy Clark <an...@apache.org>.
Ted Leung wrote:
> I could have sworn there was a part of XNI for the grammar. I
> just tried to go to your pages from xml.apache.org and couldn't
> find the link. Is this another website mess up?
Currently, I'm only thinking of XNI as the information set
communicated by the interfaces. So that's only document and
DTD information, not grammar information. However, there are
grammar related definitions grouped in with the Xerces2
design.html file but these are just implementation details.
The grammar object defined as part of this is a compiled
form and doesn't care too much about the differences
between DTD and Schema notations.
My Xerces2 pages are off of my personal Apache web site so
you won't find them on xml.apache.org. Someone said that
they were going to work on moving those pages over but it
hasn't happened. Do you want to setup the Xerces2 section
of the site and move that material over?
--
Andy Clark * IBM, TRL - Japan * andyc@apache.org
Re: Notations in schema (readme!)
Posted by Ted Leung <tw...@sauria.com>.
I could have sworn there was a part of XNI for the grammar. I
just tried to go to your pages from xml.apache.org and couldn't
find the link. Is this another website mess up?
Ted
----- Original Message -----
From: "Andy Clark" <an...@apache.org>
To: <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 7:45 PM
Subject: Re: Notations in schema (readme!)
> Ted Leung wrote:
> > Andy, what about XNI? Are we covered?
>
> I don't think this affects XNI directly since it's grammar
> information and not part of the streaming information set.
>
> --
> Andy Clark * IBM, TRL - Japan * andyc@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
Re: Notations in schema (readme!)
Posted by Andy Clark <an...@apache.org>.
Ted Leung wrote:
> Andy, what about XNI? Are we covered?
I don't think this affects XNI directly since it's grammar
information and not part of the streaming information set.
--
Andy Clark * IBM, TRL - Japan * andyc@apache.org
Re: Notations in schema (readme!)
Posted by Ted Leung <tw...@sauria.com>.
----- Original Message -----
From: "Arnaud Le Hors" <le...@us.ibm.com>
To: <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 4:34 PM
Subject: Re: Notations in schema (readme!)
> Andy Clark wrote:
> >
> > Elena Litani wrote:
> > > Exposing schema notations via DOM: use doctype.getNotations().
> > > Exposing schema notations via SAX:
yourDTDHandler.notationDecl(name,
> >
> > But is this really what we're supposed to do for Schema
> > information? The Schema notation declarations are not
> > contained within the doctype and aren't part of the DTD.
>
> I think not. The DOM Level 3 Content Model API provides for accessing
> those, so I suggest we just do that. For SAX on the other hand I just
> don't know.
Sounds like time for SAX3 (groan).
Andy, what about XNI? Are we covered?
Ted
Re: Notations in schema (readme!)
Posted by Arnaud Le Hors <le...@us.ibm.com>.
Andy Clark wrote:
>
> Elena Litani wrote:
> > Exposing schema notations via DOM: use doctype.getNotations().
> > Exposing schema notations via SAX: yourDTDHandler.notationDecl(name,
>
> But is this really what we're supposed to do for Schema
> information? The Schema notation declarations are not
> contained within the doctype and aren't part of the DTD.
I think not. The DOM Level 3 Content Model API provides for accessing
those, so I suggest we just do that. For SAX on the other hand I just
don't know.
--
Arnaud Le Hors - IBM Cupertino, XML Strategy Group
Re: Notations in schema (readme!)
Posted by Andy Clark <an...@apache.org>.
Elena Litani wrote:
> Exposing schema notations via DOM: use doctype.getNotations().
> Exposing schema notations via SAX: yourDTDHandler.notationDecl(name,
But is this really what we're supposed to do for Schema
information? The Schema notation declarations are not
contained within the doctype and aren't part of the DTD.
--
Andy Clark * IBM, TRL - Japan * andyc@apache.org
Re: Getting involved in Xerces Development
Posted by Ted Leung <tw...@sauria.com>.
Hi Elena,
Sometimes there are questions that people have that they don't want
to air in the public list. I was only trying to provide a way for Brad
to talk to someone in confidence if he wanted to.
As far as current development of Xerces-J goes, you should start
to see code and patches from me in the near future. In case you
hadn't noticed, I've been spending a lot of time recently trying to
get this project to be a little more open to developers who aren't
employed by Sun or IBM. I've tried to do that earlier this summer
without much success. This round is my last attempt at doing so. If
I fail, I'll go away, and the Sun and IBM developers can have their
closed source masquerading as open source project.
Ted
----- Original Message -----
From: "Elena Litani" <hl...@jtcsv.com>
To: <xe...@xml.apache.org>
Cc: <ca...@megapathdsl.net>; <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 10:23 AM
Subject: Re: Getting involved in Xerces Development
> Hi, Ted,
>
> I think we all agreed that since it is an open source project we are
> going to talk about development all together.
>
> Thus, I would strongly suggest to Brad to post his questions on
> xerces-j-dev list. Current development for XercesJ is mostly done by
> Lisa Martin, Neil Graham, Arnaud LeHors, Andy Clark, Edwin Goei and
> myself (sorry if I missed somebody). I believe, those are the people
> Brad should talk to.
>
> Elena
>
> Ted Leung wrote:
> >
> > Brad,
> >
> > You can e-mail me at twl@sauria.com.
> >
> > Ted Leung
> > ----- Original Message -----
> > From: "Brad O'Hearne" <ca...@megapathdsl.net>
> > To: <xe...@xml.apache.org>
> > Sent: Wednesday, February 21, 2001 9:43 AM
> > Subject: Getting involved in Xerces Development
> >
> > > Is there one of the developers/leaders on this Xerces project that
would
> > be
> > > interested in fielding a few questions off-line that I have about
getting
> > > involved with the development of Xerces?
> > >
> > > Brad
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
Re: Getting involved in Xerces Development
Posted by Ted Leung <tw...@sauria.com>.
Hi Elena,
Sometimes there are questions that people have that they don't want
to air in the public list. I was only trying to provide a way for Brad
to talk to someone in confidence if he wanted to.
As far as current development of Xerces-J goes, you should start
to see code and patches from me in the near future. In case you
hadn't noticed, I've been spending a lot of time recently trying to
get this project to be a little more open to developers who aren't
employed by Sun or IBM. I've tried to do that earlier this summer
without much success. This round is my last attempt at doing so. If
I fail, I'll go away, and the Sun and IBM developers can have their
closed source masquerading as open source project.
Ted
----- Original Message -----
From: "Elena Litani" <hl...@jtcsv.com>
To: <xe...@xml.apache.org>
Cc: <ca...@megapathdsl.net>; <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 10:23 AM
Subject: Re: Getting involved in Xerces Development
> Hi, Ted,
>
> I think we all agreed that since it is an open source project we are
> going to talk about development all together.
>
> Thus, I would strongly suggest to Brad to post his questions on
> xerces-j-dev list. Current development for XercesJ is mostly done by
> Lisa Martin, Neil Graham, Arnaud LeHors, Andy Clark, Edwin Goei and
> myself (sorry if I missed somebody). I believe, those are the people
> Brad should talk to.
>
> Elena
>
> Ted Leung wrote:
> >
> > Brad,
> >
> > You can e-mail me at twl@sauria.com.
> >
> > Ted Leung
> > ----- Original Message -----
> > From: "Brad O'Hearne" <ca...@megapathdsl.net>
> > To: <xe...@xml.apache.org>
> > Sent: Wednesday, February 21, 2001 9:43 AM
> > Subject: Getting involved in Xerces Development
> >
> > > Is there one of the developers/leaders on this Xerces project that
would
> > be
> > > interested in fielding a few questions off-line that I have about
getting
> > > involved with the development of Xerces?
> > >
> > > Brad
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
Re: Getting involved in Xerces Development
Posted by Elena Litani <hl...@jtcsv.com>.
Hi, Ted,
I think we all agreed that since it is an open source project we are
going to talk about development all together.
Thus, I would strongly suggest to Brad to post his questions on
xerces-j-dev list. Current development for XercesJ is mostly done by
Lisa Martin, Neil Graham, Arnaud LeHors, Andy Clark, Edwin Goei and
myself (sorry if I missed somebody). I believe, those are the people
Brad should talk to.
Elena
Ted Leung wrote:
>
> Brad,
>
> You can e-mail me at twl@sauria.com.
>
> Ted Leung
> ----- Original Message -----
> From: "Brad O'Hearne" <ca...@megapathdsl.net>
> To: <xe...@xml.apache.org>
> Sent: Wednesday, February 21, 2001 9:43 AM
> Subject: Getting involved in Xerces Development
>
> > Is there one of the developers/leaders on this Xerces project that would
> be
> > interested in fielding a few questions off-line that I have about getting
> > involved with the development of Xerces?
> >
> > Brad
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Getting involved in Xerces Development
Posted by Elena Litani <hl...@jtcsv.com>.
Hi, Ted,
I think we all agreed that since it is an open source project we are
going to talk about development all together.
Thus, I would strongly suggest to Brad to post his questions on
xerces-j-dev list. Current development for XercesJ is mostly done by
Lisa Martin, Neil Graham, Arnaud LeHors, Andy Clark, Edwin Goei and
myself (sorry if I missed somebody). I believe, those are the people
Brad should talk to.
Elena
Ted Leung wrote:
>
> Brad,
>
> You can e-mail me at twl@sauria.com.
>
> Ted Leung
> ----- Original Message -----
> From: "Brad O'Hearne" <ca...@megapathdsl.net>
> To: <xe...@xml.apache.org>
> Sent: Wednesday, February 21, 2001 9:43 AM
> Subject: Getting involved in Xerces Development
>
> > Is there one of the developers/leaders on this Xerces project that would
> be
> > interested in fielding a few questions off-line that I have about getting
> > involved with the development of Xerces?
> >
> > Brad
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-user-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Getting involved in Xerces Development
Posted by Ted Leung <tw...@sauria.com>.
Brad,
You can e-mail me at twl@sauria.com.
Ted Leung
----- Original Message -----
From: "Brad O'Hearne" <ca...@megapathdsl.net>
To: <xe...@xml.apache.org>
Sent: Wednesday, February 21, 2001 9:43 AM
Subject: Getting involved in Xerces Development
> Is there one of the developers/leaders on this Xerces project that would
be
> interested in fielding a few questions off-line that I have about getting
> involved with the development of Xerces?
>
> Brad
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
Getting involved in Xerces Development
Posted by Brad O'Hearne <ca...@megapathdsl.net>.
Is there one of the developers/leaders on this Xerces project that would be
interested in fielding a few questions off-line that I have about getting
involved with the development of Xerces?
Brad