Home » Archived » XML Schema Definition (XSD) » What about the future of XSDEdit?
| What about the future of XSDEdit? [message #50360] |
Tue, 17 August 2004 08:47  |
Eclipse User |
|
|
|
Originally posted by: daniel_leo.163.com
Hi,
I am using XSDEdit to implement our xml schema editor. But there are some
shortages:
1) Only string type can be added
2) SubstitutionGroup can not be defined
3) baseType cannot be defined
These above shortages can be solved by modifying code, but the result
is somewhat ugly, there are very much strange info listed in combox
4) key&keyref cannot be defined
5) Annotation&Documentation can not be defined
These above shortages cannot be solved by modifying code.
And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
it will support the 4) and 5) feature? Will it become a fully-featured XML
schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
just shows the functions of XSD library?
So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
XMLSpy, that can make XSD be popular for most ternimal users.The question
is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
Thanks:)
Brs/
Daniel Leo
|
|
|
| Re: What about the future of XSDEdit? [message #50388 is a reply to message #50360] |
Tue, 17 August 2004 10:49  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Daniel,
The XSD Edit support has been used more for viewing schemas than for
full-function editing so there hasn't been much demand to improve all
the editing capabilities. The XSD Editor is really just a demonstration
of how the XSD capabilities can be used to build an editor. We've had
no time or resource to improve it beyond the current stage. Items 1-4
could be added fairly easily, but full support for 5 would require full
XML editing capability, which would be a lot of work. Our fall back is
that in the sample editor, it's always possible for users to edit by
changing text in the source view.
There are other tools that build on XSD's support. For example, WSAD
includes a schema editor that uses XSD. But given our resource
constraints, we will need to rely on others to build a full function XML
Schema editor like XML Spy. I believe there is an XML tools project in
the works that will have a mission to build a fully functional editor.
If there are improvements to XSD you'd like to prototype and contribute
back to the project, that would be welcome as well...
daniel leo wrote:
>Hi,
>I am using XSDEdit to implement our xml schema editor. But there are some
>shortages:
>
> 1) Only string type can be added
> 2) SubstitutionGroup can not be defined
> 3) baseType cannot be defined
> These above shortages can be solved by modifying code, but the result
>is somewhat ugly, there are very much strange info listed in combox
>
> 4) key&keyref cannot be defined
> 5) Annotation&Documentation can not be defined
> These above shortages cannot be solved by modifying code.
>
>And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
>it will support the 4) and 5) feature? Will it become a fully-featured XML
>schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
>just shows the functions of XSD library?
>
>So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
>XMLSpy, that can make XSD be popular for most ternimal users.The question
>is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
>
>Thanks:)
>
>
>Brs/
>Daniel Leo
>
>
>
|
|
|
| Re: What about the future of XSDEdit? [message #50415 is a reply to message #50388] |
Tue, 17 August 2004 11:34 |
| Eclipse User |
|
|
|
Originally posted by: daniel_leo.163.com
Thank you very much:)
Brs/
Daniel Leo
Ed Merks wrote:
> Daniel,
> The XSD Edit support has been used more for viewing schemas than for
> full-function editing so there hasn't been much demand to improve all
> the editing capabilities. The XSD Editor is really just a demonstration
> of how the XSD capabilities can be used to build an editor. We've had
> no time or resource to improve it beyond the current stage. Items 1-4
> could be added fairly easily, but full support for 5 would require full
> XML editing capability, which would be a lot of work. Our fall back is
> that in the sample editor, it's always possible for users to edit by
> changing text in the source view.
> There are other tools that build on XSD's support. For example, WSAD
> includes a schema editor that uses XSD. But given our resource
> constraints, we will need to rely on others to build a full function XML
> Schema editor like XML Spy. I believe there is an XML tools project in
> the works that will have a mission to build a fully functional editor.
> If there are improvements to XSD you'd like to prototype and contribute
> back to the project, that would be welcome as well...
> daniel leo wrote:
> >Hi,
> >I am using XSDEdit to implement our xml schema editor. But there are some
> >shortages:
> >
> > 1) Only string type can be added
> > 2) SubstitutionGroup can not be defined
> > 3) baseType cannot be defined
> > These above shortages can be solved by modifying code, but the result
> >is somewhat ugly, there are very much strange info listed in combox
> >
> > 4) key&keyref cannot be defined
> > 5) Annotation&Documentation can not be defined
> > These above shortages cannot be solved by modifying code.
> >
> >And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
> >it will support the 4) and 5) feature? Will it become a fully-featured XML
> >schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
> >just shows the functions of XSD library?
> >
> >So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
> >XMLSpy, that can make XSD be popular for most ternimal users.The question
> >is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
> >
> >Thanks:)
> >
> >
> >Brs/
> >Daniel Leo
> >
> >
> >
|
|
|
| Re: What about the future of XSDEdit? [message #51241 is a reply to message #50360] |
Mon, 23 August 2004 19:37 |
 Dave Carlson
Messages: 402
Registered: July 2009 |
Senior Member |
|
|
Daniel,
Check out the new Eclipse Web Tools project. It is still in a formative
stage digesting initial open source contributions from IBM and Object Web,
but the IBM contribution includes a nice first cut at an XSD editor and an
XML document editor. The graphical view of the XSD editor is very similar
to that from other commercial XML Schema editors. I believe this
contribtion was extracted from a subset of IBM's WSAD code, so it is already
quite mature.
I have not had a chance to review the source code, but I believe the editor
is based on the EMF/XSD model, although maybe not the EMF generated editor.
The source is not yet in CVS, but zip files of the initial source
contribution are available for download.
Regards,
Dave Carlson
"daniel leo" <daniel_leo@163.com> wrote in message
news:cfsgn8$rl9$1@eclipse.org...
> Hi,
> I am using XSDEdit to implement our xml schema editor. But there are some
> shortages:
>
> 1) Only string type can be added
> 2) SubstitutionGroup can not be defined
> 3) baseType cannot be defined
> These above shortages can be solved by modifying code, but the result
> is somewhat ugly, there are very much strange info listed in combox
>
> 4) key&keyref cannot be defined
> 5) Annotation&Documentation can not be defined
> These above shortages cannot be solved by modifying code.
>
> And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
> it will support the 4) and 5) feature? Will it become a fully-featured XML
> schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
> just shows the functions of XSD library?
>
> So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
> XMLSpy, that can make XSD be popular for most ternimal users.The question
> is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
>
> Thanks:)
>
>
> Brs/
> Daniel Leo
>
|
|
|
| Re: What about the future of XSDEdit? [message #590225 is a reply to message #50360] |
Tue, 17 August 2004 10:49 |
Ed Merks
Messages: 33142
Registered: July 2009 |
Senior Member |
|
|
Daniel,
The XSD Edit support has been used more for viewing schemas than for
full-function editing so there hasn't been much demand to improve all
the editing capabilities. The XSD Editor is really just a demonstration
of how the XSD capabilities can be used to build an editor. We've had
no time or resource to improve it beyond the current stage. Items 1-4
could be added fairly easily, but full support for 5 would require full
XML editing capability, which would be a lot of work. Our fall back is
that in the sample editor, it's always possible for users to edit by
changing text in the source view.
There are other tools that build on XSD's support. For example, WSAD
includes a schema editor that uses XSD. But given our resource
constraints, we will need to rely on others to build a full function XML
Schema editor like XML Spy. I believe there is an XML tools project in
the works that will have a mission to build a fully functional editor.
If there are improvements to XSD you'd like to prototype and contribute
back to the project, that would be welcome as well...
daniel leo wrote:
>Hi,
>I am using XSDEdit to implement our xml schema editor. But there are some
>shortages:
>
> 1) Only string type can be added
> 2) SubstitutionGroup can not be defined
> 3) baseType cannot be defined
> These above shortages can be solved by modifying code, but the result
>is somewhat ugly, there are very much strange info listed in combox
>
> 4) key&keyref cannot be defined
> 5) Annotation&Documentation can not be defined
> These above shortages cannot be solved by modifying code.
>
>And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
>it will support the 4) and 5) feature? Will it become a fully-featured XML
>schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
>just shows the functions of XSD library?
>
>So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
>XMLSpy, that can make XSD be popular for most ternimal users.The question
>is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
>
>Thanks:)
>
>
>Brs/
>Daniel Leo
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: What about the future of XSDEdit? [message #590242 is a reply to message #50388] |
Tue, 17 August 2004 11:34 |
| Eclipse User |
|
|
|
Originally posted by: daniel_leo.163.com
Thank you very much:)
Brs/
Daniel Leo
Ed Merks wrote:
> Daniel,
> The XSD Edit support has been used more for viewing schemas than for
> full-function editing so there hasn't been much demand to improve all
> the editing capabilities. The XSD Editor is really just a demonstration
> of how the XSD capabilities can be used to build an editor. We've had
> no time or resource to improve it beyond the current stage. Items 1-4
> could be added fairly easily, but full support for 5 would require full
> XML editing capability, which would be a lot of work. Our fall back is
> that in the sample editor, it's always possible for users to edit by
> changing text in the source view.
> There are other tools that build on XSD's support. For example, WSAD
> includes a schema editor that uses XSD. But given our resource
> constraints, we will need to rely on others to build a full function XML
> Schema editor like XML Spy. I believe there is an XML tools project in
> the works that will have a mission to build a fully functional editor.
> If there are improvements to XSD you'd like to prototype and contribute
> back to the project, that would be welcome as well...
> daniel leo wrote:
> >Hi,
> >I am using XSDEdit to implement our xml schema editor. But there are some
> >shortages:
> >
> > 1) Only string type can be added
> > 2) SubstitutionGroup can not be defined
> > 3) baseType cannot be defined
> > These above shortages can be solved by modifying code, but the result
> >is somewhat ugly, there are very much strange info listed in combox
> >
> > 4) key&keyref cannot be defined
> > 5) Annotation&Documentation can not be defined
> > These above shortages cannot be solved by modifying code.
> >
> >And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
> >it will support the 4) and 5) feature? Will it become a fully-featured XML
> >schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
> >just shows the functions of XSD library?
> >
> >So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
> >XMLSpy, that can make XSD be popular for most ternimal users.The question
> >is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
> >
> >Thanks:)
> >
> >
> >Brs/
> >Daniel Leo
> >
> >
> >
|
|
|
| Re: What about the future of XSDEdit? [message #590743 is a reply to message #50360] |
Mon, 23 August 2004 19:37 |
Dave Carlson
Messages: 402
Registered: July 2009 |
Senior Member |
|
|
Daniel,
Check out the new Eclipse Web Tools project. It is still in a formative
stage digesting initial open source contributions from IBM and Object Web,
but the IBM contribution includes a nice first cut at an XSD editor and an
XML document editor. The graphical view of the XSD editor is very similar
to that from other commercial XML Schema editors. I believe this
contribtion was extracted from a subset of IBM's WSAD code, so it is already
quite mature.
I have not had a chance to review the source code, but I believe the editor
is based on the EMF/XSD model, although maybe not the EMF generated editor.
The source is not yet in CVS, but zip files of the initial source
contribution are available for download.
Regards,
Dave Carlson
"daniel leo" <daniel_leo@163.com> wrote in message
news:cfsgn8$rl9$1@eclipse.org...
> Hi,
> I am using XSDEdit to implement our xml schema editor. But there are some
> shortages:
>
> 1) Only string type can be added
> 2) SubstitutionGroup can not be defined
> 3) baseType cannot be defined
> These above shortages can be solved by modifying code, but the result
> is somewhat ugly, there are very much strange info listed in combox
>
> 4) key&keyref cannot be defined
> 5) Annotation&Documentation can not be defined
> These above shortages cannot be solved by modifying code.
>
> And I am wondering what is the future strategy of XSDEdit&XSDEditor. Will
> it will support the 4) and 5) feature? Will it become a fully-featured XML
> schema editor, like XMLSpy ? Or XSDEdit&XSDEditor is just a prototype that
> just shows the functions of XSD library?
>
> So if the XSDEdit/XSDEditor can support XML schema editing perfectly,like
> XMLSpy, that can make XSD be popular for most ternimal users.The question
> is what is the future of XSDEdit, or what is the roadmap of XSDEdit?
>
> Thanks:)
>
>
> Brs/
> Daniel Leo
>
|
|
|
Goto Forum:
Current Time: Sat Apr 27 04:43:49 GMT 2024
Powered by FUDForum. Page generated in 0.03846 seconds |
] 
Search
Help
Register
Login
Home
