On Wed, Mar 26, 2008 at 08:48:32PM +0900, Evgeniy Khramtsov wrote:
> Dave Cridland wrote:
>
>> X.694! X.694!
>>
> X.694 is just a mapping XSD <-> ASN.1. What do you want to say?
Only xsd -> asn.1, not xsd <- asn.1. Right?
ermine
Dave Cridland wrote:
X.694 is just a mapping XSD <-> ASN.1. What do you want to say?
Exactly. So given XSD, you have ASN.1. In which case, it should
become apparent that there's nothing particularly magical about ASN.1
- it's not "self-validating", as such.
Sure it'd be nice to have nor
On Wed Mar 26 11:48:32 2008, Evgeniy Khramtsov wrote:
Dave Cridland wrote:
X.694! X.694!
X.694 is just a mapping XSD <-> ASN.1. What do you want to say?
Exactly. So given XSD, you have ASN.1. In which case, it should
become apparent that there's nothing particularly magical about ASN.1
Dave Cridland wrote:
X.694! X.694!
X.694 is just a mapping XSD <-> ASN.1. What do you want to say?
On Wed Mar 26 11:10:13 2008, Anastasia Gornostaeva wrote:
ASN.1! ASN.1!
X.694! X.694!
(With help from Kev, who inadvertantly pasted most of X.693 into jdev
to help remind me which X.69Y it was.)
Dave.
--
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
- acap://acap.dave.
On Sun, Mar 23, 2008 at 08:59:49PM -0600, Peter Saint-Andre wrote:
> All of our XML schemas are descriptive, not normative. If we really want
> to generate code or test in this way, we might want to create formal
> definitions that are normative. But I don't know if XSDs will get us
> there -- we
Gerhard Weis wrote:
Hi,
as you mention ASN.1 and XML.
I did some research recently about it, and I found a standard 1:1
mapping for ASN.1 and XML-Schema, and there is also
a ASN.1 encoding standard (extended XER or something like that) which
ensures, that a structure serialized to XML
is v
Hi,
as you mention ASN.1 and XML.
I did some research recently about it, and I found a standard 1:1
mapping for ASN.1 and XML-Schema, and there is also
a ASN.1 encoding standard (extended XER or something like that) which
ensures, that a structure serialized to XML
is valid according to the
Remko Tronçon wrote:
> Does anyone have any experience/thoughts on this?
I have a thought: you (along with EXI WG) are just reinventing ASN.1. Of
course, I know we cannot swith to ASN.1, so we have to reinvent a wheel.
It's sad.
Remko Tronçon wrote:
> Hi,
>
> I added another proposal to the GSoC page, entitled "XSD Schema Compiler".
> Here is a short description:
>
> "The most boring, time-consuming, and error-prone job of an XMPP
> client developer is writing code to parse XML stanzas, and turning
> them into datastruct
> I haven't looked, but there must be other XSD schema compilers. It would be
> interesting to see one dedicated to the generation of XMPP objects, but it
> would need to be very flexible to handle all the different languages and
> frameworks out there.
The biggest problem I foresee is that we ha
The RFC/XEP specs would be half of the input. The other half would be a
template per-language/parsing technique. The second part would be the
pluggable section that Remko refers to.
As a matter of interest there is an XSD to c#/vb complier provided by MS for
.Net. I think that there are one or
IMHO,
not sure what the input will be to such parser,
different XMPP libraries will likely use different xml
parsing techniques/representations like
DOM,SAX,PULL-Parsing,DOM4J,to name a few of them.
cheers,
pablo
--- Remko Tronçon <[EMAIL PROTECTED]> escribió:
> Hi,
>
> I added another prop
On Sat, Mar 22, 2008 at 01:08:21PM +0100, Remko Tronçon wrote:
> I added another proposal to the GSoC page, entitled "XSD Schema Compiler".
Sounds interesting. And probably useful, too.
--
Maciek Niedzielski
xmpp:[EMAIL PROTECTED]
Hi,
I added another proposal to the GSoC page, entitled "XSD Schema Compiler".
Here is a short description:
"The most boring, time-consuming, and error-prone job of an XMPP
client developer is writing code to parse XML stanzas, and turning
them into datastructures to be used by the rest of the co
15 matches
Mail list logo
