Home » Archived » XML Schema Definition (XSD) » Identifier and package names in XSD-based EMF
| Identifier and package names in XSD-based EMF [message #71863] |
Tue, 20 March 2007 13:12  |
Eclipse User |
|
|
|
Hello
I'm new to EMF as well as XML schema. Generating a model from an XML schema,
I noticed EMF names the identifiers, as well as the model's packages, after
the last word in the schema's namespace hierarchy. For example, the
namespace identifier for a schema whose namespace is
http://www.test.org/2007/sname would be "sname"; however, the identifier for
the namespace http://www.ccsds.org/xfdu/2004 (which I use) would be "2004" -
even though I'd like it to be "xfdu".
Is there a way to configure the way EMF generates these names? It turns out
there's some inconsistency when it comes to schema namespaces (i.e., whether
the year should follow the standard's name or precede it), so being able to
change EMF's naming methods would help overcome such inconsistencies.
Thanks,
Shahar.
|
|
|
| Re: Identifier and package names in XSD-based EMF [message #71892 is a reply to message #71863] |
Tue, 20 March 2007 13:40  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------030305050404070800070107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Shahar,
This document describes all the annotations available to tailor the XML
Schema -> Ecore conversion process:
XML Schema to Ecore Mapping
< http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf>
You can use ecore:package on the <xsd:schema> element to specify the
fully qualified package name.
Shahar Ronen wrote:
> Hello
> I'm new to EMF as well as XML schema. Generating a model from an XML schema,
> I noticed EMF names the identifiers, as well as the model's packages, after
> the last word in the schema's namespace hierarchy. For example, the
> namespace identifier for a schema whose namespace is
> http://www.test.org/2007/sname would be "sname"; however, the identifier for
> the namespace http://www.ccsds.org/xfdu/2004 (which I use) would be "2004" -
> even though I'd like it to be "xfdu".
> Is there a way to configure the way EMF generates these names? It turns out
> there's some inconsistency when it comes to schema namespaces (i.e., whether
> the year should follow the standard's name or precede it), so being able to
> change EMF's naming methods would help overcome such inconsistencies.
>
> Thanks,
> Shahar.
>
>
>
--------------030305050404070800070107
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">
Shahar,<br>
<br>
This document describes all the annotations available to tailor the XML
Schema -> Ecore conversion process:<br>
<blockquote><a
href=" http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf">XML
Schema to Ecore Mapping</a><br>
</blockquote>
You can use ecore:package on the <xsd:schema> element to specify
the fully qualified package name.<br>
<br>
<br>
Shahar Ronen wrote:
<blockquote cite="midetomj7$drd$1@utils.eclipse.org" type="cite">
<pre wrap="">Hello
I'm new to EMF as well as XML schema. Generating a model from an XML schema,
I noticed EMF names the identifiers, as well as the model's packages, after
the last word in the schema's namespace hierarchy. For example, the
namespace identifier for a schema whose namespace is
<a class="moz-txt-link-freetext" href="http://www.test.org/2007/sname">http://www.test.org/2007/sname</a> would be "sname"; however, the identifier for
the namespace <a class="moz-txt-link-freetext" href="http://www.ccsds.org/xfdu/2004">http://www.ccsds.org/xfdu/2004</a> (which I use) would be "2004" -
even though I'd like it to be "xfdu".
Is there a way to configure the way EMF generates these names? It turns out
there's some inconsistency when it comes to schema namespaces (i.e., whether
the year should follow the standard's name or precede it), so being able to
change EMF's naming methods would help overcome such inconsistencies.
Thanks,
Shahar.
</pre>
</blockquote>
<br>
</body>
</html>
--------------030305050404070800070107--
|
|
|
| Re: Identifier and package names in XSD-based EMF [message #602247 is a reply to message #71863] |
Tue, 20 March 2007 13:40 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------030305050404070800070107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Shahar,
This document describes all the annotations available to tailor the XML
Schema -> Ecore conversion process:
XML Schema to Ecore Mapping
< http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf>
You can use ecore:package on the <xsd:schema> element to specify the
fully qualified package name.
Shahar Ronen wrote:
> Hello
> I'm new to EMF as well as XML schema. Generating a model from an XML schema,
> I noticed EMF names the identifiers, as well as the model's packages, after
> the last word in the schema's namespace hierarchy. For example, the
> namespace identifier for a schema whose namespace is
> http://www.test.org/2007/sname would be "sname"; however, the identifier for
> the namespace http://www.ccsds.org/xfdu/2004 (which I use) would be "2004" -
> even though I'd like it to be "xfdu".
> Is there a way to configure the way EMF generates these names? It turns out
> there's some inconsistency when it comes to schema namespaces (i.e., whether
> the year should follow the standard's name or precede it), so being able to
> change EMF's naming methods would help overcome such inconsistencies.
>
> Thanks,
> Shahar.
>
>
>
--------------030305050404070800070107
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">
Shahar,<br>
<br>
This document describes all the annotations available to tailor the XML
Schema -> Ecore conversion process:<br>
<blockquote><a
href=" http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf">XML
Schema to Ecore Mapping</a><br>
</blockquote>
You can use ecore:package on the <xsd:schema> element to specify
the fully qualified package name.<br>
<br>
<br>
Shahar Ronen wrote:
<blockquote cite="midetomj7$drd$1@utils.eclipse.org" type="cite">
<pre wrap="">Hello
I'm new to EMF as well as XML schema. Generating a model from an XML schema,
I noticed EMF names the identifiers, as well as the model's packages, after
the last word in the schema's namespace hierarchy. For example, the
namespace identifier for a schema whose namespace is
<a class="moz-txt-link-freetext" href="http://www.test.org/2007/sname">http://www.test.org/2007/sname</a> would be "sname"; however, the identifier for
the namespace <a class="moz-txt-link-freetext" href="http://www.ccsds.org/xfdu/2004">http://www.ccsds.org/xfdu/2004</a> (which I use) would be "2004" -
even though I'd like it to be "xfdu".
Is there a way to configure the way EMF generates these names? It turns out
there's some inconsistency when it comes to schema namespaces (i.e., whether
the year should follow the standard's name or precede it), so being able to
change EMF's naming methods would help overcome such inconsistencies.
Thanks,
Shahar.
</pre>
</blockquote>
<br>
</body>
</html>
--------------030305050404070800070107--
|
|
|
Goto Forum:
Current Time: Tue Feb 11 04:30:42 GMT 2025
Powered by FUDForum. Page generated in 0.03205 seconds |
] 
Search
Help
Register
Login
Home
