Two further points:
1) Last time I looked, new versions of PDF were planned to support 3D
geometry, and, in particular, they were planned to export STEP files (if you
buy a more expensive version of Acrobat Reader). That is, it is not pure
rendering for the human reader. (01)
2) A question in the Long Term Data Retention community is, can we define
"key characteristcs" (AS/EN 9100 serries term) for a document, and therefore
validation criteria to assure that the document displayed corresponds to the
one written. The validation procedure would evaluate the document displayed,
and compare it with tags written with the original file to see if the
recovered and resulting document were the same. This technology is already
implemented for 3D shapes, but I'm hoping that someone in the
commercial/legal world will sort out documents. (02)
On Feb 11, 2009 Pat Hays replied to - (03)
On Feb 11, 2009, at 9:45 AM, Alexander Garcia Castro wrote: (04)
> Sorry if this is not the right venue; I decided to send this email because
in the past I have seen some semantic web issues being discussed here. (05)
I think one of the W3C mailing lists might be more suitable for this topic.
Try semantic-web@xxxxxx (06)
>
>
> I would like to know how applicable could the PDF format be within the
context of the Semantic web? (07)
NOt very: the primary purpose of PDF is making visually accurate documents,
rather than semantic information. (08)
> The PDF format is closed; annotating PDFs, as in tagging not the file but
the information within the file, is not possible by means different from
those provided by ADOBE. For instance, if I wanted to tag a word, or an
image within, inside, a PDF I would have to do it with my acrobat
reader -the latest version; But if I wanted to facilitate such operation via
WEB I could only do it if and only if I had the XSLT so I could transform
the PDF into XML. (09)
Right. (010)
> This limitation is, IMHO, a huge one within the context of the semantic
web where we should be able to define links and use them. (011)
I don't quite see why you feel this is a SWeb problem. (012)
> Furthermore, being forced to have a third party application just for
displaying a file that should be displayed directly by the browser is not a
nice feature. (013)
That is an issue for browser implementations. (014)
> If PDF was open it could be rendered by the browser. Aren't closed
formats such as PDF viable within the context of the SW? (015)
Im not sure what exactly you are asking here. (016)
> After all the PDF was a solution within the context of portability and
exchange of information (017)
... for human readers, yes. But not for software inference agents, which is
the point of the SWeb. (018)
> ; the main problem it was solving was a simple one "I want my document to
look on display and once printed, the same everywhere" and "I want people
to be able to read my documents without loosing the format of the document
and without having to consider the OS". Isn't the PDF obsolete within this
context? (019)
What context? PDF seems to work well for its intended purpose. (?? Maybe I
havnt understood your point.) (020)
Seriously, I suggest re-sending your message to the semantic-web@xxxxxx
mailing list. (021)
Pat Hayes
>
> (022)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (023)
|