Near p.v some examples....
www.vtour.ch/sa/na37a38.html
www.ipanema.com/citytour/home.htm
or this would be relevant on p5
www.cbs.com/primetime/bigbrother3/
How about this for "the limits of digital experience" p8?
www.hitl.washington.edu/research/magnet/
Webpage text copyrighted by Hunter Hoffman, U.W. HITLab, and Affiliate Faculty at U.W. Radiology and Psychology.
The U.W Radiology Digital Imaging Science Centers’ wide field of view magnet-friendly virtual reality image delivery system makes it possible for volunteers and patients to have the illusion of going into virtual reality during fMRI brain scans.
video codecs: comparison -- www.ebu.ch/trev_301-samviq.pdf
Vergelijkend onderzoek naar video codecs
De EBU (European Broadcast Union) publiceerde eind januari een onderzoek
naar verschillende video codecs. Envivio MPEG-4, QuickTime 6, RealNetworks
9 en Windows Media 9 worden onder de loep genomen. Het rapport is te
downloaden via:
www.ebu.ch/trev_home.html
<navigate/>
Now, how would you approach defining a unifying data model
for the web?
One project in this area that might be worthwhile to look at
is the OntoWeb project, accessible through
www.ontoweb.org
that aims at producing the technology for ontology-based
information exchange for both knowledge management
and electronic commerce.
Such technology allows for adding descriptive information
and, equally important, to reason with such information.
Moreover, it allows for dealing with information formulated
in disparate terminologies by using so-called ontologies,
which may be regarded as formalized perspectives or world views.
www.w3.org/2000/01/sw/
Semantic Web Activity: Advanced Development
"Now, miraculously, we have the Web. For the documents in our lives,
everything is simple and smooth. But for data, we are still pre-Web." -- Tim Berners-Lee, Business Model for the Semantic Web
www.w3.org/DesignIssues/Business
"The bane of my existence is doing things that I know the computer could do for me." -- Dan Connolly, The XML Revolution
www.nature.com/nature/webmatters/xml/xml.html
Resource Description Framework (RDF)
The Resource Description Framework (RDF) integrates a variety of applications from library
catalogs and world-wide directories to syndication and aggregation of news,
software, and content to personal collections of music, photos,
and events using XML as an interchange syntax.
The RDF specifications provide a lightweight ontology system to support the
exchange of knowledge on the Web.
In [CWI], we read:
multimedia
While text-based content on the Web is already rapidly approaching the third generation, multimedia content is still trying to catch up with second generation techniques.
<navigate/>
The reason for this is that processing multimedia
is fundamentally different from processing text.
As phrased in [CWI]:
processing requirements
Multimedia document processing has a number of fundamentally different requirements from text which make it more difficult to incorporate within the document processing chain.
<navigate/>
More specifically it is said that:
presentation abstractions
In particular, multimedia transformation uses different document and presentation abstractions, its formatting rules cannot be based on text-flow, it requires feedback from the formatting back-end and is hard to describe in the functional style of current style languages.
<navigate/>
Now this may well be true for specific categories
of multimedia on the web.
So, for example, rendering presentations
written in SMIL is probably not an easy thing to do.
But does this really prevent us from incorporating multimedia in the
semantic web, or rather create a multimedia semantic web?
from primer
Using URIrefs as subjects, predicates, and objects in RDF statements supports the development
and use of shared vocabularies on the Web,
since people can discover and begin using vocabularies already used by others to describe things,
reflecting a shared understanding of those concepts. For example, in the triple
ex:index.html dc:creator exstaff:85740 .
the predicate dc:creator, when fully expanded as a URIref,
is an unambiguous reference to the "creator" attribute in the Dublin Core
metadata attribute set (discussed further in Section 6.1), a widely-used set of
attributes (properties) for describing information of all kinds.
The writer of this triple is effectively saying that the relationship between the
Web page (identified by http://www.example.org/index.html ) and the creator
of the page (a distinct person, identified by http://www.example.org/staffid/85740 )
is exactly the concept identified by http://purl.org/dc/elements/1.1/creator.
Another person familiar with the Dublin Core vocabulary,
or who finds out what dc:creator means (say by looking up its definition on the Web)
will know what is meant by this relationship.
In addition, based on this understanding, people can write programs to behave in
accordance with that meaning when processing triples containing the predicate dc:creator.
Metadata is data about data.
Specifically, the term refers to data used to identify, describe, or locate information resources,
whether these resources are physical or electronic. While structured metadata processed by computers
is relatively new, the basic concept of metadata has been used for many years in helping manage
and use large collections of information. Library card catalogs are a familiar example of such
metadata.
The Dublin Core is a set of "elements" (properties) for describing documents (and hence,
for recording metadata).
The element set was originally developed at the March 1995 Metadata Workshop in Dublin, Ohio.
The Dublin Core has subsequently been modified on the basis of later Dublin Core Metadata workshops,
and is currently maintained by the Dublin Core Metadata Initiative.
The goal of the Dublin Core is to provide a minimal set of descriptive elements that
facilitate the description and the automated indexing of document-like networked objects,
in a manner similar to a library card catalog.
The Dublin Core metadata set is intended to be suitable
for use by resource discovery tools on the Internet,
such as the "Webcrawlers" employed by popular World Wide Web search engines.
In addition, the Dublin Core is meant to be sufficiently simple to be understood
and used by the wide range of authors and casual
publishers who contribute information to the Internet.
Dublin Core elements have become widely used in documenting Internet resources
(the Dublin Core creator element has already been used in earlier examples).
The current elements of the Dublin Core are defined in the Dublin Core Metadata Element Set,
Version 1.1: Reference Description [DC], and contain definitions for the following properties:
Title: A name given to the resource.
Creator: An entity primarily responsible for making the content of the resource.
Subject: The topic of the content of the resource.
Description: An account of the content of the resource.
Publisher: An entity responsible for making the resource available
Contributor: An entity responsible for making contributions to the content of the resource.
Date: A date associated with an event in the life cycle of the resource.
Type: The nature or genre of the content of the resource.
Format: The physical or digital manifestation of the resource.
Identifier: An unambiguous reference to the resource within a given context.
Source: A reference to a resource from which the present resource is derived.
Language: A language of the intellectual content of the resource.
Relation: A reference to a related resource.
Coverage: The extent or scope of the content of the resource.
Rights: Information about rights held in and over the resource.
Information using the Dublin Core elements may be represented in any suitable language (e.g., in HTML meta elements). However, RDF is an ideal representation for Dublin Core information. The examples below represent the simple description of a set of resources in RDF using the Dublin Core vocabulary. Note that the specific Dublin Core RDF vocabulary shown here is not intended to be authoritative. The Dublin Core Reference Description [DC] is the authoritative reference.
http://www.w3.org/TR/rdf-primer/#dublincore
An Introduction to the Resource Description Framework
Eric J. Miller
The Resource Description Framework (RDF) is an
infrastructure that enables the encoding, exchange and reuse of
structured metadata. rdf is an application of xml that imposes needed
structural constraints to provide unambiguous methods of expressing
semantics. rdf additionally provides a means for publishing both
human-readable and machine-processable vocabularies designed to
encourage the reuse and extension of metadata semantics among
disparate information communities. the structural constraints rdf
imposes to support the consistent encoding and exchange of
standardized metadata provides for the interchangeability of separate
packages of metadata defined by different resource description
communities.
Corporation for National Research Initiatives
machine-readable catalog record formats
applications of computer file organization and
access methods
Copyright © 1998 Eric Miller
Electronic Document
text/html
en
http://www.w3.org/XML/
Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879).
Originally designed to meet the challenges of large-scale electronic publishing,
XML is also playing an increasingly important role in the exchange of a wide variety of
data on the Web and elsewhere.
http://dublincore.org/tools/
The Dublin Core Metadata Initiative is an open forum engaged in the development of
interoperable online metadata standards that support a broad range of purposes and business models.
http://dublincore.org/documents/dces/
The Elements
Element Name: Title
Label: Title
Definition: A name given to the resource.
Comment: Typically, Title will be a name by which the resource is formally known.
Element Name: Creator
Label: Creator
Definition: An entity primarily responsible for making the content of the resource.
Comment: Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
Element Name: Subject
Label: Subject and Keywords
Definition: A topic of the content of the resource.
Comment: Typically, Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
Element Name: Description
Label: Description
Definition: An account of the content of the resource.
Comment: Examples of Description include, but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.
Element Name: Publisher
Label: Publisher
Definition: An entity responsible for making the resource available
Comment: Examples of Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Element Name: Contributor
Label: Contributor
Definition: An entity responsible for making contributions to the content of the resource.
Comment: Examples of Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
Element Name: Date
Label: Date
Definition: A date of an event in the lifecycle of the resource.
Comment: Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and includes (among others) dates of the form YYYY-MM-DD.
Element Name: Type
Label: Resource Type
Definition: The nature or genre of the content of the resource.
Comment: Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary [DCT1]). To describe the physical or digital manifestation of the resource, use the FORMAT element.
Element Name: Format
Label: Format
Definition: The physical or digital manifestation of the resource.
Comment: Typically, Format may include the media-type or dimensions of the resource. Format may be used to identify the software, hardware, or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats).
Element Name: Identifier
Label: Resource Identifier
Definition: An unambiguous reference to the resource within a given context.
Comment: Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Formal identification systems include but are not limited to the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).
Element Name: Source
Label: Source
Definition: A Reference to a resource from which the present resource is derived.
Comment: The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.
Element Name: Language
Label: Language
Definition: A language of the intellectual content of the resource.
Comment: Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), defines two- and three primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian", and "en-GB" for English used in the United Kingdom.
Element Name: Relation
Label: Relation
Definition: A reference to a related resource.
Comment: Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.
Element Name: Coverage
Label: Coverage
Definition: The extent or scope of the content of the resource.
Comment: Typically, Coverage will include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.
Element Name: Rights
Label: Rights Management
Definition: Information about rights held in and over the resource.
Comment: Typically, Rights will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions may be made about any rights held in or over the resource.
dublin core -- http://uk.dublincore.org/documents/1999/07/02/dces/
Dublin Core Metadata Element Set, Version 1.1: Reference Description
Title: Dublin Core Metadata Element Set, Version 1.1: Reference Description
Date Issued: 1999-07-02
Identifier: http://dublincore.org/documents/1999/07/02/dces/
Supersedes: http://dublincore.org/documents/1998/09/dces/
Is Superseded By: http://dublincore.org/documents/2003/02/04/dces/
Latest version: http://dublincore.org/documents/dces/
Translations: http://dublincore.org/resources/translations/
Status of document: This is a DCMI Recommendation.
Description of document: This document is the reference description, version 1.1 of the Dublin Core Metadata Element Set. This document supersedes the Dublin Core Metadata Element Set, version 1.0. See the Dublin Core Home Page (http://dublincore.org) for further information about the workshops, reports, working group papers, projects, and new developments concerning the Dublin Core Metadata Element set.
Each Dublin Core element is defined using a set of ten attributes from the ISO/IEC 11179 [ISO11179] standard for the description of data elements. These include:
Name - The label assigned to the data element
Identifier - The unique identifier assigned to the data element
Version - The version of the data element
Registration Authority - The entity authorised to register the data element
Language - The language in which the data element is specified
Definition - A statement that clearly represents the concept and essential nature of the data element
Obligation - Indicates if the data element is required to always or sometimes be present (contain a value)
Datatype - Indicates the type of data that can be represented in the value of the data element
Maximum Occurrence - Indicates any limit to the repeatability of the data element
Comment - A remark concerning the application of the data element
Fortunately, six of the above ten attributes are common to all the Dublin Core elements. These are, with their respective values:
Version: 1.1
Registration Authority: Dublin Core Metadata Initiative
Language: en
Obligation: Optional
Datatype: Character String
Maximum Occurrence: Unlimited
The definitions provided here include both the conceptual and representational form of the Dublin Core elements. The Definition attribute captures the semantic concept and the Datatype and Comment attributes capture the data representation.
Each Dublin Core definition refers to the resource being described. A resource is defined in [RFC2396] as "anything that has identity". For the purposes of Dublin Core metadata, a resource will typically be an information or service resource, but may be applied more broadly.
Element: Title
Name: Title
Identifier: Title
Definition: A name given to the resource.
Comment: Typically, a Title will be a name by which the resource is
formally known.
Element: Creator
Name: Creator
Identifier: Creator
Definition: An entity primarily responsible for making the content of
the resource.
Comment: Examples of a Creator include a person, an organisation,
or a service.
Typically, the name of a Creator should be used to
indicate the entity.
Element: Subject
Name: Subject and Keywords
Identifier: Subject
Definition: The topic of the content of the resource.
Comment: Typically, a Subject will be expressed as keywords,
key phrases or classification codes that describe a topic
of the resource.
Recommended best practice is to select a value from a
controlled vocabulary or formal classification scheme.
Element: Description
Name: Description
Identifier: Description
Definition: An account of the content of the resource.
Comment: Description may include but is not limited to: an abstract,
table of contents, reference to a graphical representation
of content or a free-text account of the content.
Element: Publisher
Name: Publisher
Identifier: Publisher
Definition: An entity responsible for making the resource available
Comment: Examples of a Publisher include a person, an organisation,
or a service.
Typically, the name of a Publisher should be used to
indicate the entity.
Element: Contributor
Name: Contributor
Identifier: Contributor
Definition: An entity responsible for making contributions to the
content of the resource.
Comment: Examples of a Contributor include a person, an organisation,
or a service.
Typically, the name of a Contributor should be used to
indicate the entity.
Element: Date
Name: Date
Identifier: Date
Definition: A date associated with an event in the life cycle of the
resource.
Comment: Typically, Date will be associated with the creation or
availability of the resource. Recommended best practice
for encoding the date value is defined in a profile of
ISO 8601 [W3CDTF] and follows the YYYY-MM-DD format.
Element: Type
Name: Resource Type
Identifier: Type
Definition: The nature or genre of the content of the resource.
Comment: Type includes terms describing general categories, functions,
genres, or aggregation levels for content. Recommended best
practice is to select a value from a controlled vocabulary
(for example, the working draft list of Dublin Core Types
[DCT1]). To describe the physical or digital manifestation
of the resource, use the FORMAT element.
Element: Format
Name: Format
Identifier: Format
Definition: The physical or digital manifestation of the resource.
Comment: Typically, Format may include the media-type or dimensions of
the resource. Format may be used to determine the software,
hardware or other equipment needed to display or operate the
resource. Examples of dimensions include size and duration.
Recommended best practice is to select a value from a
controlled vocabulary (for example, the list of Internet Media
Types [MIME] defining computer media formats).
Element: Identifier
Name: Resource Identifier
Identifier: Identifier
Definition: An unambiguous reference to the resource within a given context.
Comment: Recommended best practice is to identify the resource by means
of a string or number conforming to a formal identification
system.
Example formal identification systems include the Uniform
Resource Identifier (URI) (including the Uniform Resource
Locator (URL)), the Digital Object Identifier (DOI) and the
International Standard Book Number (ISBN).
Element: Source
Name: Source
Identifier: Source
Definition: A Reference to a resource from which the present resource
is derived.
Comment: The present resource may be derived from the Source resource
in whole or in part. Recommended best practice is to reference
the resource by means of a string or number conforming to a
formal identification system.
Element: Language
Name: Language
Identifier: Language
Definition: A language of the intellectual content of the resource.
Comment: Recommended best practice for the values of the Language
element is defined by RFC 1766 [RFC1766] which includes
a two-letter Language Code (taken from the ISO 639
standard [ISO639]), followed optionally, by a two-letter
Country Code (taken from the ISO 3166 standard [ISO3166]).
For example, 'en' for English, 'fr' for French, or
'en-uk' for English used in the United Kingdom.
Element: Relation
Name: Relation
Identifier: Relation
Definition: A reference to a related resource.
Comment: Recommended best practice is to reference the resource by means
of a string or number conforming to a formal identification
system.
Element: Coverage
Name: Coverage
Identifier: Coverage
Definition: The extent or scope of the content of the resource.
Comment: Coverage will typically include spatial location (a place name
or geographic coordinates), temporal period (a period label,
date, or date range) or jurisdiction (such as a named
administrative entity).
Recommended best practice is to select a value from a
controlled vocabulary (for example, the Thesaurus of Geographic
Names [TGN]) and that, where appropriate, named places or time
periods be used in preference to numeric identifiers such as
sets of coordinates or date ranges.
Element: Rights
Name: Rights Management
Identifier: Rights
Definition: Information about rights held in and over the resource.
Comment: Typically, a Rights element will contain a rights
management statement for the resource, or reference
a service providing such information. Rights information
often encompasses Intellectual Property Rights (IPR),
Copyright, and various Property Rights.
If the Rights element is absent, no assumptions can be made
about the status of these and other rights with respect to
the resource.
<recordList>
<record creation="1070031329" modification="1107262576">
<priref>1001000025</priref>
<input.time>10:22:05</input.time>
<edit.time>13:55:55</edit.time>
<related>1001000019</related>
<edit.name>Tatja.Scholte</edit.name>
<input.name>bb-05</input.name>
<edit.date>2005-02-01</edit.date>
<input.date>2002-10-09</input.date>
<contributor.domain>organisation</contributor.domain>
<publisher.domain>organisation</publisher.domain>
<creator.domain>organisation</creator.domain>
<title>Conservation record for Antony Gormley's 'Untitled (For Francis)', 1985</title>
<subject>Gormley, Antony</subject>
<subject>mixed media</subject>
<subject_type>artist</subject_type>
<subject_type>artist_material</subject_type>
<publisher.role>museum</publisher.role>
<rights>TATE, Conservation Department. Please contact Publisher</rights>
<relation>http://www.tate.org.uk/search/default.jsp</relation>
<contributor.role>museum</contributor.role>
<creator.role>conservation department</creator.role>
<publisher>TATE, Conservation Department</publisher>
<language>English</language>
<identifier>Tate</identifier>
<identifier>T05004</identifier>
<form.type>Report</form.type>
<format>Word</format>
<format>Print</format>
<format>Photograph (black-and-white)</format>
<description>The Tate's conservation record for Antony Gormley's 'Untitled (For Francis)', 1985,
includes a record of examination, a structure and condition report,
handling and installation notes, a record of treatment,
information concerning display and installation, as well as photographs of the work.
</description>
<date>2002-10-08</date>
<coverage>UK</coverage>
<content.type>Artist's technique</content.type>
<content.type>Conservation</content.type>
<content.type>Display/Installation</content.type>
<content.type>Artist's material</content.type>
<contributor>TATE, Conservation Department</contributor>
<creator>TATE, Conservation Department</creator>
</record>
</recordList>
PROTO Video [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name for use in the presentation environment.
field MFString description []
field SFString urlPreviewImage "" # small representational image
# Small representational image of the data (video file)
# For preview (for example in the Concept Graph)
# For example a frame of the movie
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
field SFString url "" # Location of the data (video file)
field SFInt32 width 0 # Width of the video in pixels
field SFInt32 height 0 # Height of the video in pixels
]{}
PROTO VideoInterview [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the video for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlPreviewImage ""
# Small representational image of the data (video file)
# For preview (for example in the Concept Graph)
# For example a frame of the movie
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
field SFString url "" # Location of the data (video file)
field SFInt32 width 0 # Width of the video in pixels
field SFInt32 height 0 # Height of the video in pixels
]{}
PROTO Picture [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the picture for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlPreviewImage ""
# Small representational image of the data (picture)
# For preview (for example in the Concept Graph)
# For example a small version of the picture
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
field SFString url "" # Location of the data (picture file)
field SFInt32 width 0 # Width of the picture in pixels
field SFInt32 height 0 # Height of the picture in pixels
]{}
PROTO TextItem [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the textitem for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString url "" # Location of the data (text file)
# Format not know yet
]{}
PROTO GroupNode [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the groupnode for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlModel "" # Location of VRML model that represents the groupnode,
# for use in the Concept Graph.
]{}
PROTO Artwork [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the Artwork for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlPreviewImage ""
# Small representational image of the artwork
# For preview (for example in the Concept Graph)
# For example a small version of the picture
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
]{}
PROTO InterviewItem [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the Interview for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlPreviewImage ""
# Small representational image for the interview
# For preview (for example in the Concept Graph)
# For example a small version of the picture
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
]{}
PROTO MaterialItem [
field SFString shortName "" # Name in Concept Graph max. about 15 characters
field SFString ID "" # Unique identifier for internal use
field MFString connectedNodesIDs [] # List of IDs of nodes connected to this node
field SFString longName "" # Long name: for example to use in the preview in the Concept Graph
# and in the presentation environment.
field MFString description []
# Short description of the Material-item for preview in the Concept Graph
# each line of text must be in a different string
# Length of a line of text is still to be determined:
# This depends on the available space, in the meantime:
# type all text in one line.
field SFString urlPreviewImage ""
# Small representational image for the material
# For preview (for example in the Concept Graph)
# For example a small version of the picture
field SFInt32 widthPreviewImage 0
# Width of the representational image in pixels
field SFInt32 heightPreviewImage 0
# Height of the representational image in pixels
]{}
PROTO Information [
exposedField MFNode informationNodes []
eventOut SFBool isReady
]{
Script {
eventOut SFBool isReady IS isReady
url "javascript:
function initialize() {
isReady = true;
}
"
}
}
Information {
informationNodes [
GroupNode {
ID "MAIN"
shortName "Main"
longName "Main"
urlModel "models/conceptGraph/main/modelMain.wrl"
description ["Central information node"]
connectedNodesIDs ["ARTWORKS", "KEYWORDS", "INTERVIEWS", "REPORT"]
}
GroupNode {
shortName "Artworks"
longName "Artworks"
description ["Node that connects to all the artworks"]
ID "ARTWORKS"
connectedNodesIDs ["MAIN", "TRANSITORY", "ULAY", "VIDEOINSTALLATION", "ABRAMOVIC"]
urlModel "models/conceptGraph/artworks/artworksGroup.wrl"
}
## ...
Artwork {
shortName "Terra degla Dea Madre"
longName "Terra degla Dea Madre"
description ["15:40 min, colour, sound."]
ID "AV24"
connectedNodesIDs ["VIDEOINSTALLATION", "DTV24", "TTV24", "PV24", "CV24", "VV24", "G0"]
urlPreviewImage "images/previewImages/AV24.jpg"
widthPreviewImage 479
heightPreviewImage 349
}
Video {
ID "CV24"
shortName "Interview clip Terra degla Dea Madre"
longName "Interview clip showing Terra degla Dea Madre"
url "interviewclips/interview_terra_degla.avi"
width 320
height 360
urlPreviewImage "images/previewImages/interview_terra_degla.jpg"
widthPreviewImage 320
heightPreviewImage 240
description [""]
connectedNodesIDs ["CLIP", "AV24"]
}
Video {
shortName "Video Terra degla dea madre"
longName "Video Terra degla dea madre"
description [""]
ID "VV24"
connectedNodesIDs ["AV24", "AV21_1"]
url "videos/Terra degla dea madre.avi"
width 320
height 240
urlPreviewImage "images/previewImages/AV24.jpg"
widthPreviewImage 479
heightPreviewImage 349
}
TextItem {
shortName "Instruction"
longName "Green Dragon Lying instructions for the public."
description ["Text explaining the way the public has to interact with the artwork."]
ID "ITO05"
connectedNodesIDs ["AO05", "INTERACTION"]
url "text/AO05_instruction.txt"
}
]
}
(C) Æliens
20/08/2009
You may not copy or print any of this material without explicit permission of the author or the publisher.
In case of other copyright issues, contact the author.