Changes between Version 4 and Version 5 of IdsAdiAvalonCollabInterests

Timestamp:

06/25/09 13:42:22 (15 years ago)

Author:

ianglendinning (IP: 193.212.132.34)

Comment:

--

IdsAdiAvalonCollabInterests

@@ -44 +44 @@
 Exchange ''and'' collaboration – (and not just iRING technology ?) Business context … eg EDI exchange per Mike’s comment above. Meta-content / wrapper. (Response - See the responses on this work being independent of the technologies. Need to focus on the content and not get side-tracked on all the business collaboration and interoperability aspects here - HOWEVER note that one aspect / axis of the [https://www.posccaesar.org/wiki/IdsAdiComplianceSpecification compliance guideline] concerns the change management "round tripping" aspects of any batch or asynchronous transaction.)
 
-Andy Till (BP) – The progress on defining "hand-off" between suppliers and EPC’s impressive. We should also be concerned with lower levels of business maturity / expectations – maybe shallower implementations. Business drivers for EPC’s and OO’s may be subtly different – Design vs  & O&M & legal / records. Is there an “OO Datasheet” … distinct from design and procure ? (Responses - How to’s do consider [https://www.posccaesar.org/wiki/IdsAdiComplianceSpecification compliance levels] and business maturity to adoption. Technology aspects of compliance levels are NOT RELEVANT to this content collaboration Wiki scope - iRING or XML Schemas or other implementation choices are not limiting here - the content issues concern the analysis and mapping of content need to support business scopes.
+Andy Till (BP)
+The progress on defining "hand-off" between suppliers and EPC’s impressive. We should also be concerned with lower levels of business maturity / expectations – maybe shallower implementations. Business drivers for EPC’s and OO’s may be subtly different – Design vs  & O&M & legal / records. Is there an “OO Datasheet” … distinct from design and procure ? (Responses - "How to’s" do consider [https://www.posccaesar.org/wiki/IdsAdiComplianceSpecification compliance levels] and business maturity to adoption. Technology aspects of compliance levels are NOT RELEVANT to this content collaboration Wiki scope - iRING or XML Schemas or other implementation choices are not limiting here - the content issues concern the analysis and mapping of content needed to support business scopes.
 
 ----