OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Re FPIs for RFCs

[ Lists Home | Date Index | Thread Index ]
  • From: "Rick Jelliffe" <ricko@allette.com.au>
  • To: <xml-dev@ic.ac.uk>
  • Date: Wed, 3 Dec 1997 15:58:06 +1100

> From: Murray Altheim <altheim@mehitabel.eng.Sun.COM>

> Maybe I'm confused by this point, but only the owner has the right to
> create FPIs within their namespace. 

Who gives this right?  What law or cases say that, if internic.net
makes a file publically available on an archive-server, I cannot
use its address inside a 9070 identifier?  Unlike that English newspaper
case, I am not passing off the thing pointed to as mine, I am
*not* passing it off.  ISO standards are not law.  FPIs are merely a
statement of fact, in a standard form. 

Statements of fact cannot be copyright, under US Law. So a telephone 
directory can be taken and reproduced without copyright infringement
(unless there is some non-mechanical uniqueness in the arrangement),
including company names that are also tradmarks.  This is because 
names and addresses are facts not inventions.  

Tell me why is legal to say:

	  image/gif is part of the Multipurpose Internet Mail Extensions
		given in ds.internic.net/rfc/rfc2046.txt

but somehow illegal to say:

	PUBLIC "+//IDN ds.internic.net/rfc/rfc2046.txt//NOTATION 
      	Multipurpose Internet Mail Extensions::image/gif//EN">

The use of Internet Domain Names in Formal Public Identifiers is part 
of WebSGML. The text is currently being finalized. I have asked for 

If it is clarified to say that only owners of public text can make
up FPIs, and that people cannot construct appropriate FPIs using
publicly available facts, then there are a lot of naughty FPIs out

That being said, I must agree with David that ISO 9070 seems clear
(but contradictory to ISO 8879) on it. I will ask WG4 for ISO 8879 
to be reconciled with ISO 9070.  Even though I certainly do not see 
how it can be unlawful, if it is wrongly formed against the rules of 
ISO 9070, that is a good enough reason not to do it.

Rick Jelliffe

ISO 8879
4.223 "The portion of a public identifier
that identies the owner or originator of public text". 

ISO 9070
"3.10 Owner name: the portion of a public identifier that names its owner.

.... 13 The owner of a public identifier is not necessarily the owner of
the object it identifies"

and from the introduction:
"... and an 'owner name', which identifies the originator of the public

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS