Didier PH Martin
martind at netfolder.com
Tue May 25 20:03:19 BST 1999
> Yes; but on the other hand, if product vendor X announces some new
> product and describe their new protocil or format (totally proprietary
> and undocuments) as "the new standard" and it, for exanmple, it covers
> the same ground as an existing W3C Recommendation, then we do the world
> no favours if a magazine editor rings us to do a sidebar on the WE3C
> spec and we don't promote it, in that forum, as being "more standard"
> than product X.
And what if W3C compete against other "standard" institutions? And what if
this product is documented and the copyright notice explitely express that
we can use this spec (We should not forget that all W3C material is
copyrighted also).Below are extracts from the W3C copyright notice and an
other one from biztalk.org (because this is this thread's origin after all).
So, what if someone publish a document with a copyright statement like in
the biztalk documents? What if a big bunch of people use and elaborate on
this spec? Is it then a "standard"? a de facto "standard"? "an open
specification" we can freely implement? maybe is the latter who knows ? ;-)
W3C copyright extract:
Permission to use, copy, and distribute the contents of this document, or
the W3C document from which this statement is linked, in any medium for any
purpose and without fee or royalty is hereby granted, provided that you
include the following on ALL copies of the document, or portions thereof,
that you use:
A link or URL to the original W3C document.
The pre-existing copyright notice of the original author, if it doesn't
exist, a notice of the form: "Copyright © World Wide Web Consortium,
(Massachusetts Institute of Technology, Institut National de Recherche en
Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but a textual
representation is permitted.)
If it exists, the STATUS of the W3C document.
When space permits, inclusion of the full text of this NOTICE should be
provided. We request that authorship attribution be provided in any
software, documents, or other items or products that you create pursuant to
the implementation of the contents of this document, or any portion thereof.
No right to create modifications or derivatives of W3C documents is granted
pursuant to this license. However, subsequent to additional requirements
documented in the Copyright FAQ, modifications or derivatives are sometimes
granted by the W3C to individuals complying with those terms.
Biztalk copyright extract:
Microsoft hereby grants to all users of this BizTalk (tm) Framework
specification, version 0.8 (the "Specification"), a perpetual, nonexclusive,
royalty-free, world-wide right and license under any Microsoft copyrights in
the Specification to copy, publish and distribute the Specification.
Microsoft further agrees to grant to users a royalty-free license under
applicable Microsoft intellectual property rights to implement and use the
BizTalk XML tags and schema guidelines included in the Specification for the
purpose of creating computer programs that adhere to such guidelines --one
condition of this license shall be the party's agreement not to assert
patent rights against Microsoft and other companies for their implementation
of the Specification. Microsoft expressly reserves all other rights it may
have in the material and subject matter of this Specification. Microsoft
expressly disclaims any and all warranties regarding this Specification
including any warranty that this Specification or implementations thereof
does not violate the rights of others
Didier PH Martin
mailto:martind at netfolder.com
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev