1 / 8

Paul Lunceford 13 April2010 703-885-1380 luncep @fgm

DDMS V3.0. Paul Lunceford 13 April2010 703-885-1380 luncep @fgm.com. Data Services Office Ken Fagan Ken.Fagan@disa.mil. Status and Future. 3.0 still in Pre-Release Awaiting approval of IC/ISM V2 for General Release Must be downloaded for use

kenna
Download Presentation

Paul Lunceford 13 April2010 703-885-1380 luncep @fgm

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DDMS V3.0 Paul Lunceford 13 April2010 703-885-1380 luncep@fgm.com Data Services Office Ken Fagan Ken.Fagan@disa.mil

  2. Status and Future • 3.0 still in Pre-Release • Awaiting approval of IC/ISM V2 for General Release • Must be downloaded for use • INT namespace not available until IC/ISM V2 Approval • IC/ISM approval imminent • Future • No open CRs at this time to brief • IC/ISM is planned for Version 4 release and approval this summer • IC/ISM Version 4 will include DoD CUI markings • DDMS 3.1 planned after IC/ISM Version 4 release • If no outstanding and approved CRs exist at that time, 3.1 will only include IC/ISM Version 4 • DDMS 3.1 will go for acceptance into the DISR following IC/ISM Version 4 acceptance into the ICSR • DDMS 3.0 planned for adoption into IC PUBS V4

  3. Resource tag changes (Mandatory) Namespace and Schema location now reference version 3.0 Data Encoding Specification Version of ISM used (should always be 2 for DDMS 3.0) <ddms:Resource xmlns:ddms="http://metadata.dod.mil/mdr/ns/DDMS/3.0/" xmlns:ICISM="urn:us:gov:ic:ism" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://metadata.dod.mil/mdr/ns/DDMS/3.0/ ../DDMS/3.0/DDMS-v3_0.xsd" ICISM:DESVersion="2" ICISM:resourceElement="true" ICISM:createDate="2010-04-08" ICISM:ownerProducer="USA" ICISM:classification="U"> DDMS Record creation/modification date. DDMS Record has its own security marking attributes that govern the DDMS record, not the asset it describes. Notification that this is the top resource element for the XML file for security markings. If true, the DDMS card is the parent of the XML file. If false, the security markings on this record must be rolled up into the security markings for the XML file as a whole.

  4. Unknown entity and category/keyword extensions Unknown entity now allowed for creator, publisher, contributor, and pointOfContact. Unknown represents that the DDMS record creator was unable to tell if the entity was either a Person, and Organization, or a Web Service. <ddms:publisher ICISM:classification="U" ICISM:ownerProducer="GBR"> <ddms:Unknown> <ddms:name>DON CIO</ddms:name> <ddms:phone>222-555-1212</ddms:phone> <ddms:email>DON.CIO@navy.mil</ddms:email> </ddms:Unknown> </ddms:publisher> <ddms:Subject> <ddms:category ddms:qualifier="http://metadata.dod.mil/mdr/ns/TaxFG/0.75c/Core_Tax_0.75c.owl#Janes_Analysis" ddms:code="Janes_Analysis" ddms:label="Janes Defense &amp; Geopolitics Analysis"amps:Confidence=".88" amps:Percession=".92/"> <ddms:keyword ddms:value="data" amps:Confidence=".98" amps:Percession=".94" amps:Offset="228"/> Notional The Subject tag now allows for attribute extensions on both category and keyword. This allows automated record generators to add new tags concerning the accuracy of the categorizations. Extension attributes that prove to provide generic applicability may be adopted directly into the DDMS standard after testing of that applicability.

  5. geospatialCoverage and RelatedResource tag Optional ISM securityTags now allowed for XML portion marking of geospatialCoverage, temporalCoverage, and virtualCoverage Geospatial coverage tags that identify a country code must now include both the qualifier and the value. <ddms:geospatialCoverage ICISM:classification="U" ICISM:ownerProducer="GBR“> <ddms:GeospatialExtent> <ddms:geographicIdentifier> <ddms:name>United States</ddms:name> <ddms:countryCode ddms:qualifier="http://metadata.dod.mil/mdr/ns/GPAS/codelist/iso3166-1/trigraph" ddms:value="USA"/> </ddms:geographicIdentifier> </ddms:GeospatialExtent> </ddms:geospatialCoverage> <ddms:relatedResources ddms:relationship="http://purl.org/dc/terms/references" ddms:direction="outbound"> <ddms:RelatedResource ddms:qualifier="http://purl.org/dc/terms/URI" ddms:value="http://en.wikipedia.org/wiki/Tank"> <ddms:link xlink:type="locator" xlink:href="http://en.wikipedia.org/wiki/Tank"/> </ddms:RelatedResource> </ddms:relatedResources> If defining RelatedResources, a RelatedResource must be present (removed minOccurs=“0”)

  6. security tag (mandatory changes) and extensions The security tag describes the security markings of the asset the DDMS Record describes, not the record itself. Therefore, it should be excluded from any XML security portion marking rollup procedures and should always be marked as excludeFromRollup=“true” <ddms:security ICISM:classification="U" ICISM:ownerProducer="USA" ICISM:excludeFromRollup="true"/> <armament:FirePower> <armament:range>22 Miles</armament:range> </armament:FirePower> <recordsMgmt:recordHistory> <recordsMgmt:superseeded>http://xxx.xx.xxx/olddocument.doc</recordsMgmt:superseeded> </recordsMgmt:recordHistory> </ddms:Resource> Notional DDMS now allows for more than one extension set.

  7. Questions ?

  8. www.disa.mil

More Related