Understanding TMF 633 (how to declare simple service ...

文章推薦指數: 80 %
投票人數:10人

I'm new to TM Forum and evaluate how to revamp in house SOM application based on TMF 633/TMF 641/ TMF 638. I read TMF633 Service catalog ...    Skiptomaincontent(PressEnter). LogIn Skipauxiliarynavigation(PressEnter). tmforum.orgHelp/FAQsContactUsCodeofConduct Skipmainnavigation(PressEnter). Togglenavigation SearchOptions HomeCommunitiesAllCommunitiesMyCommunitiesDirectoryEventsUpcomingEventsBrowseDiscussionPostsLibraryEntries CommunitiesCommunityHomeDiscussionTopicThread OpenAPIs  ViewOnly CommunityHome Discussion 5.7K Library 41 Events 0 Members 48.4K Backtodiscussions Expandall| Collapseall sortbymostrecent sortbythread UnderstandingTMF633(howtodeclaresimpleservicespecification) waichowJul21,202008:08Hi, I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TM...JonathanGoldbergJul21,202008:20HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfand...waichowJul23,202004:15HiJonathan,Thanksforyourclarification.IfIneedtocreatewith...JonathanGoldbergJul23,202006:21HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryout...VanceShipleyJul27,202001:36Whileit'struethat"theOpenAPImodeldoesnotdistinguishbetweenCFSandRFS"explicitlyit...waichowJul27,202003:54HiJonathan,Mymainpurposeistodefinespecification(CFS)fornorthbound/COM.Then,ourmi...JonathanGoldbergJul27,202007:10TMF633isacatalogAPI,representingthefunctionalityofdefiningservicesandtheircapabili...WingSinJul27,202007:33HiJonathan,Thanksforyourcomments,Ihaveupdatedthespecaccordingly. However,Iwant...JonathanGoldbergJul28,202011:41HiWingIthinkyouraisedsomethingsimilarinanotherpost,regardingmappingbetweenaninte...WingSinAug25,202007:57Hi Jonathan,Thanksforyourcomments,Ihaveupdatedthespec.Wouldyoupleaseadviseifw...JonathanGoldbergAug26,202001:46HiWingTomynon-practicedeyeyourexamplelooksOK.Ialreadystatedmyrecommendation,whi... 1.  UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember waichow PostedJul21,202008:08 Reply ReplyPrivately OptionsDropdown Hi, I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638. IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification. Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 2.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 1 Like TMForumMember JonathanGoldberg PostedJul21,202008:20 Reply ReplyPrivately OptionsDropdown HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps. {    "name":"VirtualStorageMedium",    "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",    "@type":"LogicalResourceSpecification",    "@baseType":"ResourceSpecification",    "resourceSpecCharacteristic":[        {            "name":"MaximumAllowedStorage",            "description":"Thestoragelimitinthevirtualstoragemedium,",            "valueType":"integer",            "configurable":true,            "minCardinality":1,            "maxCardinality":1,            "isUnique":true,            "resourceSpecCharacteristicValue":[                {                    "valueType":"integer",                    "value":1024000                },                {                    "valueType":"integer",                    "value":2048000                }            ]        }    ] }------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.------------------------------ OriginalMessage OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 3.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember waichow PostedJul23,202004:15 Reply ReplyPrivately OptionsDropdown HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate 1servicecatalog 3servicecatalog(,,)? eg/ {   "name": "ADDVMS",   "description": "Add Voice Mail Service Specification",   "isBundle": true,   "lastUpdate": "2020-07-22T02:47:10.141Z",   "lifecycleStatus": "Active",   "version": "0.1",   "serviceSpecCharacteristic": [     {       "configurable": true,       "name": "MSISDN",       "description": "Mobile Number",       "extensible": true,       "isUnique": true,       "maxCardinality": 1,       "minCardinality": 1,       "valueType": "string"     },     {       "configurable": true,       "name": "IMSI",       "description": "IMSINumber",       "extensible": true,       "isUnique": true,       "maxCardinality": 1,       "minCardinality": 1,       "valueType": "string"     },     {       "configurable": true,       "name": "BRANDCODE",       "description": "Brand (mapping)",       "extensible": true,       "isUnique": true,       "maxCardinality": 1,       "minCardinality": 1,       "valueType": "string",       "serviceSpecCharacteristicValue": [         {           "isDefault": true,       "valueType": "String"           "value": "0"         },         {           "isDefault": false,       "valueType": "String"           "value": "1"         }       ]     },     {       "configurable": true,       "name": "VMSSERVICECLASS",       "description": "Mail Box Type",       "extensible": true,       "isUnique": true,       "maxCardinality": 1,       "minCardinality": 1,       "regex": "",       "valueType": "string",       "serviceSpecCharacteristicValue": [         {           "isDefault": true,       "valueType": "String"           "value": "3"         },         {           "isDefault": false,       "valueType": "String"           "value": "5"         }       ]     },     {       "configurable": true,       "name": "VMSLANG",       "description": "Mail Box Language (mapping)",       "extensible": true,       "isUnique": true,       "maxCardinality": 1,       "minCardinality": 1,       "regex": "",       "valueType": "string",       "serviceSpecCharacteristicValue": [         {           "isDefault": false,       "valueType": "String"           "value": "1"         },         {           "isDefault": true,       "valueType": "String"           "value": "2"         },         {           "isDefault": false,       "valueType": "String"           "value": "3"         }       ]     }   ],   "@type": "CustomerFacingServiceSpecification" } Thanks------------------------------waichowPCCWSolutionsLimited------------------------------ OriginalMessage OriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 4.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember JonathanGoldberg PostedJul23,202006:21 Reply ReplyPrivately OptionsDropdown HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel: TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec. Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful. IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec. Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.------------------------------ OriginalMessage OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 5.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember VanceShipley PostedJul27,202001:36 Reply ReplyPrivately OptionsDropdown Whileit'struethat"theOpenAPImodeldoesnotdistinguishbetweenCFSandRFS"explicitlyitdoessoimplicitlybytheinclusionofresourceSpecificationinanRFS.------------------------------VanceShipleySigScale------------------------------ OriginalMessage OriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 6.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember waichow PostedJul27,202003:54 Reply ReplyPrivately OptionsDropdown HiJonathan,Mymainpurposeistodefinespecification(CFS)fornorthbound/COM.Then,ourmiddleware(SOM)shouldtranslate/decomposeTMF641orderandtheninvokeRFSservicelogic. Idon'twantnorthbound/COMtoinvoketheRFS/TMF640directly.SoIwillperformthese2activities. Defineservicecatalog(TMF633)withoutanyoperationcarryoutontheservice. Defineorderspec(TMF640)withoperationscarryoutontheservice AmIontherighttrack?SeemsTMF633itselfwithoutanyoperationcarryoutontheservicedoesnothavetoomuchvalueatall,doImisunderstandtherationalebehindTMF633?Thanks------------------------------waichowPCCWSolutionsLimited------------------------------ OriginalMessage OriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 7.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember JonathanGoldberg PostedJul27,202007:10 Reply ReplyPrivately OptionsDropdown TMF633isacatalogAPI,representingthefunctionalityofdefiningservicesandtheircapabilities.TMF640isoneofafamilyofinstanceAPIsintheservicedomain,representingfunctionalityofactingonaspecificservice(inthiscaseactivatingandconfiguringtheserviceinthenetwork).SoTMF640isnottheplacetoexposetheallowedactions.Subjecttocorrectionbydomainexpertssuchas@VanceShipleyand@KamalMaghsoudlou,itseemstomethatthereisatacitassumptionthatthereisafixedandclosedlistofactionsyoucantakeonaservice,adding,modifying,suspending,resuming,andterminating.Perhapsyouwouldliketoseeamoreexplicitlistofactionsdefinedatcataloglevel,sincesomeserviceswouldnotallowsuspendorresume,othersmightnotallowmodify,etc.ThisconceptismissingfromtheOpenAPIcatalogAPIs(Product,Service,Resource);itispresentintheInformationFramework(SID)forProductintheProductActionABE,butthereisnoSIDequivalentforServiceactions.So ​inanimplementationofTMF640APIyoumightwellrejectarequestto(forexample)suspendaservice,basedonyourinternalknowledgeoftheservicedefinition,eventhoughthisisnotcurrentlyrepresentedincatalogAPIs.Hopeithelps------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.------------------------------ OriginalMessage OriginalMessage:Sent:Jul27,202003:53From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Mymainpurposeistodefinespecification(CFS)fornorthbound/COM.Then,ourmiddleware(SOM)shouldtranslate/decomposeTMF641orderandtheninvokeRFSservicelogic. Idon'twantnorthbound/COMtoinvoketheRFS/TMF640directly.SoIwillperformthese2activities.Defineservicecatalog(TMF633)withoutanyoperationcarryoutontheservice.Defineorderspec(TMF640)withoperationscarryoutontheserviceAmIontherighttrack?SeemsTMF633itselfwithoutanyoperationcarryoutontheservicedoesnothavetoomuchvalueatall,doImisunderstandtherationalebehindTMF633?Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 8.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember WingSin PostedJul27,202007:33 Reply ReplyPrivately OptionsDropdown HiJonathan,Thanksforyourcomments,Ihaveupdatedthespecaccordingly.However,Iwanttoaskhowcanweincludethesemanticmeaninginthespec?Aswewantthevaluepassasavalueinstead,woulditbefinetoadd"description"tagasfollowing?Oranybetterapproach? Thanks. "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "value":"3", "description":"Normal" }, { "isDefault":false, "valueType":"String", "value":"5", "description":"Premium" } ] { "name":"VMS", "description":"VoiceMailServiceSpecification", "lastUpdate":"2020-07-22T02:47:10.141Z", "lifecycleStatus":"Active", "version":"0.1", "serviceSpecCharacteristic":[ { "configurable":true, "name":"MSISDN", "description":"MobileNumber", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string" }, { "configurable":true, "name":"IMSI", "description":"MobileSIMNumber", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string" }, { "configurable":true, "name":"BRANDCODE", "description":"Brand", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "value":"0" }, { "isDefault":false, "valueType":"String", "value":"1" } ] }, { "configurable":true, "name":"VMSSERVICECLASS", "description":"MailBoxType", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "regex":"", "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "value":"3" }, { "isDefault":false, "valueType":"String", "value":"5" } ] }, { "configurable":true, "name":"VMSLANG", "description":"MailBoxLanguage", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "regex":"", "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":false, "valueType":"String", "value":"1" }, { "isDefault":true, "valueType":"String", "value":"2" }, { "isDefault":false, "valueType":"String", "value":"3" } ] } ] }------------------------------WingSinPCCWSolutionsLimited------------------------------ OriginalMessage OriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 9.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember JonathanGoldberg PostedJul28,202011:41 Reply ReplyPrivately OptionsDropdown HiWingIthinkyouraisedsomethingsimilarinanotherpost,regardingmappingbetweenaninternal(numeric)characteristicvalueinRFSandanexternal(human-semantic)valueinCFS.AtanyratetheOpenAPIdoesnothaveanydistinction(currently,atanyrate)betweenavalueandsomehuman-readablerepresentationofthatvalue.Thisistrueforcharacteristicsandforvaluesinstrongly-typedenums.IguessthattheideaisthattheOpenAPIdealswithbackendintegration,andisnotconcernedwithpresentationissues.YoucanofcourseextendthemodelandAPIbyaddingattributes,perhaps"displayValue"wouldbeclearerthan"description",ifthatisyourintention.Hopeithelps------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.------------------------------ OriginalMessage OriginalMessage:Sent:Jul26,202023:30From:WingSinSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourcomments,Ihaveupdatedthespecaccordingly.However,Iwanttoaskhowcanweincludethesemanticmeaninginthespec?Aswewantthevaluepassasavalueinstead,woulditbefinetoadd"description"tagasfollowing?Oranybetterapproach?Thanks."serviceSpecCharacteristicValue":[{"isDefault":true,"valueType":"String","value":"3","description":"Normal"},{"isDefault":false,"valueType":"String","value":"5","description":"Premium"}]{"name":"VMS","description":"VoiceMailServiceSpecification","lastUpdate":"2020-07-22T02:47:10.141Z","lifecycleStatus":"Active","version":"0.1","serviceSpecCharacteristic":[{"configurable":true,"name":"MSISDN","description":"MobileNumber","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string"},{"configurable":true,"name":"IMSI","description":"MobileSIMNumber","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string"},{"configurable":true,"name":"BRANDCODE","description":"Brand","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":true, "valueType":"String","value":"0"},{"isDefault":false, "valueType":"String","value":"1"}]},{"configurable":true,"name":"VMSSERVICECLASS","description":"MailBoxType","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"regex":"","valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":true, "valueType":"String","value":"3"},{"isDefault":false, "valueType":"String","value":"5"}]},{"configurable":true,"name":"VMSLANG","description":"MailBoxLanguage","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"regex":"","valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":false, "valueType":"String","value":"1"},{"isDefault":true, "valueType":"String","value":"2"},{"isDefault":false, "valueType":"String","value":"3"}]}]}------------------------------WingSinPCCWSolutionsLimitedOriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 10.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember WingSin PostedAug25,202007:57 Reply ReplyPrivately OptionsDropdown Hi Jonathan,Thanksforyourcomments,Ihaveupdatedthespec.Wouldyoupleaseadviseifwecouldincludethesemanticmeaningwith"description"tagaswewanttopassthosevalueinstead.Oristhereanybetterapproach? Thanks. "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "description":"Normal", "value":"3" }, { "isDefault":false, "valueType":"String", "description":"Premium", "value":"5" } ] { "id":"1", "name":"VMS", "description":"VoiceMailServiceSpecification", "lastUpdate":"2020-07-22T02:47:10.141Z", "lifecycleStatus":"Active", "version":"0.1", "serviceSpecCharacteristic":[ { "configurable":true, "name":"MSISDN", "description":"MobileNumber", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string" }, { "configurable":true, "name":"IMSI", "description":"MobileSIMNumber", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string" }, { "configurable":true, "name":"BRANDCODE", "description":"Brand", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "value":"0" }, { "isDefault":false, "valueType":"String", "value":"1" } ] }, { "configurable":true, "name":"VMSSERVICECLASS", "description":"MailBoxType", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "regex":"", "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":true, "valueType":"String", "value":"3" }, { "isDefault":false, "valueType":"String", "value":"5" } ] }, { "configurable":true, "name":"VMSLANG", "description":"MailBoxLanguage", "extensible":true, "isUnique":true, "maxCardinality":1, "minCardinality":1, "regex":"", "valueType":"string", "serviceSpecCharacteristicValue":[ { "isDefault":false, "valueType":"String", "value":"1" }, { "isDefault":true, "valueType":"String", "value":"2" }, { "isDefault":false, "valueType":"String", "value":"3" } ] } ] }----------------------------------------------------------------WingSinPCCWSolutionsLimited---------------------------------------------------------------- OriginalMessage OriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ 11.  RE:UnderstandingTMF633(howtodeclaresimpleservicespecification) 0 Like TMForumMember JonathanGoldberg PostedAug26,202001:46 Reply ReplyPrivately OptionsDropdown HiWingTomynon-practicedeyeyourexamplelooksOK.Ialreadystatedmyrecommendation,whichisthatifyouareinanycaseextendingCharacteristicValueSpecificationthen"displayValue"seemstomeabetternamethan"description".Hopeithelps------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.------------------------------ OriginalMessage OriginalMessage:Sent:Jul27,202002:22From:WingSinSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi Jonathan,Thanksforyourcomments,Ihaveupdatedthespec.Wouldyoupleaseadviseifwecouldincludethesemanticmeaningwith"description"tagaswewanttopassthosevalueinstead.Oristhereanybetterapproach? Thanks."serviceSpecCharacteristicValue":[{"isDefault":true,"valueType":"String","description":"Normal","value":"3"},{"isDefault":false,"valueType":"String","description":"Premium","value":"5"}]{"id":"1","name":"VMS","description":"VoiceMailServiceSpecification","lastUpdate":"2020-07-22T02:47:10.141Z","lifecycleStatus":"Active","version":"0.1","serviceSpecCharacteristic":[{"configurable":true,"name":"MSISDN","description":"MobileNumber","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string"},{"configurable":true,"name":"IMSI","description":"MobileSIMNumber","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string"},{"configurable":true,"name":"BRANDCODE","description":"Brand","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":true, "valueType":"String","value":"0"},{"isDefault":false, "valueType":"String","value":"1"}]},{"configurable":true,"name":"VMSSERVICECLASS","description":"MailBoxType","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"regex":"","valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":true, "valueType":"String","value":"3"},{"isDefault":false, "valueType":"String","value":"5"}]},{"configurable":true,"name":"VMSLANG","description":"MailBoxLanguage","extensible":true,"isUnique":true,"maxCardinality":1,"minCardinality":1,"regex":"","valueType":"string","serviceSpecCharacteristicValue":[{"isDefault":false, "valueType":"String","value":"1"},{"isDefault":true, "valueType":"String","value":"2"},{"isDefault":false, "valueType":"String","value":"3"}]}]}----------------------------------------------------------------WingSinPCCWSolutionsLimited----------------------------------OriginalMessage:Sent:Jul23,202006:21From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiTheservicecatalogdefinitionreflectstheservice,nottheoperationsthatyoucarryoutontheservice.YoushouldcreateasingleVoiceMailservicespecificationinthecatalog.Toadd,change,orremovevoice-mail,youwouldpresumablyneedtoprocessaserviceorderTMF641-orperhapsifyoucanworkdirectlyagainstthenetworkyoucoulduseserviceactivationandconfigurationTMF640.Specificcommentsonyourproposedmodel:TheOpenAPImodeldoesnotdistinguishbetweenCFSandRFS-ifyouwanttomakethatdistinctionthat'sfine,butthenyouneedtoincludea@baseTypethatcontainsServiceSpecificationanda@schemaLocationthatdefinesCFSextensiontoServiceSpec.Ithinkitwouldbebettertohavetruevaluesinyourcharacteristicexamples,sothatsomeonewholooksatthespec(andtheinstantiationintheinventory)canunderstandthesemanticmeaning.Valuessuchas"3"and"5"forserviceclass,or"1"and"2"fornationallanguage,arenotnecessarilyhelpful.IfyousetisBundletotrue,theexpectationisthattheservicespechassub-structure,andIwouldexpecttoseeareferencetoacontainedservicespec.Hopeithelps​​------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul23,202004:15From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiJonathan,Thanksforyourclarification.IfIneedtocreatewiththreeoperations/actions,shouldIcreate1servicecatalog3servicecatalog(,,)?eg/{  "name": "ADDVMS",  "description": "Add Voice Mail Service Specification",  "isBundle": true,  "lastUpdate": "2020-07-22T02:47:10.141Z",  "lifecycleStatus": "Active",  "version": "0.1",  "serviceSpecCharacteristic": [    {      "configurable": true,      "name": "MSISDN",      "description": "Mobile Number",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "IMSI",      "description": "IMSINumber",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string"    },    {      "configurable": true,      "name": "BRANDCODE",      "description": "Brand (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "0"        },        {          "isDefault": false,      "valueType": "String"          "value": "1"        }      ]    },    {      "configurable": true,      "name": "VMSSERVICECLASS",      "description": "Mail Box Type",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": true,      "valueType": "String"          "value": "3"        },        {          "isDefault": false,      "valueType": "String"          "value": "5"        }      ]    },    {      "configurable": true,      "name": "VMSLANG",      "description": "Mail Box Language (mapping)",      "extensible": true,      "isUnique": true,      "maxCardinality": 1,      "minCardinality": 1,      "regex": "",      "valueType": "string",      "serviceSpecCharacteristicValue": [        {          "isDefault": false,      "valueType": "String"          "value": "1"        },        {          "isDefault": true,      "valueType": "String"          "value": "2"        },        {          "isDefault": false,      "valueType": "String"          "value": "3"        }      ]    }  ],  "@type": "CustomerFacingServiceSpecification"}Thanks------------------------------waichowPCCWSolutionsLimitedOriginalMessage:Sent:Jul21,202008:19From:JonathanGoldbergSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)HiWaiWelcome,hopeyouwillfindyourinteractionwiththeTMForumproductiveforyourselfandyourcompany.AllthepublishedOpenAPIuserguides(weusedtocallthemspecifications)includeexamplesofJSONresourcesandpayloads.AstheOpenAPIteamcontinuetoworkonAPIdefinitions,wetrytorefineandupdatetheexamplessothattheywillreflectrealbusinessscenarios,asfaraspossible.Indeedthesimplestwaytodefineaserviceinthecatalogistousecompletelydynamicdefinitions,withspecifications,specificationcharacteristics,andvalues.Anexamplebelow(admittedlyfromResourceCatalog,buttheideaisverysimilarforServiceCatalog)foraverysimplespecforastoragewithonecharacteristicforthemaximumstorage,usingvaluestorepresentthelistofallowedvalues.Hopeithelps.{   "name":"VirtualStorageMedium",   "description":"Thisresourcespecificationdefinesthevirtualstoragemedium",   "@type":"LogicalResourceSpecification",   "@baseType":"ResourceSpecification",   "resourceSpecCharacteristic":[       {           "name":"MaximumAllowedStorage",           "description":"Thestoragelimitinthevirtualstoragemedium,",           "valueType":"integer",           "configurable":true,           "minCardinality":1,           "maxCardinality":1,           "isUnique":true,           "resourceSpecCharacteristicValue":[               {                   "valueType":"integer",                   "value":1024000               },               {                   "valueType":"integer",                   "value":2048000               }           ]       }   ]}------------------------------JonathanGoldbergAmdocsManagementLimitedAnyopinionsandstatementsmadebymeonthisforumarepurelypersonal,anddonotnecessarilyreflectthepositionoftheTMForumormyemployer.OriginalMessage:Sent:Jul21,202002:48From:waichowSubject:UnderstandingTMF633(howtodeclaresimpleservicespecification)Hi,I'mnewtoTMForumandevaluatehowtorevampinhouseSOMapplicationbasedonTMF633/TMF641/TMF638.IreadTMF633ServicecatalogmanagementAPIRESTspecification(release18.5.0/pp21,27-29)butIhavenogluehowtodeclare/representsimple(keyvalue)servicespecification.Forsimple/standaloneservicespecwithoutanyservicedependency,shouldIdeclareeverythinginServiceSpecification/ServiceSpecCharacteristic/ServiceSpecCharacteristicValue?Regards------------------------------WaiChowPCCWSolutionsLimited------------------------------ × NewBestAnswer Thisthreadalreadyhasabestanswer.Wouldyouliketomarkthismessageasthenewbestanswer? No Copyright2019TMForum.Allrightsreserved.ViewourWebsiteT&CsandPrivacyPolicy. PoweredbyHigherLogic



請為這篇文章評分?