Issue 19062: Deprecate Unit and QuantityKind stereotypes in 1.4 (sysml-rtf) Source: NASA (Dr. Nicolas F. Rouquette, nicolas.f.rouquette(at)jpl.nasa.gov) Nature: Uncategorized Issue Severity: Summary: Instead of deleting the Unit and QuantityKind stereotypes according to the 18269 resolution in SysML 1.4 ballot 4, I suggest moving these stereotypes to the SysML::DeprecatedElements package. Without doing this, a SysML 1.4 tool that opens a SysML 1.3 model will have to convert InstanceSpecifications stereotyped by SysML 1.3 Unit or QuantityKind into InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. Even if a SysML 1.4 tool alerts the user that this migration has happened, it will not be possible to discern InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind due migration from SysML 1.3 vs. deliberate choice. A better migration strategy would be to convert SysML 1.3 Unit/QuantityKind-stereotyped InstanceSpecifications into SysML 1.4 InstanceSpecifications that are both: stereotyped by SysML::DeprecatedElements::Unit/QuantityKind Classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind The former leaves a persistent indication that the InstanceSpecifications have been partially migrated. The latter represents a partial migration to SysML 1.4 Units/QuantityKinds; that is, the user can complete the migration by classifying these InstanceSpecifications with concrete SysML Blocks that specialize SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: November 1, 2013: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: "Rouquette, Nicolas F (313D)" To: "issues@omg.org" CC: "sysml-rtf@omg.org" , "cb@conradbock.org" Subject: Deprecate Unit and QuantityKind stereotypes in 1.4 Thread-Topic: Deprecate Unit and QuantityKind stereotypes in 1.4 Thread-Index: AQHO11TiGL4FtQZhtEqmgMARf1q0TQ== Date: Fri, 1 Nov 2013 22:51:22 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.4.130416 x-originating-ip: [128.149.137.114] X-Source-Sender: nicolas.f.rouquette@jpl.nasa.gov X-AUTH: Authorized X-Virus-Scanned: amavisd-new at omg.org Instead of deleting the Unit and QuantityKind stereotypes according to the 18269 resolution in SysML 1.4 ballot 4, I suggest moving these stereotypes to the SysML::DeprecatedElements package. Without doing this, a SysML 1.4 tool that opens a SysML 1.3 model will have to convert InstanceSpecifications stereotyped by SysML 1.3 Unit or QuantityKind into InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. Even if a SysML 1.4 tool alerts the user that this migration has happened, it will not be possible to discern InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind due migration from SysML 1.3 vs. deliberate choice. A better migration strategy would be to convert SysML 1.3 Unit/QuantityKind-stereotyped InstanceSpecifications into SysML 1.4 InstanceSpecifications that are both: stereotyped by SysML::DeprecatedElements::Unit/QuantityKind Classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind The former leaves a persistent indication that the InstanceSpecifications have been partially migrated. The latter represents a partial migration to SysML 1.4 Units/QuantityKinds; that is, the user can complete the migration by classifying these InstanceSpecifications with concrete SysML Blocks that specialize SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. - Nicolas. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1383368655; bh=kk0dgFgJvKkaw5g8e6tiUYO8ecUVSyPom6UHmZLk/L4=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language; b=52nUtLMSA53mfgPCvv3Jj4y2nLqB32wpphWOm7oC5cfBu9S+8n/tmbM9apPSBIDtIdWZwLMULPetEz5uqL5nUINMNv80TiEC6sJzRUyg0u4qdrBW9PSvAHlKheGwnt68os10YU33e1FE4aGIodndsaFRrcUCwYWP5rnAlYxOwP0= X-Yahoo-Newman-Id: 480083.99086.bm@smtp114.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: vfcmOnUVM1nDIAoykDLfdZRdGyncMFY2qoweykkXgPfhVQ3 PV9QN7JYuoBSV3x9TEDdY8ALLYnTD6My0LZGym6koj_ynGq2WgP1aSE03tc6 QISQBJDrqmTJTDpDntWGUk2J7tVhKzgPpuG4rJ_EGiTtK6weCWuoIfmY5z5d 6Nx7W8yu5OVi1VKhi8tO0wLc3rdzMcXTlXn4xMoMqB_rwfHJaOUVqF9b9OK6 zoaTdLz3Q_lN9NWvhEsa483k4fxucw8JzsKKOXruBb4FLlpR.x8Wng8clvr2 pbfumOZeUNZirPgsAXnRlcS3jDdwPxdMR_O1zBTJs5OoYtUEiA0yOiENQYM4 TpemdMYIWSvvZ874bA7mMg9LR8aOZLO2LQtveraNIcOFFT49L5melOMioi1I puabQxUWSuARW6DUCNU6ZisdI_vxS8CAm1PsYgNijYx8YCPkUngNZ4E8QICz Bf6H1Dzc.ozbdASNCLtHA__c1t7oPVtCQGLnLg2i..iJVjwupS3KBen2lIWn Oh3kPnifixjMftjz9P8lKXSgyx6nIBHzwapVBWEVXt5GJkcWKOkJL8g-- X-Yahoo-SMTP: BHehp.2swBCs4PqecFo6LCqjUcnFjw4- X-Rocket-Received: from mjchonolesHP (mjchonoles@71.225.92.207 with ) by smtp114.mail.ne1.yahoo.com with SMTP; 01 Nov 2013 22:04:15 -0700 PDT From: "Michael Chonoles" To: "'Rouquette, Nicolas F \(313D\)'" , Cc: , Subject: RE: Deprecate Unit and QuantityKind stereotypes in 1.4 Date: Sat, 2 Nov 2013 01:04:08 -0400 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQGr+xZ6jzc7HEH3l2UUJFlOU3UFN5pXG7DA X-Virus-Scanned: amavisd-new at omg.org Makes sense to me From: Rouquette, Nicolas F (313D) [mailto:nicolas.f.rouquette@jpl.nasa.gov] Sent: Friday, November 01, 2013 6:51 PM To: issues@omg.org Cc: sysml-rtf@omg.org; cb@conradbock.org Subject: Deprecate Unit and QuantityKind stereotypes in 1.4 Instead of deleting the Unit and QuantityKind stereotypes according to the 18269 resolution in SysML 1.4 ballot 4, I suggest moving these stereotypes to the SysML::DeprecatedElements package. Without doing this, a SysML 1.4 tool that opens a SysML 1.3 model will have to convert InstanceSpecifications stereotyped by SysML 1.3 Unit or QuantityKind into InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. Even if a SysML 1.4 tool alerts the user that this migration has happened, it will not be possible to discern InstanceSpecifications classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind due migration from SysML 1.3 vs. deliberate choice. A better migration strategy would be to convert SysML 1.3 Unit/QuantityKind-stereotyped InstanceSpecifications into SysML 1.4 InstanceSpecifications that are both: stereotyped by SysML::DeprecatedElements::Unit/QuantityKind Classified by SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind The former leaves a persistent indication that the InstanceSpecifications have been partially migrated. The latter represents a partial migration to SysML 1.4 Units/QuantityKinds; that is, the user can complete the migration by classifying these InstanceSpecifications with concrete SysML Blocks that specialize SysML::Libraries::UnitAndQuantityKind::Unit or QuantityKind respectively. - Nicolas.