Re: [xml-dev] incompatible uses of XML Schema

["M. David Peterson" <m.david.x2x2x@gmail.com>]

Already a project in progress as part of the x2x2x.org family which,
as luck would have it is an independent non-profit so it could act
nicely as a host for this.  Heres a sample of what I mean:

http://trac.x2x2x.org/projects/justshowmethecode

This obviously doesnt fit what Dr. Kay was refering to directly but
with a new project created and published we can all put in our two
cents as to how the site should be indexed as the entire Trac
interface is built on top of a fairly sophisticated Wiki.

While not a perfect example, would an interface such as this be the
right thing for the job?  And what would be the prefered third tier
for this such that if we were to switch the UI to something like the
Saxon.NET XSLT 2.0-based Trac look-a-like we wouldnt then be left
scratching our heads as to whats going on.  My initial thought is:

xmlcommunity.x2x2x.org

but looking at that now looks rediculous.  Any ideas?  I should note
that I do own XMLWiki.com and have no immediate plans to use it so
would be more than happy to use this as the base domain instead.  We
could also focus on each W3C project as a third tier domain with its
own Trac project and interface into this project.  While it would take
a bit to get that set-up, if it would be  a good thing to do I dont
mind doing it.

Please let me know...

[PLEASE NOTE:] that the underlying "db" on this is Subversion and Trac
itself is written in Python and is completely open source and open for
contributions to extend into other areas of interest.  In actual fact
I have started and am nearly complete with the equivalent of the Trac
project written in XSLT 2.0 and running via Saxon.NET, using
Subversion for source-control/diff.  If any of you made the immediatte
realization that Subversion is written using the Apache Portable
Library and that there have been some HUGE problems with .NET and the
APL playing nicely, making it difficult at best to bring support for
Subversion to the CLI and via a standard .NET-based API that mirrors
the SVN command tree.  While I am unable to redistribute the current
set of SVNSharp DLL's that I have, (more on that via xsltblog.com
later today) there is a company in Europe who decided enough was
enough and, while you will have to build the source yourself for now
given the fact that:

a) we're all developers
b) building code is what we do and do well
c) this is 101 stuff so if your feeling lost when you hear the words
"build the source" maybe it's time you took a few seconds to sharpen
your skills a bit anyway ;

Denis Gervalle and his company, Softec, are the ones responsible for
this wonderful gift which has already taken away about 50% of the
development time I needed for 3 of my projects and have no doubt it
will save even more.  You can access the entry into the
SubversionSharp related projects via http://www.softec.st/ClrProjects
and contact Denis via webmaster@softec.st if you have any questions or
comments or want to find out if and when dll distribution will take
place.  I would love to give you a downloadable zip of the assemblies
I have but in taling with Denis he asked me to hold off from doing
this until he had finalized a few more things.  If he gives me the
green light to make them available via a stand alone archive file ( I
do have permission to redistribute with other projects that use these
libraries, just not on there own.)  One other thing that I want to
say...

THANK YOU DENIS!  

This was a TON of work and time that Denis has given to all of us and
I know that there are a lot of .NET developers out there who have been
eager to work with Subversion and yet simply could not...  you picked
a very difficult and

BTW... I've never announced the existence of the above
justshowmethecode project link as I didn't want to add yet another
site to maintain on top of everything else until I could cut my
current project set in half (meaning half of them completely delivered
in a 1.0 release.)  But if I would have thought about it for two more
seconds I would have realized that this isnt designed to be maintained
by one person and instead serve an entire project and its community. 
As such if you read the current intro and have a good feel for what
this project might become then please dont hesitate to start writing
things out via the Wiki such that we get used to the idea



On 4/21/05, Michael Kay <mike@saxonica.com> wrote:
> >
> > Perhaps vendors should be encouraged more to clearly state the limits
> > to the conformance of their main products pages:
> >    We don't support wildcards.
> >    We don't support xsi':type
> >    We don't support elements-in-elements
> >    We don't enforce unambiguity
> > etc.
> >
> 
> Or perhaps some independent party could put this information together in one
> place so that the rest of us can compare the products side-by-side.
> 
> Michael Kay
> http://www.saxonica.com/
> 
> 
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
> 
> 


-- 
<M:D/>

:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist