FEA DRM XML Schema Draft Version 0.3

Drafts: Updated FEA DRM XML Schema (0.3) and Sample XML Instance Document

From:      Chiusano Joseph  <chiusano_joseph@bah.com>
To:        [drm-team] ; DRM comment reconciliation team
Sent:      Friday, December 16, 2005 5:02 PM
Subject:   [drm-team] Updated DRM XML Schema / Sample XML Instance Document    (03)

DRM Team, (04)

Over the past several weeks, I have been updating the DRM XML Schema (at Mike Daconta's request) to bring it in line with the DRM 2.0 abstract model. Attached is the updated XML schema, along with a sample XML instance document. Please note that this schema is not official (it is only a first cut), as it has not been vetted within any community. (05)

If you have comments on this schema: Unless more official instructions are conveyed, I would recommend that you either note them and hold on to them for future use, or send them to the red-time list (see "To:" line for address) so that they are recorded and archived. As our DRM 2.0 period is closing out, there are no planned further updates of this schema at this time. (06)

Items to note: (07)

- The XML schema does not take into account public comments that had been received on the DRM XML Schema Version 0.2; however, some comments may now be moot given the restructuring and removal of items from the schema. - The sample XML document contains generic values, and lists 2 iterations of any repeating element/element group; - For highlights of the updates that were made, please see below; - I placed a good amount of information in the schema header regarding the conventions used in the schema, and other aspects; (08)

Lastly: It has been a great pleasure working with all of you on the DRM these past 10 months. I wish that our paths may cross again soon, and may you and yours enjoy a wonderful holiday season. (09)

Kind Regards, Joe (010)

HIGHLIGHTS OF UPDATES: (011)

(1) General: (012)

- Replaced all "href" elements with more descriptively-named elements; (013)

- Replaced all "rdf:id" elements with an attribute "ID", of type "xsd:id" (we were not using rdf:id properly in the previous version - it is not intended as a "ref" in an XML schema, it is intended to be placed on a node element); (014)

- Updated all relationships between concepts to reflect abstract model; (015)

(2) Dublin Core schema import: Pointed to schema URL from Dublin Core site, rather than relying on a downloaded schema; (016)

(3) W3C XML schema import: Removed (not needed, as schema processors automatically include this schema); (017)

(4) Element "Data": Removed, for compliance with DRM 2.0 (i.e., DRM 2.0 does not discuss a "Data" concept); (018)

(4) Element "DataAssetType": Renamed to "TypeOfDataAsset" to avoid confusion with the complex type "DataAssetType" that is defined in the schema; (019)

(5) Element "DataStandards" (and related elements): Removed for the time being, as it is not in the abstract model and there have been some questions in the past about the purpose of this element; (020)

(6) Element "Encryption": Renamed to "MinimumEncryptionLevel", for more specificity; (021)

(6) Element "Endpoint": Changed type from xsd:string to xsd:anyURI; (022)

(7) Element "ExternalEntitiesRefs": Represented as "ExternalEntities" element; also created a corresponding "InlineEntities" element. Same idea for "ExternalExchangePackageRefs", "ExternalResourcesRefs", and "ExternalTaxonomyRefs" elements. (023)

(10) Element "FEAMapping" (and related elements): Removed for the time being, as there has been discussion of representing FEA reference models as taxonomies. May want to add a flag in the future indicating whether a taxonomy is an FEA reference model or not. (024)

(11) Element "NodeChildren": Purpose of this element is now handled by the "TopicRelationship" element; (025)

(12) Element "Nodes" (and related elements): Represented as "Topics" element; (026)

(13) Element "PayloadRef": Changed to a URI that points to an external representation, such as an XML schema; (027)

(14) Element "QualityOfService": Renamed to "QualityOfServiceInformation", for more specificity; (028)

(15) Element "Recipient": Represented as "Consumer"; (029)

(16) Element "Relationships": Replaced with "EntityRelationships" and "TopicRelationships" elements for more specificity; also simplified the representations. (030)

(17) Element "ReliableMessaging": Renamed to "ReliableMessagingCapabilities" , for more specificity; (031)

(18) Element "ResourceRefs": Represented as "DigitalDataResourceRefs"; (032)

(19) Element "Resources": Represented as "UnstructuredDataResources"; (033)

(20) Element "ResultFormat": Removed, as its purpose is covered by "PayloadRef" element on ExchangePackage; (034)

(21) Element "Security": Renamed to "QueryPointSecurity", for more specificity; (035)

(22) Element "SemiStructuredData": Represented as "SemiStructuredDataResource"; (036)

(23) Element "Sender": Represented as "Supplier"; (037)

(24) Element "Steward": Represented as "DataSteward"; (038)

(25) Element "StructuredData": Represented as "StructuredDataResource"; (039)

(26) Element "SubmissionMetadata": Changed name to "SubmissionInformation" (friendlier name); (040)

(27) Element "UnstructuredData": Represented as "UnstructuredDataResource"; (041)

(28) Complex type "DataReferenceModelType": Removed "xml:base" attribute (no longer needed - see "rdf:id" update above); (042)

(29) Complex type "QueryPoint": Removed "TransactionType" element as it is specified on "ExchangePackage" element; (043)

(30) Complex type "QueryPoint": Removed "Status" element as it is specified on "ExchangePackage" element; (044)

Kind Regards,
Joseph Chiusano
Associate
Booz Allen Hamilton (045)

700 13th St. NW, Suite 1100
Washington, DC 20005
O: 202-508-6514
C: 202-251-0731
Visit us online@ http://www.boozallen.com (046)

Attachment: Draft_FEA_DRM_XML_Schema_v.0.3.xsd
FEA Data Reference Model (DRM) Schema Draft Version 0.3 [source]
Description: text/xml

Attachment: Sample_FEA_DRM_Instance_v.0.3.xml
Sample XML instance for FEA Data Reference Model (DRM) Schema Draft Version 0.3 [source]

[Source: http://colab.cim3.net/forum/ontac-forum/2005-12/msg00086.html]

Prepared by Robin Cover for The XML Cover Pages archive. See details in the news story: "U.S. Federal Enterprise Architecture Data Reference Model (DRM) Version 2.0."

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	FEA DRM XML Schema Draft Version 0.3 Drafts: Updated FEA DRM XML Schema (0.3) and Sample XML Instance Document From: Chiusano Joseph <chiusano_joseph@bah.com> To: [drm-team] ; DRM comment reconciliation team Sent: Friday, December 16, 2005 5:02 PM Subject: [drm-team] Updated DRM XML Schema / Sample XML Instance Document (03) DRM Team, (04) Over the past several weeks, I have been updating the DRM XML Schema (at Mike Daconta's request) to bring it in line with the DRM 2.0 abstract model. Attached is the updated XML schema, along with a sample XML instance document. Please note that this schema is not official (it is only a first cut), as it has not been vetted within any community. (05) If you have comments on this schema: Unless more official instructions are conveyed, I would recommend that you either note them and hold on to them for future use, or send them to the red-time list (see "To:" line for address) so that they are recorded and archived. As our DRM 2.0 period is closing out, there are no planned further updates of this schema at this time. (06) Items to note: (07) - The XML schema does not take into account public comments that had been received on the DRM XML Schema Version 0.2; however, some comments may now be moot given the restructuring and removal of items from the schema. - The sample XML document contains generic values, and lists 2 iterations of any repeating element/element group; - For highlights of the updates that were made, please see below; - I placed a good amount of information in the schema header regarding the conventions used in the schema, and other aspects; (08) Lastly: It has been a great pleasure working with all of you on the DRM these past 10 months. I wish that our paths may cross again soon, and may you and yours enjoy a wonderful holiday season. (09) Kind Regards, Joe (010) HIGHLIGHTS OF UPDATES: (011) (1) General: (012) - Replaced all "href" elements with more descriptively-named elements; (013) - Replaced all "rdf:id" elements with an attribute "ID", of type "xsd:id" (we were not using rdf:id properly in the previous version - it is not intended as a "ref" in an XML schema, it is intended to be placed on a node element); (014) - Updated all relationships between concepts to reflect abstract model; (015) (2) Dublin Core schema import: Pointed to schema URL from Dublin Core site, rather than relying on a downloaded schema; (016) (3) W3C XML schema import: Removed (not needed, as schema processors automatically include this schema); (017) (4) Element "Data": Removed, for compliance with DRM 2.0 (i.e., DRM 2.0 does not discuss a "Data" concept); (018) (4) Element "DataAssetType": Renamed to "TypeOfDataAsset" to avoid confusion with the complex type "DataAssetType" that is defined in the schema; (019) (5) Element "DataStandards" (and related elements): Removed for the time being, as it is not in the abstract model and there have been some questions in the past about the purpose of this element; (020) (6) Element "Encryption": Renamed to "MinimumEncryptionLevel", for more specificity; (021) (6) Element "Endpoint": Changed type from xsd:string to xsd:anyURI; (022) (7) Element "ExternalEntitiesRefs": Represented as "ExternalEntities" element; also created a corresponding "InlineEntities" element. Same idea for "ExternalExchangePackageRefs", "ExternalResourcesRefs", and "ExternalTaxonomyRefs" elements. (023) (10) Element "FEAMapping" (and related elements): Removed for the time being, as there has been discussion of representing FEA reference models as taxonomies. May want to add a flag in the future indicating whether a taxonomy is an FEA reference model or not. (024) (11) Element "NodeChildren": Purpose of this element is now handled by the "TopicRelationship" element; (025) (12) Element "Nodes" (and related elements): Represented as "Topics" element; (026) (13) Element "PayloadRef": Changed to a URI that points to an external representation, such as an XML schema; (027) (14) Element "QualityOfService": Renamed to "QualityOfServiceInformation", for more specificity; (028) (15) Element "Recipient": Represented as "Consumer"; (029) (16) Element "Relationships": Replaced with "EntityRelationships" and "TopicRelationships" elements for more specificity; also simplified the representations. (030) (17) Element "ReliableMessaging": Renamed to "ReliableMessagingCapabilities" , for more specificity; (031) (18) Element "ResourceRefs": Represented as "DigitalDataResourceRefs"; (032) (19) Element "Resources": Represented as "UnstructuredDataResources"; (033) (20) Element "ResultFormat": Removed, as its purpose is covered by "PayloadRef" element on ExchangePackage; (034) (21) Element "Security": Renamed to "QueryPointSecurity", for more specificity; (035) (22) Element "SemiStructuredData": Represented as "SemiStructuredDataResource"; (036) (23) Element "Sender": Represented as "Supplier"; (037) (24) Element "Steward": Represented as "DataSteward"; (038) (25) Element "StructuredData": Represented as "StructuredDataResource"; (039) (26) Element "SubmissionMetadata": Changed name to "SubmissionInformation" (friendlier name); (040) (27) Element "UnstructuredData": Represented as "UnstructuredDataResource"; (041) (28) Complex type "DataReferenceModelType": Removed "xml:base" attribute (no longer needed - see "rdf:id" update above); (042) (29) Complex type "QueryPoint": Removed "TransactionType" element as it is specified on "ExchangePackage" element; (043) (30) Complex type "QueryPoint": Removed "Status" element as it is specified on "ExchangePackage" element; (044) Kind Regards, Joseph Chiusano Associate Booz Allen Hamilton (045) 700 13th St. NW, Suite 1100 Washington, DC 20005 O: 202-508-6514 C: 202-251-0731 Visit us online@ http://www.boozallen.com (046) Attachment: Draft_FEA_DRM_XML_Schema_v.0.3.xsd FEA Data Reference Model (DRM) Schema Draft Version 0.3 [source] Description: text/xml Attachment: Sample_FEA_DRM_Instance_v.0.3.xml Sample XML instance for FEA Data Reference Model (DRM) Schema Draft Version 0.3 [source] [Source: http://colab.cim3.net/forum/ontac-forum/2005-12/msg00086.html] Prepared by Robin Cover for The XML Cover Pages archive. See details in the news story: "U.S. Federal Enterprise Architecture Data Reference Model (DRM) Version 2.0."