When we started the wg, we wanted to tightly control the properties that are used for determining identity and reconciliation, hence we defined tag/mfg/mode/serialNumber as part of the crtv vocabulary. This has changed over time so that the wg members are now amenable to using other vocabularies. I'm ok with using the AM property definitions but, at this point it's going to be a big workload for the reconciliation spec implementers to switch to using the AM namespace.
What I'll do is to define the crtv:tag/mfg/model/serialNumber properties as owl:sameAs (e.g. crtv:assetTag owl:sameAs oslc_asset:tag) in the crtvocabulary. This will allow implementers to handle oslc_asset properties gracefully. Thanks ! T Tuan Dang Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common Data Model Internet: [email protected] phone: (919) 224-1242 T/L 687-1242 From: Tuan Dang/Raleigh/IBM@IBMUS To: [email protected], Date: 02/21/2013 10:48 AM Subject: [Oslc-recon] Question from AM workgroup regarding re-use of resource oslc_asset:Asset Sent by: "Oslc-Recon" <[email protected]> from Sheehan Anderson: Hi Tuan Good to hear from you. We added the following properties to the 2.0 specification for your use http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/#manufacturer http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/#model http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/#serialNumber http://open-services.net/wiki/asset-management/OSLC-Asset-Management-Vocabulary/#tag I don't fully understand why you need to contribute your own properties to the Asset resource instead of using these existing properties. Thanks ! T Tuan Dang Tivoli OSLC governance, OSLC Reconciliation workgroup lead, Tivoli Common Data Model Internet: [email protected] phone: (919) 224-1242 T/L 687-1242 _______________________________________________ Oslc-Recon mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-recon_open-services.net
