Changes between Version 5 and Version 6 of ISO15926inOWLConventionalLiterals

Show
Ignore:
Timestamp:
06/18/08 07:44:59 (16 years ago)
Author:
jbourne (IP: 70.54.77.119)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISO15926inOWLConventionalLiterals

    v5 v6  
    142142Now, consider the case that a supplier adjusts an equipment specification datum, or an EPC continues to make modifications to a design during commissioning.  Data is again flowing.  That new data must correlate and "patch" the existing data in an efficient, and fault-free manner.  If we need to rename identifiers, then we have just introduced a substantial complexity to that act of patching the data efficiently and flawlessly. 
    143143 
    144 Not only must it "patch" the first system it encounters, it needs to patch every successive downstream system reliably and consistently.  Not only that, but what about full circle actions?  Isn't it possible that an ERP system might make direct contact with an OEM system using part 7 passed through this long chain?  Isn't it possible that an aMDM system might consult the original standard reference against which an OEM categorized their equipment for more details or as the basis for a search for substitute equipment? 
     144Not only must it "patch" the first system it encounters, it needs to patch every successive downstream system reliably and consistently.  Not only that, but what about full circle actions?  Isn't it possible that an ERP system might make direct contact with an OEM system using part 7 passed through this long chain?  Isn't it possible that an AIM system might consult the original standard reference against which an OEM categorized their equipment for more details or as the basis for a search for substitute equipment? 
    145145 
    146146So long story short, given that data is being continually merged from multiple sources, sometimes from the same source again and again, it is untenable for the identifiers to change or collide.  Given that it is unreasonable to create a central registry of literals (for security, scalability and performance reasons), it is not far fetched to say that it is adviseable that literals are not identified at all, unless they absolutely must be for the relationships that they participate in. 
Home
About PCA
Reference Data Services
Projects
Workgroups