RFC 3085

URN Namespace for NewsML Resources

📅 published March 2001, from ietf

URN Namespace for NewsML Resources 🦋

okay so the title block first, bestie 💅 It's RFC 3085, published in March 2001 by the Network Working Group. The category is Informational, and it was written by A. Coates (Reuters), D. Allen (IPTC), and D. Rivers-Moore (Rivcom). It doesn't list any obsoletes or updates.

Status of This Memo

This memo is for the Internet community to read as information. It is not an Internet standard of any kind 🌸 and distribution is unlimited.

Copyright (C) The Internet Society (2001). All Rights Reserved. 🎀

Abstract

This doc defines a URN (Uniform Resource Name) namespace for naming NewsML NewsItems ✨ A NewsItem is an information resource that can be written as a NewsML element inside a NewsML document. Those documents follow the NewsML Document Type Declaration (DTD), which the International Press Telecommunications Council (IPTC) defined.

1. Introduction 🧚

NewsML is an XML format for bundling multimedia news resources. The IPTC created it, and version 1.0 got approved on 6 October 2000 💜

The same logical NewsItem can live in several physical places. NewsML lets a NewsItem have multiple URLs, but only one URN. The URN is what uniquely names the resource, so it's the main ID bestie. 🫶

This is a spec for a formal namespace.

2. Specification Template 💖

Namespace ID

"newsml" requested.

Registration Information

  • Registration Version Number: 1
  • Registration Date: 2000-11-07

Declared registrant of the namespace

David Allen ho73@dial.pipex.com IPTC Royal Albert House Sheet Street Windsor SL4 1BE

Declaration of structure

The identifier has the following ABNF[6] specification. This part is literally the grammar, so no vibes here, just exact rules 🤓

NSS = ProviderId ":" DateId ":" NewsItemId ":" RevisionId Update
ProviderId = string
DateId = date
NewsItemId = string
RevisionId = posint
Update = 0*1( "A" / "U" )
date = century year month day
century = ( "0" posdig ) / ( posdig DIGIT )
year = 1*2DIGIT
month = ( 0 posdig ) / ( "1" ( "0" "1" "2" ) )
day = ( 0 posdig ) / ( ( "1" / "2" ) DIGIT ) / "30" / "31"
string = 1*char
char = ALPHA / DIGIT / symbol / escape
symbol = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / ";" /
  "$" / "_" / "!" / "*" / "'"
escape = "%" HEXDIG HEXDIG
posint = posdig *DIGIT
posdig = "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9"

The ProviderId must be an Internet domain name. It must be owned by the organisation that creates the NewsML resource and gives it the URN, at the date given by the DateId.

DateId is a date in ISO 8601 Basic Format (CCYYMMDD). It must match a date when the organisation allocating the URN owned the domain name in the ProviderId.

The NewsItemId must be unique among all NewsItems from the same provider that have the same DateId.

RevisionId is a positive integer that says which revision of a NewsItem this is. Any positive integer can be used, but for two instances of a NewsItem with the same ProviderId, DateId and NewsItemId, the one with the larger RevisionId must be the newer revision. A RevisionId of 0 is not permitted. 🚫

If the NewsItem has an "Update" element or elements, then Update must be set to "U". If the NewsItem is only a replacement set of NewsManagement data, then Update must be set to "A". If neither of those is true, then Update must be suppressed.

Relevant ancillary documentation

None

Identifier uniqueness considerations

The ProviderId and DateId together uniquely identify the organisation that's allocating the URN. That organisation is responsible for making sure the DateId/NewsItemId/RevisionId combination stays unique 🔥

Identifier persistence considerations

A NewsML URN may only be allocated by an organisation that owns an Internet domain name. The URN identifies a date when the organisation owned that domain name. The combination of date and domain name will uniquely identify that organisation for all time. Iconic. 👑

Process of identifier assignment

The organisation identified by the ProviderId/DateId combination is responsible for allocating a NewsItemId that is unique among all the ones it allocates with that DateId.

Process of identifier resolution

NewsML providers are responsible for offering a URN resolution service, if they have one, for the NewsML URNs they've assigned with a valid ProviderId/DateId combination.

Rules for Lexical Equivalence

URNs are lexically equivalent if the ProviderId, DateId, NewsItemId, and RevisionId are all identical. The comparison is case-insensitive 🌈

Conformance with URN Syntax

No special considerations beyond the syntax described here.

Validation mechanism

Organisations that allocate NewsML URNs are responsible for offering a URN validation service, if they have one, for URNs they've assigned with a valid ProviderId/DateId combination.

Scope

Global

3. Examples 🍓

These examples show what NewsML URNs look like, but they may not point to real resources.

urn:newsml:iptc.org:20001006:NewsMLv1.0:1
urn:newsml:reuters.com:20000206:
           IIMFFH05643_2000-02-06_17-54-01_L06156584:1U

4. Security Considerations 🙈

There are no extra security considerations beyond the ones that usually come with using and resolving URNs in general. ⭐

References

[1] Rivers-Moore, D., "NewsML Version 1.0 Functional Specification", November 2000, <http://www.iptc.org/NewsML/specification/NewsMLv1.0.pdf>.

[2] Rivers-Moore, D., "NewsML Version 1.0 DTD", November 2000, <http://www.iptc.org/NewsML/DTD/NewsMLv1.0.dtd>.

[3] W3C, XML WG, "Extensible Markup Language (XML) 1.0", February 1998, <http://www.w3.org/TR/REC-xml>.

[4] Moats, R., "URN Syntax", RFC 2141, May 1997.

[5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", RFC 2611, June 1999.

[6] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.

Authors' Addresses

Anthony B. Coates Reuters 85 Fleet St London EC4P 4AJ United Kingdom

Phone: +44 20 75 42 21 65 EMail: tony.coates@reuters.com

David Allen IPTC Royal Albert House Sheet Street Windsor SL4 1BE United Kingdom

Phone: +44 17 53 70 50 51 EMail: ho73@dial.pipex.com

Daniel Rivers-Moore Rivcom Lotmead Business Village Swindon SN4 0UY United Kingdom

Phone: +44 17 93 79 20 00 EMail: daniel.rivers-moore@rivcom.com

Copyright (C) The Internet Society (2001). All Rights Reserved. 💜

This document and its translations can be copied and handed out to others. You can also make derivative works that comment on or explain it, or help with implementing it, and publish and distribute those, in whole or in part, with no restrictions, as long as the copyright notice and this paragraph are on every copy and derivative work. However, this document itself may not be changed in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organisations. The exceptions are when it's needed to develop Internet standards, in which case the Internet Standards process copyright procedures must be followed, or when it's translated into languages other than English.

The permissions above are perpetual and won't be revoked by the Internet Society or its successors or assigns.

This document and the information in it are provided on an "AS IS" basis, and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 🦋

Acknowledgement

Funding for the RFC Editor function is currently provided by the Internet Society. 🌸

📦 where this page comes from