Issue 15452: XMI issue - root elements for XMI Schemas (mof2xmi-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: At the moment every metaclass has a XML element generated, allowing it to be the root of any interchange. While this flexibility might be useful in some cases, it clogs up the XSD with elements that will never get used in practice. Proposed resolution: Define two boolean XMI Tags: 1. To define whether root elements should be restricted: org.omg.xmi.restrictRoots (defaults to true) 2. To mark classifiers (classes or associations) as being potential roots: org.omg.xmi.rootElement (defaults to false) Resolution: Revised Text: Actions taken: September 8, 2010: received issue Discussion: Proposed Disposition: Deferred End of Annotations:===== ubject: XMI issue - root elements for XMI Schemas Date: Wed, 8 Sep 2010 14:48:10 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XMI issue - root elements for XMI Schemas Thread-Index: ActPn3HWTp1tF0W1SO63pT70QvaDcA== From: "Pete Rivett" To: At the moment every metaclass has a XML element generated, allowing it to be the root of any interchange. While this flexibility might be useful in some cases, it clogs up the XSD with elements that will never get used in practice. Proposed resolution: Define two boolean XMI Tags: 1. To define whether root elements should be restricted: org.omg.xmi.restrictRoots (defaults to true) 2. To mark classifiers (classes or associations) as being potential roots: org.omg.xmi.rootElement (defaults to false) -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp Date: Fri, 10 Sep 2010 17:05:26 +0100 From: Dave Hawkins User-Agent: Thunderbird 2.0.0.21 (X11/20090302) To: Juergen Boldt CC: issues@omg.org, mof2xmi-rtf@omg.org Subject: Re: issue 15452 -- MOF 2 XMI RTF issue I've never been entirely sure why XMI encodes root objects differently to composites. It actually makes it more complex to implement XMI readers and writers. I'd prefer a form, for example, like: And not allow in any circumstances. Dave Juergen Boldt wrote: Subject: XMI issue - root elements for XMI Schemas Date: Wed, 8 Sep 2010 14:48:10 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XMI issue - root elements for XMI Schemas Thread-Index: ActPn3HWTp1tF0W1SO63pT70QvaDcA== From: "Pete Rivett" To: At the moment every metaclass has a XML element generated, allowing it to be the root of any interchange. While this flexibility might be useful in some cases, it clogs up the XSD with elements that will never get used in practice. Proposed resolution: Define two boolean XMI Tags: 1. To define whether root elements should be restricted: org.omg.xmi.restrictRoots (defaults to true) 2. To mark classifiers (classes or associations) as being potential roots: org.omg.xmi.rootElement (defaults to false) -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp * Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org * [] -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA. Date: Fri, 10 Sep 2010 17:05:26 +0100 From: Dave Hawkins User-Agent: Thunderbird 2.0.0.21 (X11/20090302) To: Juergen Boldt CC: issues@omg.org, mof2xmi-rtf@omg.org Subject: Re: issue 15452 -- MOF 2 XMI RTF issue I've never been entirely sure why XMI encodes root objects differently to composites. It actually makes it more complex to implement XMI readers and writers. I'd prefer a form, for example, like: Date: Fri, 10 Sep 2010 17:05:26 +0100 From: Dave Hawkins User-Agent: Thunderbird 2.0.0.21 (X11/20090302) To: Juergen Boldt CC: issues@omg.org, mof2xmi-rtf@omg.org Subject: Re: issue 15452 -- MOF 2 XMI RTF issue I've never been entirely sure why XMI encodes root objects differently to composites. It actually makes it more complex to implement XMI readers and writers. I'd prefer a form, for example, like: And not allow in any circumstances. Dave Juergen Boldt wrote: Subject: XMI issue - root elements for XMI Schemas Date: Wed, 8 Sep 2010 14:48:10 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XMI issue - root elements for XMI Schemas Thread-Index: ActPn3HWTp1tF0W1SO63pT70QvaDcA== From: "Pete Rivett" To: At the moment every metaclass has a XML element generated, allowing it to be the root of any interchange. While this flexibility might be useful in some cases, it clogs up the XSD with elements that will never get used in practice. Proposed resolution: Define two boolean XMI Tags: 1. To define whether root elements should be restricted: org.omg.xmi.restrictRoots (defaults to true) 2. To mark classifiers (classes or associations) as being potential roots: org.omg.xmi.rootElement (defaults to false) -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp * Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org * [] -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505. Reg. office: Oracle Parkway, Thames Valley Park, Reading RG6 1RA. Subject: RE: issue 15452 -- MOF 2 XMI RTF issue Date: Fri, 10 Sep 2010 10:18:42 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 15452 -- MOF 2 XMI RTF issue Thread-Index: ActRAntwyM4IMQseSyunyY0ePF9EMAACPv9Q From: "Pete Rivett" To: "Dave Hawkins" Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id o8AH0FGD026577 The reason is that XMI 2.x moved from a 'striped' approach of Element/Property/Element/Property to Element/Property/Property/Property etc. Personally I think that was a mistake but I did not have much influence at the time. Also some people were not keen on requiring XMI as the root element (as opposed to a root from the metamodel such as Package): again I didn't think that was a problem. FWIW XMI 2.4 is making xmi:type mandatory on all non-link elements - though redundant on root objects (as I think you pointed out) it does make processing more symmetrical. Cheers Pete -----Original Message----- From: Dave Hawkins [mailto:dave.hawkins@oracle.com] Sent: Friday, September 10, 2010 9:05 AM To: Juergen Boldt Cc: issues@omg.org; mof2xmi-rtf@omg.org Subject: Re: issue 15452 -- MOF 2 XMI RTF issue I've never been entirely sure why XMI encodes root objects differently to composites. It actually makes it more complex to implement XMI readers and writers. I'd prefer a form, for example, like: And not allow in any circumstances. Dave Juergen Boldt wrote: > >> Subject: XMI issue - root elements for XMI Schemas >> Date: Wed, 8 Sep 2010 14:48:10 -0700 >> X-MS-Has-Attach: >> X-MS-TNEF-Correlator: >> Thread-Topic: XMI issue - root elements for XMI Schemas >> Thread-Index: ActPn3HWTp1tF0W1SO63pT70QvaDcA== >> From: "Pete Rivett" >> To: >> >> At the moment every metaclass has a XML element generated, allowing >> it to be the root of any interchange. >> While this flexibility might be useful in some cases, it clogs up the >> XSD with elements that will never get used in practice. >> >> Proposed resolution: >> Define two boolean XMI Tags: >> 1. To define whether root elements should be restricted: >> org.omg.xmi.restrictRoots (defaults to true) >> 2. To mark classifiers (classes or associations) as being potential >> roots: org.omg.xmi.rootElement (defaults to false) >> >> -- >> Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc >> 65 Enterprise, Aliso Viejo, CA 92656 >> cell: +1 949 338 3794 >> Follow me on Twitter @rivettp or http://twitter.com/rivettp >> >> > > * > > Juergen Boldt > Director, Member Services > Object Management Group > 140 Kendrick St > Building A Suite 300 > Needham, MA 02494 > USA > > tel: +1 781 444 0404 x 132 > fax: +1 781 444 0320 > email: juergen@omg.org > www.omg.org > > * [] > > > > -- Dave Hawkins | Principal Software Engineer | +44 118 924 0022 Oracle JDeveloper Development Oracle Corporation UK Ltd is a company incorporated in England & Wales. Company Reg. No. 1782505.