[Nodal-j-devel] Harland--Placeless Documents
Status: Pre-Alpha
Brought to you by:
leei
From: Jack P. <jac...@th...> - 2002-06-24 19:35:30
|
fyi... http://www2.parc.com/csl/projects/harland/ Harland provides: "=B7 persistent document objects that can hold application data in a=20 dynamically-extensible set of named property values =B7 a query facility for retrieving these objects based on the values= =20 of their properties =B7 enforcement of application-supplied constraints =B7 automatic manipulation of a relational database for storage and=20 query processing without a fixed schema for the application data " Reference was found at http://nooface.com/ "Harland is a Java API developed by Xerox PARC that provides a persistent=20 attribute store for document-based applications written in Java. Harland=20 works in combination with a relational database by providing a layer on top= =20 of the relational model to simplify attribute storage and retrieval, while= =20 retaining the performance and aspects of data structuring that make RDBs so= =20 powerful. Document properties are statements about documents that make=20 sense to the user, and affect what they can do with the documents. Harland= =20 is the latest implementation of Placeless Documents, an architecture=20 developed by Xerox in which documents are organized and managed according=20 to their properties, rather than according to their location, as in=20 traditional hierarchical file systems (see online presentation). A 90-day=20 trial version of Harland can be downloaded. " Placeless Documents: http://www2.parc.com/csl/projects/placeless/ "Placeless Documents are documents that are organized and managed according= =20 to their properties, rather than according to their location. Document=20 properties can be things you already know about your documents, like that=20 they're published, or notes, or about the budget,or drafts, or source code,= =20 or important, or shared with your colleagues, or from your manager, or big,= =20 or from the Web, or... whatever suits you. Document properties can also be= =20 things that you want to be true about your documents, like that they are=20 backed up, or replicated on your laptop, or can be purchased for a small=20 fee. These latter properties carry the code to implement or interface with= =20 the desired functionality. Document properties are statements about your=20 documents that make sense to you, and affect what you're going to do with=20 the documents. " "Our vision is one of customizable, context-aware management of integrated= =20 information spaces, which: =B7 integrate information components from many sources: repositories= =20 (WWW, mail, file systems), devices (scanners, video-cameras, television,=20 phone), and dynamic processes (workflow, source code management systems,=20 search engines, and dynamic document content), =B7 allow customizable organization of the information based on=20 properties of that information, e.g., budget related, read at home, shared= =20 with John, and From: pet...@pa..., =B7 allow information properties to be arbitrary objects specified=20 through many different mechanisms: explicitly by the users themselves,=20 captured by physical context sensors, inferred from usage, automatically=20 generated by content analysis, etc. =B7 allow information properties to be active and carry behaviors to= =20 automate information work, enabling functionality like fax to John at 5pm=20 each day, translate to English, notarized, backed-up in Utah for safety,= etc. =B7 scale to sizes anywhere between an individual and the enterprise, =B7 are available at all locations required by the users, and =B7 protect the privacy and intellectual property of users. In this world the focus is on information, customization, and functionality= =20 that extends beyond the abilities of monolithic applications. Essentially,= =20 information carries the behaviors and semantics needed to operate on it.=20 Information is independent of location and becomes responsive to the=20 environments it is used in and the contexts of individual users, and it is= =20 managed independently by both its consumers and providers. " |