The Dublin Core Metadata Element Set
RFC 5013

Note: This ballot was opened for revision 07 and is now closed.

Lars Eggert No Objection

Comment (2007-05-07)
No email
send info
agree with Russ' comment - the wording should be changed

(Chris Newman; former steering group member) (was No Objection) Yes

Yes (2007-05-10)
No email
send info
The inclusion of a language attribute makes this comply with section 4 of
RFC 2277 / BCP 18.  Section 3 of RFC 2277 / BCP 18 doesn't apply because
this is too high level to discuss charsets (it describes meta information
without describing the encoding of that information when it is applied
to a specific protocol context).  When this is mapped to vanilla XML
or XHTML, for example, it would need to comply with the XML charset
requirements (support for both UTF-8 and UTF-16).  When used in an IETF
protocol, we would expect support for UTF-8.

It also uses an international date format, although the syntax is
somewhat more liberal than RFC 3339.  The more liberal syntax is
suitable for such a high level document as the accuracy necessary for
RFC 3339 format may not be available in this context.

I conclude this complies with our internationalization and date-time
requirements.

(Lisa Dusseault; former steering group member) Yes

Yes ( for -)
No email
send info

(Dan Romascanu; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ( for -)
No email
send info

(David Ward; former steering group member) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ()
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection (2007-05-07)
No email
send info
  This document is intended for publication as an Informational RFC. It
  is not an IETF standards-track document.  I wonder if we are going to
  confuse the reader by using the word "standard" when this document
  refers to itself.  
  - Section 2: The fifteen element "Dublin Core" described in this
    standard ...
  - Section 3: The elements described in this standard ...
  - Section 3: ... implementation detail is outside the scope of this
    standard.
  - Appendix A:  This appendix is not part of the standard.
  - Appendix B:  This appendix is not part of the standard.

(Tim Polk; former steering group member) No Objection

No Objection ()
No email
send info

(Cullen Jennings; former steering group member) (was Discuss) No Record

No Record ()
No email
send info