Context Navigation

Changes between Version 1 and Version 2 of IdsAdiAvalonCollabInterests

Timestamp:: 06/25/09 13:00:32 (15 years ago)
Author:: ianglendinning (IP: 193.212.132.34)
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

IdsAdiAvalonCollabInterests

v1	v2
15	15
16	16	These are specific interest areas of the members
17		(See also ~~the general subject areas already recognized~~.)
	17	(See also [https://www.posccaesar.org/wiki/IdsAdiAvalonCollab the subject areas already recognized].)
18	18
19	19	Adrian Laud (Noumenon)
…	…
39	39
40	40	Ivo Willems (Fluor)
41		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 ~~compliance guideline~~ concerns the change management "round tripping" aspects of any batch or asynchronous transaction.)
	41	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.)
42	42
43		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 “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.
44
45
46
47
48
49
	43	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.
50	44
51	45	----