OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cam message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Overlap between OASIS CAM templates and BTRI NIEM / IEPD


Just FYI - 

http://niem.gtri.gatech.edu/niemtools/resources/docs/NIEM_IEPD_Reqs_v2-1.doc

Seems like CAM templates are a perfect match for NIEM / IEPD requirements,

DW

======================
2.3	Enhance IEPD consistency and readability community wide
An IEPD must be human readable as well as machine readable so that it can be parsed easily for automatic processing tasks such as registration, content assembly/disassembly, search and navigation, etc.  The IEPD specification must provide a consistent format for identifying and defining each artifact contained in an IEPD.  Furthermore, an IEPD may have mandatory, conditionally mandatory, or optional artifacts to support various business contexts for which it was designed.
  
2.4	Facilitate IEPD interoperability and portability
To maximize IEPD utility, the IEPD specification must enhance sharing and reuse.  An IEPD must be portable, self-contained, and self-documented.  It must contain its own documentation to explain specifically how it is to be used, and its own metadata to enable it to be easily registered anywhere.  It must be packaged in a common, open standard format and each artifact should be easy to identify, examine, understand, and use.  An IEPD and the artifacts it contains should be independent of specific tools, applications, or systems to the maximum practical extent.  

2.5	IEPDs capture business context 
Business context is used for search, discovery, and navigation in a repository or IEPDs, and to understand how and which IEPDs can be used in particular business exchanges.  



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]