idnits 2.17.1 draft-ietf-webdav-dublin-core-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([WEBDAV], [DUBLIN]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 5, 1998) is 9335 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Bradner' is mentioned on line 194, but not defined -- Looks like a reference, but probably isn't: '1996' on line 194 ** Obsolete normative reference: RFC 2413 (ref. 'DUBLIN') (Obsoleted by RFC 5013) -- Possible downref: Non-RFC (?) normative reference: ref. 'WEBDAV' -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 WEBDAV Working Group J. Stracke, Netscape 2 INTERNET DRAFT October 5, 1998 3 5 Expires April, 1999 7 Use of Dublin Core Metadata in WebDAV 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or made obsolete by other 18 documents at any time. It is inappropriate to use Internet-Drafts as 19 reference material or to cite them other than as "work in progress". 21 To view the entire list of current Internet-Drafts, please check 22 the "1id-abstracts.txt" listing contained in the Internet-Drafts 23 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 24 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 25 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 26 (US West Coast). 28 Distribution of this document is unlimited. Please send comments to 29 the Distributed Authoring and Versioning (WEBDAV) working group at 30 , which may be joined by sending a message 31 with subject "subscribe" to . 33 Discussions of the WEBDAV working group are archived at 34 . 36 Abstract 38 This document specifies a standard mapping for using the metadata 39 vocabulary of Dublin Core ([DUBLIN]) in a WebDAV ([WEBDAV]) server. 41 Contents 43 STATUS OF THIS MEMO 1 44 ABSTRACT 1 45 CONTENTS 2 47 1 INTRODUCTION 2 49 2 MAPPING 3 51 2.1 NAMESPACE 3 53 2.2 PROPERTY NAMES 3 55 2.3 PROPERTY FORMAT 3 57 2.4 SUBELEMENTS 3 59 3 INTERNATIONALIZATION CONSIDERATIONS 4 61 4 SECURITY CONSIDERATIONS 4 63 5 IANA CONSIDERATIONS 4 65 6 COPYRIGHT 4 67 7 INTELLECTUAL PROPERTY 5 69 8 ACKNOWLEDGEMENTS 5 71 9 REFERENCES 6 73 9.1 NORMATIVE REFERENCES 6 75 9.1 INFORMATIONAL REFERENCES 6 77 10 AUTHORS' ADDRESSES 6 79 1 Introduction 81 This document specifies a standard mapping for using the metadata 82 vocabulary of Dublin Core ([DUBLIN]) in a WebDAV ([WEBDAV]) server. 84 WebDAV defines a protocol for manipulating metadata on a Web 85 resource; in WebDAV, an element of metadata is called a property. 86 Dublin Core defines several metadata elements, with standard names 87 and standard meanings. A server which stores Dublin Core metadata 88 for its content may wish to make the metadata available as WebDAV 89 properties; to forestall the emergence of nonstandard ways to 90 provide this functionality, this document defines a standard 91 mapping from Dublin Core element labels into WebDAV property names. 93 2 Mapping 95 2.1 Namespace 97 WebDAV properties are expressed as XML elements ([XML]), using XML 98 namespaces ([XMLNS]) to permit different groups to define sets of 99 properties without interfering with each other. XML namespaces are 100 named by URIs. The Dublin Core datamodel group is defining a 101 namespace for XML tags representing Dublin Core elements; WebDAV 102 properties should use that same namespace. The 103 URI currently proposed for that namespace is 104 . Note that this is 105 currently only a proposal within the datamodel group; if the Dublin 106 Core group as a whole picks a different URI, WebDAV should use that 107 URI. 109 2.2 Property Names 111 A WebDAV property representing a Dublin Core element has the same 112 name as the Dublin Core element label. 114 2.3 Property Format 116 Since a WebDAV property can occur on a resource only once, while a 117 content item may bear more than one instance of a Dublin Core 118 element, some mechanism is needed to represent the multivalued 119 elements in the singlevalued property syntax. The Dublin Core 120 datamodel group is working on defining an XML DTD for this 121 representation; WebDAV properties should use that DTD when it is 122 ready. 124 2.4 Subelements 126 As of this writing, the Dublin Core group is debating how and 127 whether to provide subelements (that is, a technique for 128 structuring metadata elements). Since subelements are not yet 129 standardized, this document cannot yet give a definitive answer on 130 how to integrate them into WebDAV; a future document may be needed. 132 One approach under consideration, set out in [GUENTHER], is to use 133 structured element names (e.g., Creator becomes structured into 134 Creator.PersonalName and Creator.CorporateName); if this approach 135 is adopted, then this document can be applied unchanged, because 136 Creator.CorporateName is a perfectly legal XML tag name. 137 Alternative approaches could include storing structured data in an 138 element; this approach would require a future document specifying a 139 mapping from that structure into XML. 141 3 Internationalization Considerations 143 XML is an inherently internationalizable format, able to express 144 any language or character set; as a result, all WebDAV properties, 145 including the Dublin Core properties defined here, are 146 internationalizable. 148 4 Security Considerations 150 The security considerations of this mapping are those of [DUBLIN] 151 plus those of [WEBDAV]. 153 5 IANA Considerations 155 The namespace defined here is isomorphic to the element namespace 156 defined in [DUBLIN], so this document introduces no new IANA 157 considerations beyond those of [DUBLIN]. 159 6 Copyright 161 The following copyright notice is copied from RFC 2026 [Bradner, 162 1996], section 10.4, and describes the applicable copyright for this 163 document. 165 Copyright (C) The Internet Society April 5, 1998. All Rights 166 Reserved. 168 This document and translations of it may be copied and furnished to 169 others, and derivative works that comment on or otherwise explain it 170 or assist in its implementation may be prepared, copied, published 171 and distributed, in whole or in part, without restriction of any 172 kind, provided that the above copyright notice and this paragraph 173 are included on all such copies and derivative works. However, this 174 document itself may not be modified in any way, such as by removing 175 the copyright notice or references to the Internet Society or other 176 Internet organizations, except as needed for the purpose of 177 developing Internet standards in which case the procedures for 178 copyrights defined in the Internet Standards process must be 179 followed, or as required to translate it into languages other than 180 English. 182 The limited permissions granted above are perpetual and will not be 183 revoked by the Internet Society or its successors or assignees. 185 This document and the information contained herein is provided on an 186 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 187 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 188 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 189 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 190 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 192 7 Intellectual Property 194 The following notice is copied from RFC 2026 [Bradner, 1996], 195 section 10.4, and describes the position of the IETF concerning 196 intellectual property claims made against this document. 198 The IETF takes no position regarding the validity or scope of any 199 intellectual property or other rights that might be claimed to 200 pertain to the implementation or use other technology described in 201 this document or the extent to which any license under such rights 202 might or might not be available; neither does it represent that it 203 has made any effort to identify any such rights. Information on the 204 IETF's procedures with respect to rights in standards-track and 205 standards-related documentation can be found in BCP-11. Copies of 206 claims of rights made available for publication and any assurances 207 of licenses to be made available, or the result of an attempt made 208 to obtain a general license or permission for the use of such 209 proprietary rights by implementors or users of this specification 210 can be obtained from the IETF Secretariat. 212 The IETF invites any interested party to bring to its attention any 213 copyrights, patents or patent applications, or other proprietary 214 rights which may cover technology that may be required to practice 215 this standard. Please address the information to the IETF Executive 216 Director. 218 8 Acknowledgements 220 The triviality of this specification is due to the hard work put 221 into [WEBDAV], [DUBLIN], [XML], and [XMLNS] by their respective 222 authors and working groups. 224 The need for this specification was pointed out (by Jim Whitehead, 225 I think) during the variants discussion held after a meeting of the 226 versioning design team of the WebDAV working group. 228 Thanks to Liz Parrot for alerting me to the question of 229 subelements. 231 9 References 233 9.1 Normative References 235 [DUBLIN] S. Weibel, J. Kunze, C. Lagoze, M. Wolf, "Dublin Core 236 Metadata for Resource Discovery." RFC 2413. Online Computer 237 Library Center; University of California, San Francisco; Cornell; 238 Reuters. September, 1998. 240 [WEBDAV] Y. Y. Goland, E. J. Whitehead, Jr., A. Faizi, 241 S. R. Carter, D. Jensen, "Extensions for Distributed Authoring on 242 the World Wide Web - WebDAV." 243 Draft-ietf-webdav-protocol-08. Internet Draft, work in progress. 244 Microsoft, U.C. Irvine, Netscape, Novell. April, 1998. 246 [XML] T. Bray, J. Paoli, C. M. Sperberg-McQueen, "Extensible 247 Markup Language (XML)." World Wide Web Consortium Recommendation 248 REC-xml-19980210. . 250 9.2 Informational References 252 [XMLNS] T. Bray, D. Hollander, A. Layman, "Name Spaces in XML" 253 World Wide Web Consortium Working Draft, 254 . 256 [GUENTHER] R. Guenther, "Dublin Core Qualifiers/Substructure", 257 . October, 1997. 259 10 AUTHORS' ADDRESSES 261 J. Stracke 262 Netscape Communications Corporation 263 501 E. Middlefield Rd. 264 Mountain View, CA 94043 265 Email: francis@netscape.com