Authored by: cricketjeff on Thursday, June 20 2013 @ 07:14 AM EDT |
It is effectively a restatement of the whole point of hypertext.
I am pretty sure you'd find Tim Berners-Lee he's say this was invisaged in the
creation of the web!
---
There is nothing in life that doesn't look better after a good cup of tea.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Thursday, June 20 2013 @ 09:20 AM EDT |
Gitte about RFC1700 from October 1994? I'm
not sure when HTML became a registered
MIME type though. Since HTTP uses MIME
types I'm confident it was.
Also HTML was mentioned in 1991 which is
another prior art. HTTP is a messaging
protocol. The client (web browser) sent a
message to the server requesting a
particular document which then responded
with a message that contains said document
which could be HTML which in 1991 included
image and link tags.
Then there's Apple's "data tapping" patent
which discloses recognizing links and
structured text in unstructured text and
providing a choice of multiple actions. It
seems it's prior art would be prior art to
this patent as it discloses, I think, that
performing an automatic action or single
action as the need for its invention.
Are those early enough as Prior art?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Thursday, June 20 2013 @ 12:02 PM EDT |
I think the prior art could predate applications.
The people who design and write programs (i.e., those knowledgeable in the art)
are familiar with programming languages, such as C, which have include
statements that direct compilers to include text from a second source file.
The ability to access files over a network is as old as networks. The Internet
wasn't the first; for example, DECNET had that functionality.
Applying these principles to applications is fairly obvious. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Thursday, June 20 2013 @ 12:17 PM EDT |
Yes, the April 4, 1995 date is the issue here, as there was
some
use of HTML
in email message bodies prior to that
time but it certainly was not a
standard.
There were some rich text formats in use. Even RFC 1896 for
enriched text in
email, published in Feb 1996, doesn't
mention
HTML. It supercedes RFC 1523 (Sep
1993) which
covers
enriched text (MIME). Neither of these RFCs covers
hyperlinks within the rich
text.
They both refer to the
rich text standard embodied in RFC 1563 (Jan
1994) which
does
not include URLS (links) of any kind in its definition.
It does make mention
of
If one
could make a case that use of enriched text is the actual
prior art, and that HTML is one of many
enriched text formats, and one could
make a case of
"obviousness" so long as pre-1995 enriched text email prior
art
is found.
One possible route is to track the creation of the MIME
types
and HTML tags. For instance, the HTML IMG tag for
image URLs was proposed by
Marc
Andreessen in Feb 1993. The
MIME content type text/html was introduced in
1994 but I
don't have an explicit document to cite. It was introduced
officially in RFC 1866 by
the
HTML 2.0 working group in November 1995. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, June 21 2013 @ 02:54 PM EDT |
To help in the search for prior art here are a couple of RFCs dealing with
e-mail:
RFC 821 - Simple Mail Transfer Protocol
RFC 822 - STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
RFC 934 - Proposed standard for message encapsulation
RFC 1049 - Content-type header field for Internet messages
RFC 1341 - MIME (Multipurpose Internet Mail Extensions): Mechanisms for
Specifying and Describing the Format of Internet Message Bodies
RFC 1428 - Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
RFC 1437 - The Extension of MIME Content-Types to a New Medium
RFC 1590 - Media Type Registration Procedure
RFC 1521 - MIME (Multipurpose Internet Mail Extensions) Part One
RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One (this one is
divided into 5 parts so your may want to search through each part)
RFC 2822 - Internet Message Format
Hope this helps the search.
-Isnala[ Reply to This | Parent | # ]
|
|