XML Community of Practice (Discussion Draft)XML Community of Practice (Discussion Draft)xmlCoP_0f35d21e-6830-46a4-9b78-6e93b60a4aadA future in which the format in which information is created and stored is no impediment to its usage and sufficient agreement exists concerning the semantics (meaning) of elements to enable communities of interest to communicate efficiently and effectively._da5b0fd2-3e59-4d24-9ca7-a17944c3af21To accelerate, facilitate and catalyze the effective and appropriate implementation of XML technology in the information systems and planning of the Federal Government._e8a0cab8-2819-4755-ae66-12f5dcbbe144Ongoing EvolutionIn recognition of the relatively new and dynamic nature of the technology, we were asked to develop an "evolving" strategy. Beyond the initial iteration of the plan and set of tasks, no further deadlines have been specified nor is "completion" of the plan contemplated in the sense that no further changes can be anticipated.Online Documentation of Strategy and ResultsOur strategy is to be defined and documented at xml.gov. Our Web site is both the embodiment of our strategic plan as well as a primary means of implementing it. All of our significant accomplishments should be documented on the site, meaning that it also constitutes a record by which to assess the results we have achieved. Openness and VolunteerismThere are no qualifications for participation in the xmlCoP nor any mandate for anyone to do so.Fiscal ScarcityThe financial resources available to the Working Group are quite limited. We are largely reliant upon GSA for financial support. Funding for the XML Registry was included in GSA's budget for FY 2004 but was not approved by Congress. Non-Policy and Non-Operational FocusWe are not a policy-making body nor were we chartered to take on operational responsibilities. Identification of Project/Task DeliverablesIn a charter revision, the CIO Council's Architecture and Infrastructure Committee (AIC) instructed us to take a more operational orientation, in the sense of identifying specific project/task deliverables.Voluntary Consensus StandardsIn accordance with OMB Circulars A-76 and A-119, whenever possible, agencies should use voluntary consensus standards developed in partnership with commerce and industry.Support for Policy InitiativesOur strategic activities should support the policy initiatives of the Administration, including for example the Citizen-Centered eGovernment Action Plan and OMB's information quality guidelines. Limited Scope with Extended VisionOur extended and revised charter expires on November 30, 2008. We should not assume that it will be extended and should scope our objectives accordingly, while at the same time considering how best to facilitate necessary followup and further value-additive activities that may be warranted beyond that date.XML Best Practices and Recommended StandardsXML Best Practices and Recommended Standards_d2adbba9-985e-4279-b08b-c7aa42a764121Update/Expand Previous DraftIn March 2001, Scott Hoffman of Tibco/Extensibility provided a short draft outlining four suggested "XML Best Practices in Regard to Development and Interoperability." That document is available at http://www.xml.gov/documents/completed/xml_best_practices.htm This objective, if it is adopted, would be to update and expand that list._8c3382a2-40fe-4641-9fcf-90f59cf8fc7c1A set of best practices for XML schemas compiled by participants in the xml-dev listserv is available at http://www.xfront.com/BestPracticesHomepage.html ET.gov and FEA TRMUse the ET.gov site and process to identify and propose XML-related specifications for inclusion in the Federal Enterprise Architecture (FEA) Technical Reference Model (TRM)._a2ccf52d-78f6-4ffe-aeee-47a78d3521812The ET.gov site is available at http://et.gov/, where information on eight-stage process can be found. The mapping for XML in the TRM is provided at http://xml.gov/efforts.asp Components and specifications that have been mapped to XML at ET.gov can be discovered at http://etgov.i411.com Integration of ET.gov, Standards.gov, and FEA TRMIf this objective is adopted, the purpose would be to use XML to integrate the process by which ET.gov is used to identify potential standards for inclusion in the FEA TRM with the processes by which changes to the FEA are considered and approved as well as the process by which data are gathered for the reports gathered and posted at Standards.gov in compliance the OMB Circular A-119._f906e969-318d-49ad-8b48-b88817a27b433See also desirable enhancements 6.4 and 7 at http://et.gov/history/enhancementrequirements.htmIndustry and Public Interest Group PartnershipsPartnerships with Key Industry and Public Groups Developing XML Standards and Specifications _ca7c7c64-ef26-4a5d-be8a-c7c2a57879fa2OASISIf this objective is adopted, the purpose would be to determine how to partner more effectively with OASIS._11b04853-dd62-42cd-936b-8eea02d3e81a1A link to OASIS's Web site is provided at http://xml.gov/related_links.asp. A more explicit link to OASIS standards is provided at http://xml.gov/index.asp#oasis and links to OASIS events are commonly provided at http://xml.gov/index.asp#new However, the xmlCoP does not have membership in OASIS nor does OASIS have any formal liaison or other connection to the xmlCoP.W3CIf this objective were adopted, the purpose would be to explore prospects for more formal and potentially productive relationships with the W3C._62eebcca-2897-4bc6-947d-b6f5aad1faf32A link to W3C technical reports and publications is provided at http://xml.gov/index.asp#w3c AIIM iECM CommitteeAIIM's Interoperable Enterprise Content Management (iECM) committee is developing a "standards road map" related to enterprise content management applications and service components. A subtask of that initiative is to identify and, as necessary, specify additional XML tags for all of the elements of metadata conceptually identified in ANSI/AIIM/ARMA TR48-2006. If this objective were to be adopted, potential purposes include encouraging wider participation among .gov agencies in the iECM committee, focusing attention of xmlCoP participants on the metadata subtask, and/or seeking inclusion of the iECM metadata specification in the FEA TRM and/or DRM. _fa13d36a-3525-4e46-9229-05d4dae2d7693Additional information on the iECM committee is available at http://www.aiim.org/standards.asp?ID=29284Intergovernmental PartnershipsPartnerships with Governmental Communities of Interest to Accelerate the Delivery of XML Benefits_f7d44aab-6fca-4a6f-86d5-0421f896cf3d3XBRL CoPStrengthen collaboration with or accept the XBRL CoP into the xmlCoP as a formally recognized participant._9e0c075a-c5ec-4dee-8cf5-26c46313b3c21The XBRL CoP's collaborative site is at https://usgovxbrl.webexone.com/login.asp?loc=&link=%2Fdefault%2Easp%3F Collaborative Expedition WorkshopsIf this objective were adopted, the purpose would be to more formally integrate the activities of the xmlCoP into the ongoing series of regularly scheduled CollabEx workshops._ccd409b2-0175-4863-8292-7f3c66db38fe2Information on the workshops is available at http://colab.cim3.net/cgi-bin/wiki.pl?ExpeditionWorkshopEducation and OutreachResults-Oriented Education and Outreach_d272c3f6-f335-4b7f-9374-02c2022542a94xml.gov SiteThe xml.gov site is the primary means by which the xmlCoP shares information with stakeholders._aaa4f3a2-481b-4a5f-8884-4d94b1ac767f1xmlCoP ListservThe xmlCoP has a listserv that is used primarily for announcements of general interest to subscribers. Subscription to the listserv has not been promoted and has been declining recently. Potential objectives include promoting subscription and/or using the list more actively for dialog on issues that may or may not be of interest to many subscribers._e146e8cc-fa55-4af1-a3f3-8f18dedae9622The listserv archives are available at http://listserv.gsa.gov/cgi-bin/wa.exe?A0=XMLWG and individuals can subscribe, unsubscribe, or change their subscription options there.MeetingsDuring the first six years of its existence, the xmlCoP met virtually every month to receive presentations and engage in discussion. The purpose of this objective would be to determine whether to resume meeting regularly and, if so, whether to limit participation in portions or all of some meetings to .gov employees only._fe296d40-af7a-4a46-b79c-bb0e5f8ab76e3Information on the xmlCoP's meeting schedule and links to the agendas for all meetings conducted in the past are available at http://xml.gov/agendas.asp Minutes and meeting notes from all of those meetings are available at http://xml.gov/minutes.aspTutorials PageIf this objective were to be adopted, the purpose would be to determine whether and, if so, how to update and enhance the links provided at http://xml.gov/tutorials.asp _13d64929-9716-43de-b55e-dcd00ff2c4674Multi-Agency Projects and ProductsEncourage Projects and Products Benefiting Stakeholders of Multiple Agencies_da8b2a15-f133-4dfb-85cf-d9298714ce6d5Although the xmlCoP does not take on operational responsibilities, we do encourage others to initiate, lead, and operate XML-related projects and services benefiting multiple agencies.ET.gov Site/ProcessThe purpose of the ET.gov site and process is to facilitate the identification, discovery, and formation of communities of practice (CoPs) around emerging technology (ET) components and specifications of interest to government agencies. The purpose of this objective, if it were to be adopted, would be to engage the xmlCoP more consistently and perhaps more formally in reviewing and perhaps encouraging the formation of CoPs around XML-related components and specifications identified in the ET.gov process. A related but separate objective might be to review and seek resources to implement some or all of the potential enhancements to the ET.gov site._b96e06c7-7e79-4119-8610-e4458a336ef61See http://et.gov/ and http://et.gov/history.htm and particularly http://et.gov/history/enhancementrequirements.htm StratMLStrategy Markup Language (StratML) is an XML vocabulary and schema for strategic plans. Its purposes include but may not be limited to the following: - Facilitate the sharing, referencing, indexing, discovery, linking, reuse, and analyses of the elements of strategic plans, including goal and objective statements as well as the names and descriptions of stakeholder groups and any other content commonly included in strategic plans. - Enable the concept of "strategic alignment" to be realized in literal linkages among goal and objective statements and all other records created by organizations in the routine course of their business processes. - Facilitate the discovery of potential performance partners who share common goals and objectives and/or either produce inputs needed or require outputs produced by the organization compiling the strategic plan. - Facilitate stakeholder feedback on strategic goals and objectives. - Facilitate updating and maintenance of discrete elements of strategic plans without requiring review and approval of the entire plan through bureaucratic channels, thereby helping to make the strategic planning process more agile and responsive to stakeholder feedback and changing circumstances, thus helping to overcome the tendency of strategic plans to become outdated "shelfware". - Reduce the needless time, effort, inconsistencies, and delays associated with maintaining data redundantly in myriad "stovepipe" systems rather than referencing the authoritative sources._53fd075e-eea0-408a-b6b2-5afd754fbc812See http://xml.gov/stratml/index.htmXML Registry ServicesIf this objective were adopted, the purpose would be to determine whether to endeavor to renew the President's budget request for the registry and/or to pursue other alternatives, e.g., encouraging agencies, LOBs, and eGov project managers to post their schemas on the Web so that value-added service providers (e.g., USA.gov) can index them and facilitate discovery and reuse of the elements and schema fragments they contain._85c62c9a-1ced-4342-9e0a-747f7d1561243See http://xml.gov/registries.asp XML NDRGIf this objective were adopted, the purpose would be to determine what, if anything further, to do to foster the adoption and use of XML Naming and Design Rules and Guidelines (NDRG), perhaps in partnership with the CIO/AIC's Data Architecture Subcommittee (DAS)._22a57477-57f7-4fc6-a153-8870cb58f0d64See references at http://usasearch.gov/search?affiliate=xml.gov&v%3Aproject=firstgov&query=NDRG See also https://collab.core.gov/CommunityBrowser.aspx?id=2234 and http://www.mel.nist.gov/msid/XML_testbed/tools.html At the latter site, see especially http://www.mel.nist.gov/msid/XML_testbed/QOD.html RMSCIf this objective were adopted, the purpose might be to explore prospects for leveraging the work of AIIM's iECM committee, and particularly the XML metadata task group, in the Records Management Service Components (RMSC) being developed by NARA under the auspices of the President's eGov initiatives._921f7721-51d3-4229-90c6-67c5ed9908a65See http://www.archives.gov/era/pdf/rmsc-overview.pdf The relationship of the RMSC to the ET.gov process is outlined at http://xml.gov/documents/completed/firm/20070320pechakucha/RMSC.htm2007-10-012008-11-302010-02-08http://xml.gov/documents/in_progress/strategy.htmArthurColman (www.drybridge.com)colman@drybridge.com