#1175 Code vs text - second attempt at resolution

Why? For what purpose? To make the IETF's definitions more
out of alignment
with the rest of the IPR world??? - As to Code - all that
matters is the
patent protection capabilities - and to not destroy
people's patent
capabilities by participating with the IETF - unless that is
the goal here.

That said - then the real diagramming - whether specific to
CODE or DRAWINGS
should conform to US and Euro Patent
Documentation/Diagramming Standards,
the IETF's publishing rights are orthogonal & of little
impact to all other
concerns.

The reasoning is that if someone cannot protect the
uniqueness of their
invention without destroying those rights within the IETF,
then there is no
reason to deal with the IETF and in fact the IETF becomes a
threat to many
corporate entities IMHO.



Todd Glassey

----- Original Message ----- 
From: "David B Harrington" <dbharringtoncomcast.net>
To: "'Harald Alvestrand'" <haraldalvestrand.no>; <ipr-wgietf.org>
Sent: Monday, June 05, 2006 5:45 AM
Subject: RE: #1175 Code vs text - second attempt at
resolution


> Hi,
>
> I suggest that a contributor that wishes to ensure that
their
> "pseudocode" can be copied with the same
constraints as code would be
> could explicitly mark the section with
<code></code> markers.
> Pseudocode that is not explicitly surrounded by
<code> markers could
> be declared (by IPR-WG document) to be non-code for
purposes of
> copyright.
>
> David Harrington
> dharringtonhuawei.com
> dbharringtoncomcast.net
> ietfdbhcomcast.net
>
>
> > -----Original Message-----
> > From: Harald Alvestrand [mailto:haraldalvestrand.no]
> > Sent: Saturday, June 03, 2006 6:44 PM
> > To: ipr-wgietf.org
> > Subject: #1175 Code vs text - second attempt at
resolution
> >
> > In our list of open issues, we have this issue:
> >
> > > If there are different rights granted to
participants for
> > working with
> > > code than with non-code, it
> > > has to be possible for users to tell which is
which.
> > Suggestions include:
> > > - Defining it by type (C code, ABNF, MIBs...)
> > > - Defining it by marker
(<code>/</code>)
> > > - Defining it by separate submission (file
alongside draft)
> > > If there are no such differences, the point
is moot.
> >
> > The discussion from my previous attempt at a
resolution had 4
> > participants, which is a bit too few for comfort.
Mainly, it seems
> to
> > have indicated that the resolution should say less
- and clearly
> > illustrates that defining "pseudocode"
is even harder than
> > defining "code".
> >
> > Second attempt:
> >
------------------------------------------------------------
--------
> > If a distinction needs to be drawn between code
and non-code in IETF
> > documents, the community desires that:
> >
> > - Specifications in formal languages, including C
code, ABNF, MIBs,
> > ASN.1 and so on, are clearly "code".
> > - Tables such as the character lists in IDNA are
to be regarded as
> > "code" too.
> > - Prose, including "pseudocode" that
does not claim any level of
> > formality, is not "code" for the
purposes of this resolution. This
> > resolution does not say anything about the IETF's
desires regarding
> > "pseudocode", one way or another.
> > - The IETF Trust should maintain specific guidance
on what will be
> > regarded as "code", including guidance
on how to mark "code" in
> > documents where doubt could exist; this guidance
is expected to
> change
> > more often than the IETF IPR rules (as enshrined
in BCPs), if
> needed.
> >
------------------------------------------------------------
-------
> > I think this communicates a desire of the
community that it will be
> > clear how to apply for the 95% case, which should
be good
> > enough to put
> > text into our draft.
> >
> > Comments?
> >
> >                          Harald
> >
> >
> >
> >
> > _______________________________________________
> > Ipr-wg mailing list
> > Ipr-wgietf.org
> > https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
> >
> >
> > _______________________________________________
> > Ipr-wg mailing list
> > Ipr-wgietf.org
> > https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
> >
>
>
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wgietf.org
> https:/
/www1.ietf.org/mailman/listinfo/ipr-wg


_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg