- From: <tony_hammond@harcourt.com>
- Date: Tue, 4 Sep 2001 17:15:47 +0100
- To: <dehora@acm.org>
- Cc: "RDF-IG" <www-rdf-interest@w3.org>
Bill: Sorr y for the delay in getting back to your request for info about literals. I posted an announcement to the RDF Interest list a couple of weeks ago (see below) about a new DOI service that uses RDF as the data model to support intelligent resolution of a public identifier (the DOI - Digital Object Identifier - currently being used by the STM publishing community) to multiple resources. In this model a core set of properties is defined to qualify (or specialize) the resources so that they can be meaningfully interpreted by client applications. Literals are used for these properties, which include: "access", "detail", "label", "resolve", "role", and "type". For more information see http://www2.harcourt-international.com/~tony/doi/yads/DObject.html or http://dx.doi.org/1014/yads [link from "Schematic Overview"] Also of interest may be the use of a "data:" URI scheme (RFC 2397) to support literals as resources in their own right, ie inline (or by-value) resources rather than the usual by-reference resources. Regards, Tony Art: Many thanks for this - very timely. I already included support for the RDF Validator into "yads" - Yet Another DOI Service. A DOI is a managed identifier of an intellectual property entity which enables the network retrieval of a set of related services. (For further information see < http://dx.doi.org/10.1000/1>.) "yads" shows how DOIs can be simply resolved to multiple resources and crucially how those resources are themselves interrelated. "yads" supports a number of visualizations of a DOI (menu popup, text dump, and RDF arcs and nodes diagram courtesy of the RDF Validator), as well as providing technical details of implementations. "yads" is available at http://dx.doi.org/1014/yads Tony Tony Hammond Head, Online Resource Activity Academic Press +44 (0)20 7424 4229 tony_hammond@harcourt.com "dehora" <dehora@eircom.net> To: "RDF-IG" <www-rdf-interest@w3.org> Sent by: cc: www-rdf-interest-requ Subject: what are you using literal property values for? est@w3.org 24/08/2001 22:05 Please respond to dehora -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm looking to scare up use cases folk have for RDF literals as property values or indeed if anyone out there is using literals in this way in applications or data models. Mainly I'm curious to know: - -what list members are using literals values for. - -what kind of literals you are using (strings, xml/infoset, binary...). - -how applications are interpreting these literals. - -if people are extending the parseType attribute. - -what problems you're running into with literal values. If you post to me directly, I'll summarize for the list. Thanks, Bill de hÓra -----BEGIN PGP SIGNATURE----- Version: PGP 7.0 iQA/AwUBO4bBROaWiFwg2CH4EQLqLQCg8mbolqgowq8+2Dq66wMffZ7u9EkAoI9e iYR6aiVJVoNWmXaGQBgA5yBM =8Y/V -----END PGP SIGNATURE-----
Received on Tuesday, 4 September 2001 11:17:02 UTC