Loading ...
Sorry, an error occurred while loading the content.

FW: RFC 3937 on A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC)

Expand Messages
  • Misha Wolf
    fyi Misha Wolf Standards Manager Product and Platform Architecture Group Reuters ... From: rfc-dist-bounces@mailman.rfc-editor.org
    Message 1 of 1 , Nov 2, 2004
    • 0 Attachment
      fyi


      Misha Wolf
      Standards Manager
      Product and Platform Architecture Group
      Reuters


      -----Original Message-----
      From: rfc-dist-bounces@...-editor.org
      [mailto:rfc-dist-bounces@...-editor.org] On Behalf Of
      rfc-editor@...
      Sent: 01 November 2004 17:20
      To: rfc-dist@...
      Cc: rfc-editor@...
      Subject: [rfc-dist] RFC 3937 on A Uniform Resource Name (URN) Namespace
      for the International Press Telecommunications Council (IPTC)


      A new Request for Comments is now available in online RFC libraries.


      RFC 3937

      Title: A Uniform Resource Name (URN) Namespace for
      the International Press Telecommunications Council
      (IPTC)
      Author(s): M. Steidl
      Status: Informational
      Date: October 2004
      Mailbox: mdirector@...
      Pages: 9
      Characters: 15458
      Updates/Obsoletes/SeeAlso: None

      I-D Tag: draft-steidl-iptc-urn-00.txt

      URL: ftp://ftp.rfc-editor.org/in-notes/rfc3937.txt


      This document describes a URN (Uniform Resource Name) namespace for
      identifying persistent resources published by the International Press
      Telecommunications Council (IPTC). These resources include XML Data
      Type Definition files (DTD), XML Schema, Namespaces in XML, XSL
      stylesheets, other XML based document and documents of other data
      formats like PDF documents, Microsoft Office documents and others.

      This memo provides information for the Internet community. It does
      not specify an Internet standard of any kind. Distribution of this
      memo is unlimited.

      This announcement is sent to the IETF list and the RFC-DIST list.
      Requests to be added to or deleted from the IETF distribution list
      should be sent to IETF-REQUEST@.... Requests to be
      added to or deleted from the RFC-DIST distribution list should
      be sent to RFC-DIST-REQUEST@....

      Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
      an EMAIL message to rfc-info@... with the message body
      help: ways_to_get_rfcs. For example:

      To: rfc-info@...
      Subject: getting rfcs

      help: ways_to_get_rfcs

      Requests for special distribution should be addressed to either the
      author of the RFC in question, or to RFC-Manager@.... Unless
      specifically noted otherwise on the RFC itself, all RFCs are for
      unlimited distribution.

      Submissions for Requests for Comments should be sent to
      RFC-EDITOR@.... Please consult RFC 2223, Instructions to RFC
      Authors, for further information.


      Joyce K. Reynolds and Sandy Ginoza
      USC/Information Sciences Institute

      ...

      Below is the data which will enable a MIME compliant Mail Reader
      implementation to automatically retrieve the ASCII version
      of the RFCs.



      --------------------------------------------------------------- -
      Visit our Internet site at http://www.reuters.com

      Get closer to the financial markets with Reuters Messaging - for more
      information and to register, visit http://www.reuters.com/messaging

      Any views expressed in this message are those of the individual
      sender, except where the sender specifically states them to be
      the views of Reuters Ltd.
    Your message has been successfully submitted and would be delivered to recipients shortly.