|
| Re: Controlling xmi:version in Serialized Assets [message #105019 is a reply to message #105016] |
Fri, 21 December 2007 19:54  |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------050807030707050307030308
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
David,
Is he using a generated XML Schema or an "XMI" Schema?
An XMI schema would allow the version attribute (and would allow it at
all levels of the tree, which is kind of stupid, but then I think XMI
schemas are kind of useless):
<xsd:attributeGroup name="ObjectAttribs">
<xsd:attributeGroup ref="xmi:IdentityAttribs"/>
<xsd:attributeGroup ref="xmi:LinkAttribs"/>
* <xsd:attribute fixed="2.0" form="qualified" name="version"
type="xsd:string" use="optional"/>*
<xsd:attribute form="qualified" name="type" type="xsd:QName"
use="optional"/>
</xsd:attributeGroup>
If you are generating an XML Schema, then you should be using an
XMLResourceImpl for doing the save in which case you won't get an
xmi:version tag in the result.
It's best to ask this type of question in the EMF newsgroup.
David Lynch wrote:
> Ed, my boss has been using EMF to generate XSDs that describe ecore
> documents; then, he uses XML Spy to validate the ecore documents
> against the XSD schema. Everything is working except on thing:
> xmi:version="2.0" attribute at the root level. Do you know why this
> would be, and is there any elegant way to control the xmi:version
> level in the serialization?
>
--------------050807030707050307030308
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David,<br>
<br>
Is he using a generated XML Schema or an "XMI" Schema?
|
|
|
| Re: Controlling xmi:version in Serialized Assets [message #612965 is a reply to message #105016] |
Fri, 21 December 2007 19:54 |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------050807030707050307030308
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
David,
Is he using a generated XML Schema or an "XMI" Schema?
An XMI schema would allow the version attribute (and would allow it at
all levels of the tree, which is kind of stupid, but then I think XMI
schemas are kind of useless):
<xsd:attributeGroup name="ObjectAttribs">
<xsd:attributeGroup ref="xmi:IdentityAttribs"/>
<xsd:attributeGroup ref="xmi:LinkAttribs"/>
* <xsd:attribute fixed="2.0" form="qualified" name="version"
type="xsd:string" use="optional"/>*
<xsd:attribute form="qualified" name="type" type="xsd:QName"
use="optional"/>
</xsd:attributeGroup>
If you are generating an XML Schema, then you should be using an
XMLResourceImpl for doing the save in which case you won't get an
xmi:version tag in the result.
It's best to ask this type of question in the EMF newsgroup.
David Lynch wrote:
> Ed, my boss has been using EMF to generate XSDs that describe ecore
> documents; then, he uses XML Spy to validate the ecore documents
> against the XSD schema. Everything is working except on thing:
> xmi:version="2.0" attribute at the root level. Do you know why this
> would be, and is there any elegant way to control the xmi:version
> level in the serialization?
>
--------------050807030707050307030308
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David,<br>
<br>
Is he using a generated XML Schema or an "XMI" Schema?
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03735 seconds
] 
Search
Help
Register
Login
Home
