[JBoss JIRA] Created: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
8:56 a.m.
XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Reporter: John Doyle
Assignee: John Doyle
The main case for this is REST services. REST services do not have a standard description
mechanism like WSDL for SOAP services. The inputs and outputs of the service might be
documented in a HTML help page, with sample XML documents, with WADL, etc. Hand modeling
is too difficult, so we need to come up with other assists. The solution is probably a
mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:32 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
John Doyle commented on TEIIDDES-119:
-------------------------------------
WSDL 2.0 is supporting REST.
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Reporter: John Doyle
Assignee: John Doyle
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
Greg Haber commented on TEIIDDES-119:
-------------------------------------
Other than inst2xsd, another great tool for building XSDs from sample XMLs is trang
(http://www.thaiopensource.com/relaxng/trang.html). If we go the best practices approach
for producing we should discuss both trang and inst2xsd.
What would be really slick would be to have one of these tools under the covers in
Designer (both have BSD-style licenses so we could do this). inst2xsd (part of Apache
XMLBeans) is designed to be called either from the command line or programmatically (see
http://svn.apache.org/viewvc/xmlbeans/trunk/src/tools/org/apache/xmlbeans...)
- we could hide it behind a Designer import wizard.
And, on the topic of REST services, one thing we should doc clearly is how to deal with
best-case REST services (those where the input parameters are encoded in the URL, and an
XSD is available to describe the returned XML doc). One such example is the Yahoo
Geocoding service (http://developer.yahoo.com/maps/rest/V1/geocode.html).
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Reporter: John Doyle
Assignee: John Doyle
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
John Doyle commented on TEIIDDES-119:
-------------------------------------
Thanks Greg,
we should probably consider relaxng as a source of metadata as well.
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Reporter: John Doyle
Assignee: John Doyle
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
Barry LaFond updated TEIIDDES-119:
----------------------------------
Fix Version/s: Future
Affects Version/s: 6.0.0
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: John Doyle
Fix For: Future
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
John Doyle updated TEIIDDES-119:
--------------------------------
Fix Version/s: 6.2.0
(was: Future)
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: John Doyle
Fix For: 6.2.0
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://jira.jboss.org/jira/browse/TEIIDDES-119?page=com.atlassian.jira.p...
]
John Doyle updated TEIIDDES-119:
--------------------------------
Fix Version/s: Future
(was: 6.2.0)
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://jira.jboss.org/jira/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: John Doyle
Fix For: Future
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 p.m.
New subject: [JBoss JIRA] Assigned: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://issues.jboss.org/browse/TEIIDDES-119?page=com.atlassian.jira.plug...
]
John Doyle reassigned TEIIDDES-119:
-----------------------------------
Assignee: (was: John Doyle)
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://issues.jboss.org/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Fix For: Future
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://issues.jboss.org/browse/TEIIDDES-119?page=com.atlassian.jira.plug...
]
Barry LaFond updated TEIIDDES-119:
----------------------------------
Fix Version/s: 7.7.1
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://issues.jboss.org/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Fix For: Future, 7.7.1
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
New subject: [JBoss JIRA] (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://issues.jboss.org/browse/TEIIDDES-119?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-119:
---------------------------------------
I think this issue may be somewhat solved by the exclusive use of the XMLTABLE() function
AND the WS procedures that can now be generated from New Model wizard AND through the
Import > Teiid Designer > File Source (XML) >> Source and View Models option.
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://issues.jboss.org/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Fix For: 7.7.1, Future
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://issues.jboss.org/browse/TEIIDDES-119?page=com.atlassian.jira.plug...
]
Barry LaFond updated TEIIDDES-119:
----------------------------------
Fix Version/s: (was: Future)
Assignee: Ted Jones
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://issues.jboss.org/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: Ted Jones
Fix For: 7.7.1
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [JBoss JIRA] (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.
[
https://issues.jboss.org/browse/TEIIDDES-119?page=com.atlassian.jira.plug...
]
Barry LaFond updated TEIIDDES-119:
----------------------------------
Fix Version/s: 8.0
(was: 7.7.1)
XML-Relaional modeling needs to be easier for sources that do not
provide an XSD.
---------------------------------------------------------------------------------
Key: TEIIDDES-119
URL: https://issues.jboss.org/browse/TEIIDDES-119
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.0.0
Reporter: John Doyle
Assignee: Ted Jones
Fix For: 8.0
The main case for this is REST services. REST services do not have a standard
description mechanism like WSDL for SOAP services. The inputs and outputs of the service
might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand
modeling is too difficult, so we need to come up with other assists. The solution is
probably a mix of new features and documented best practices.
For example:
Add WADL support to the importer.
Document use of a schema from XML tool (like inst2XSD)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4624
days inactive
5763
days old
teiid-designer-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Barry LaFond (JIRA) -
Greg Haber (JIRA)
-
John Doyle (JIRA)