Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » ECORE 2 XML Schema and back
| |
| Re: ECORE 2 XML Schema and back [message #133648 is a reply to message #133635] |
Wed, 25 February 2009 21:02   |
 Renat Zubairov
Messages: 30
Registered: July 2009 |
Member |
|
|
Thans Ed for reply. I tried it on Extended library model. I transformed the
ecore to XSD and then generated ecore again from the XSD I've got before.
Then I turn it to XSD again and... All element definitions that were
mentoned in XSD are gone. Also transitive, derived and volatile attributes
have not survived the round trip in the ECORE. Also one attribute
(people:EFeatureMapEntry) didn't survived either.
But most interesting part is that all types were changing the namespace, see
the example here:
http://screencast.com/t/zoa3wMLujP2
They used to be defined in http://www.eclipse.org/... Ecore.ecore... but
after roundtrip they became /plugin/org..../Ecore.ecore...
Renat
On 25.02.09 16:15, in article go3nb0$qlu$2@build.eclipse.org, "Ed Merks"
<Ed.Merks@gmail.com> wrote:
> Renat,
>
> Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
> It's possible that I've overlooked something, but if so, you can report
> it and I'll fix it. This is really an EMF question, not an EMFT question...
>
>
> Renat Zubairov wrote:
>> Hi all,
>>
>> I generated XML Schema from ECORE using "Generator -> Export model..."
>> option. And the generated Schema contains attributes in ecore namespace "
>> http://www.eclipse.org/emf/2002/Ecore". May I assume that this kind of
>> transformation is reversible, so that next time I will generate ECORE back
>> from this schema I will get exactly the same ECORE model? Is there any
>> limitations on that?
>>
>> Thanks!
>>
>> Renat
>>
>>
|
|
|
| Re: ECORE 2 XML Schema and back [message #133660 is a reply to message #133648] |
Wed, 25 February 2009 21:36 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------030605000809090204080409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Renat,
Comments below.
Renat Zubairov wrote:
> Thans Ed for reply. I tried it on Extended library model. I transformed the
> ecore to XSD and then generated ecore again from the XSD I've got before.
> Then I turn it to XSD again and... All element definitions that were
> mentoned in XSD are gone.
I didn't say XSD -> Ecore -> XSD is a round trip.
> Also transitive, derived and volatile attributes
> have not survived the round trip in the ECORE. Also one attribute
> (people:EFeatureMapEntry) didn't survived either.
>
Yes, I think you're right about the transient thing. They're really not
supposed to be in the XSD given they are transient and hence not
serialized...
> But most interesting part is that all types were changing the namespace, see
> the example here:
>
> http://screencast.com/t/zoa3wMLujP2
>
> They used to be defined in http://www.eclipse.org/... Ecore.ecore... but
> after roundtrip they became /plugin/org..../Ecore.ecore...
>
The Ecore model is kind of special so these two versions of it are
effectively equivalent when it comes to their use as data types.
> Renat
>
>
> On 25.02.09 16:15, in article go3nb0$qlu$2@build.eclipse.org, "Ed Merks"
> <Ed.Merks@gmail.com> wrote:
>
>
>> Renat,
>>
>> Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
>> It's possible that I've overlooked something, but if so, you can report
>> it and I'll fix it. This is really an EMF question, not an EMFT question...
>>
>>
>> Renat Zubairov wrote:
>>
>>> Hi all,
>>>
>>> I generated XML Schema from ECORE using "Generator -> Export model..."
>>> option. And the generated Schema contains attributes in ecore namespace "
>>> http://www.eclipse.org/emf/2002/Ecore". May I assume that this kind of
>>> transformation is reversible, so that next time I will generate ECORE back
>>> from this schema I will get exactly the same ECORE model? Is there any
>>> limitations on that?
>>>
>>> Thanks!
>>>
>>> Renat
>>>
>>>
>>>
>
>
--------------030605000809090204080409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Renat,<br>
<br>
Comments below.<br>
<br>
Renat Zubairov wrote:
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">Thans Ed for reply. I tried it on Extended library model. I transformed the
ecore to XSD and then generated ecore again from the XSD I've got before.
Then I turn it to XSD again and... All element definitions that were
mentoned in XSD are gone. </pre>
</blockquote>
I didn't say XSD -> Ecore -> XSD is a round trip.<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">Also transitive, derived and volatile attributes
have not survived the round trip in the ECORE. Also one attribute
(people:EFeatureMapEntry) didn't survived either.
</pre>
</blockquote>
Yes, I think you're right about the transient thing. They're really
not supposed to be in the XSD given they are transient and hence not
serialized...<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">But most interesting part is that all types were changing the namespace, see
the example here:
<a class="moz-txt-link-freetext" href="http://screencast.com/t/zoa3wMLujP2">http://screencast.com/t/zoa3wMLujP2</a>
They used to be defined in <a class="moz-txt-link-freetext" href="http://www.eclipse.org/">http://www.eclipse.org/</a>... Ecore.ecore... but
after roundtrip they became /plugin/org..../Ecore.ecore...
</pre>
</blockquote>
The Ecore model is kind of special so these two versions of it are
effectively equivalent when it comes to their use as data types.<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">
Renat
On 25.02.09 16:15, in article <a class="moz-txt-link-abbreviated" href="mailto:go3nb0$qlu$2@build.eclipse.org">go3nb0$qlu$2@build.eclipse.org</a>, "Ed Merks"
<a class="moz-txt-link-rfc2396E" href="mailto:Ed.Merks@gmail.com"><Ed.Merks@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Renat,
Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
It's possible that I've overlooked something, but if so, you can report
it and I'll fix it. This is really an EMF question, not an EMFT question...
Renat Zubairov wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I generated XML Schema from ECORE using "Generator -> Export model..."
option. And the generated Schema contains attributes in ecore namespace <a class="moz-txt-link-rfc2396E" href="http://www.eclipse.org/emf/2002/Ecore">"
http://www.eclipse.org/emf/2002/Ecore"</a>. May I assume that this kind of
transformation is reversible, so that next time I will generate ECORE back
from this schema I will get exactly the same ECORE model? Is there any
limitations on that?
Thanks!
Renat
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------030605000809090204080409--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: ECORE 2 XML Schema and back [message #620689 is a reply to message #133581] |
Wed, 25 February 2009 15:15 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Renat,
Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
It's possible that I've overlooked something, but if so, you can report
it and I'll fix it. This is really an EMF question, not an EMFT question...
Renat Zubairov wrote:
> Hi all,
>
> I generated XML Schema from ECORE using "Generator -> Export model..."
> option. And the generated Schema contains attributes in ecore namespace "
> http://www.eclipse.org/emf/2002/Ecore". May I assume that this kind of
> transformation is reversible, so that next time I will generate ECORE back
> from this schema I will get exactly the same ECORE model? Is there any
> limitations on that?
>
> Thanks!
>
> Renat
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: ECORE 2 XML Schema and back [message #620690 is a reply to message #133635] |
Wed, 25 February 2009 21:02 |
Renat Zubairov
Messages: 30
Registered: July 2009 |
Member |
|
|
Thans Ed for reply. I tried it on Extended library model. I transformed the
ecore to XSD and then generated ecore again from the XSD I've got before.
Then I turn it to XSD again and... All element definitions that were
mentoned in XSD are gone. Also transitive, derived and volatile attributes
have not survived the round trip in the ECORE. Also one attribute
(people:EFeatureMapEntry) didn't survived either.
But most interesting part is that all types were changing the namespace, see
the example here:
http://screencast.com/t/zoa3wMLujP2
They used to be defined in http://www.eclipse.org/.. Ecore.ecore... but
after roundtrip they became /plugin/org..../Ecore.ecore...
Renat
On 25.02.09 16:15, in article go3nb0$qlu$2@build.eclipse.org, "Ed Merks"
<Ed.Merks@gmail.com> wrote:
> Renat,
>
> Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
> It's possible that I've overlooked something, but if so, you can report
> it and I'll fix it. This is really an EMF question, not an EMFT question...
>
>
> Renat Zubairov wrote:
>> Hi all,
>>
>> I generated XML Schema from ECORE using "Generator -> Export model..."
>> option. And the generated Schema contains attributes in ecore namespace "
>> http://www.eclipse.org/emf/2002/Ecore". May I assume that this kind of
>> transformation is reversible, so that next time I will generate ECORE back
>> from this schema I will get exactly the same ECORE model? Is there any
>> limitations on that?
>>
>> Thanks!
>>
>> Renat
>>
>>
|
|
|
| Re: ECORE 2 XML Schema and back [message #620691 is a reply to message #133648] |
Wed, 25 February 2009 21:36 |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------030605000809090204080409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Renat,
Comments below.
Renat Zubairov wrote:
> Thans Ed for reply. I tried it on Extended library model. I transformed the
> ecore to XSD and then generated ecore again from the XSD I've got before.
> Then I turn it to XSD again and... All element definitions that were
> mentoned in XSD are gone.
I didn't say XSD -> Ecore -> XSD is a round trip.
> Also transitive, derived and volatile attributes
> have not survived the round trip in the ECORE. Also one attribute
> (people:EFeatureMapEntry) didn't survived either.
>
Yes, I think you're right about the transient thing. They're really not
supposed to be in the XSD given they are transient and hence not
serialized...
> But most interesting part is that all types were changing the namespace, see
> the example here:
>
> http://screencast.com/t/zoa3wMLujP2
>
> They used to be defined in http://www.eclipse.org/.. Ecore.ecore... but
> after roundtrip they became /plugin/org..../Ecore.ecore...
>
The Ecore model is kind of special so these two versions of it are
effectively equivalent when it comes to their use as data types.
> Renat
>
>
> On 25.02.09 16:15, in article go3nb0$qlu$2@build.eclipse.org, "Ed Merks"
> <Ed.Merks@gmail.com> wrote:
>
>
>> Renat,
>>
>> Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
>> It's possible that I've overlooked something, but if so, you can report
>> it and I'll fix it. This is really an EMF question, not an EMFT question...
>>
>>
>> Renat Zubairov wrote:
>>
>>> Hi all,
>>>
>>> I generated XML Schema from ECORE using "Generator -> Export model..."
>>> option. And the generated Schema contains attributes in ecore namespace "
>>> http://www.eclipse.org/emf/2002/Ecore". May I assume that this kind of
>>> transformation is reversible, so that next time I will generate ECORE back
>>> from this schema I will get exactly the same ECORE model? Is there any
>>> limitations on that?
>>>
>>> Thanks!
>>>
>>> Renat
>>>
>>>
>>>
>
>
--------------030605000809090204080409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Renat,<br>
<br>
Comments below.<br>
<br>
Renat Zubairov wrote:
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">Thans Ed for reply. I tried it on Extended library model. I transformed the
ecore to XSD and then generated ecore again from the XSD I've got before.
Then I turn it to XSD again and... All element definitions that were
mentoned in XSD are gone. </pre>
</blockquote>
I didn't say XSD -> Ecore -> XSD is a round trip.<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">Also transitive, derived and volatile attributes
have not survived the round trip in the ECORE. Also one attribute
(people:EFeatureMapEntry) didn't survived either.
</pre>
</blockquote>
Yes, I think you're right about the transient thing. They're really
not supposed to be in the XSD given they are transient and hence not
serialized...<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">But most interesting part is that all types were changing the namespace, see
the example here:
<a class="moz-txt-link-freetext" href="http://screencast.com/t/zoa3wMLujP2">http://screencast.com/t/zoa3wMLujP2</a>
They used to be defined in <a class="moz-txt-link-freetext" href="http://www.eclipse.org/">http://www.eclipse.org/</a>... Ecore.ecore... but
after roundtrip they became /plugin/org..../Ecore.ecore...
</pre>
</blockquote>
The Ecore model is kind of special so these two versions of it are
effectively equivalent when it comes to their use as data types.<br>
<blockquote cite="mid:C5CB705B.1AAD%25renat.zubairov@sopera.de"
type="cite">
<pre wrap="">
Renat
On 25.02.09 16:15, in article <a class="moz-txt-link-abbreviated" href="mailto:go3nb0$qlu$2@build.eclipse.org">go3nb0$qlu$2@build.eclipse.org</a>, "Ed Merks"
<a class="moz-txt-link-rfc2396E" href="mailto:Ed.Merks@gmail.com"><Ed.Merks@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Renat,
Yes, the idea is that Ecore -> XSD -> Ecore should be a round trip.
It's possible that I've overlooked something, but if so, you can report
it and I'll fix it. This is really an EMF question, not an EMFT question...
Renat Zubairov wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I generated XML Schema from ECORE using "Generator -> Export model..."
option. And the generated Schema contains attributes in ecore namespace <a class="moz-txt-link-rfc2396E" href="http://www.eclipse.org/emf/2002/Ecore">"
http://www.eclipse.org/emf/2002/Ecore"</a>. May I assume that this kind of
transformation is reversible, so that next time I will generate ECORE back
from this schema I will get exactly the same ECORE model? Is there any
limitations on that?
Thanks!
Renat
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>
--------------030605000809090204080409--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Goto Forum:
Current Time: Thu Apr 25 22:23:16 GMT 2024
Powered by FUDForum. Page generated in 0.03130 seconds |
] 
Search
Help
Register
Login
Home
