Soatopicindex - QVIZ

SOATopicIndex - QVIZ

SOATopicIndex

From QVIZ

Jump to: navigation, search

State Of The Art Topic Index (SOTA)

Partners should add topics that are relevant also to their work and to also provide other partners with insights or understanding of project technology, standards etc.

● Cross Reference of SOTA documents (Word, powerpoint, etc) SOTA Attachment Cross Reference

Contents

● 1 General resources

● 2 Archive and content organization

● 3 Technologies relevant to QVIZ

● 4 Knowledge related (Ontology, thesauri,etc) or standards

[edit] General resources

1. Relvant State-of-the-Art Reports 2. Support and Networking 1. Mailing Lists 3. Relevant projects 1. Electronic library project 2. Relevant Projects 4. Issue and Bug Tracking Software

Archive and content organization [edit]

1. Archive overview provenance principle 2. Inner organization of Fonds 3. Record Keeping Concept 4. Partner archive systems ( more)

http://qviz.humlab.umu.se/index.php/SOATopicIndex (1 of 5)2006-09-29 08:49:10 SOATopicIndex - QVIZ 1. NAE System Description 2. SVAR and National Archives System Description 3. Vision of Britain System Description 4. Comparison of admin unit issues across partners systems 5. Archive features - QVIZ 1. Trackback 6. Archive Standards

Technologies relevant to QVIZ [edit]

1. Image annotation to support user generated Thematic maps 2. Web Tools: Screen Capture 3. Prominent digital repositories Technologies and Digital Archive Technologies 1. See also Digital Object Metadata 4. Semantic repositories and other basis repository techologies (also semantic digital or semantic e-Libraries, etc) 5. Semantic web services (SWS) and Service oriented architecture (SOA) 6. Access Stategies 7. Workflow Technologies (includes BEPL,etc related tools) 8. Relevant social software (mainly to point out relevant features) 1. Semantic web tools 2. Wiki or combined social software tools 3. Blogging tools 4. Applications for Semantic Communities 5. browser plug-ins (social bookmarking, blogging, annotation) 6. Semantic wikis - summary of relevant features 7. Other Groupware 9. Alogorithms to address scalability, site annotation,etc issues 10. Distributed user profiles management User profiling, services, standards (how to share and use by different services or apps... even institution might access) 11. Authentication (SingleSignOn, across services, multiple applications or server, institutions systems) 12. Persistent Object Identifier Technologies(DOI, \OpenUrl,etc) 13. Digital Object Metadata 14. Technologies for Rich Internet Applications in QVIZ 1. Technologies for Rich Internet Applications (client-side AJAX, Flash ,etc) 2. Technologies for Collaboration and Presentation in Rich Internet Applications 3. AJAX and FLASH Together 15. Visualisation and Knowledge 16. Relevant WebGIS technologies

http://qviz.humlab.umu.se/index.php/SOATopicIndex (2 of 5)2006-09-29 08:49:10 SOATopicIndex - QVIZ 1. General functionalities 2. Visualization 3. Service standards 4. Client technologies 5. Server-side technologies 6. Applications 17. Agent Frameworks

Knowledge related (Ontology, thesauri,etc) or standards [edit]

1. Collection Description Overview and Importance (DCMI Collections, Michael, ISAD(G), RLSP) 1. Collection Descriptions: proprietary descriptions of Partners 2. Communities 1. Communities Of Practice, Interest, etc 2. Organisation - how might roles be organised by the community? 3. Community and collaboration related standards 3. Administrative Ontology, gazetters and relevant GIS]] 1. Gazetteers 2. Gazetteer Content Standards 3. Gazetteer Feature Types 4. Administrative Unit typologies in VoB and Qviz 5. Service standards 6. Timeless access to time-spatial admin unit information 7. Relevant ADL 4. Other Archive related (digial library, CH including for libraries, museums) 1. Overview 2. EAD 3. Marcont 5. Digital Objects and Digital Library 1. Digital Objects and Library Standards 6. Other Domain knowledge 1. Relevant Ontologies and Thesauri 7. Rights and business process related (address object rights and roles) 8. Standards to support annotation 1. Standards to support annotation 2. Standards to support image annotation 3. Bookmarking, Social Bookmarking 4. XPointer and applications 9. Ontology or semantic systems related 10. Miscellaneous

http://qviz.humlab.umu.se/index.php/SOATopicIndex (3 of 5)2006-09-29 08:49:10 SOATopicIndex - QVIZ Retrieved from "http://qviz.humlab.umu.se/index.php/SOATopicIndex"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/SOATopicIndex (4 of 5)2006-09-29 08:49:10 SOATopicIndex - QVIZ

● This page was last modified 15:26, 27 September 2006. ● This page has been accessed 215 times.

http://qviz.humlab.umu.se/index.php/SOATopicIndex (5 of 5)2006-09-29 08:49:10 SOTA Attachment Cross Reference - QVIZ

SOTA Attachment Cross Reference

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 SOTA Attachment Reference Index

● 3 Partner

● 4 Topic /descriptor

[edit] Summary

SOTA Attachment Reference Index (docs, powerpoints,etc), but not images.

SOTA Attachment Reference Index [edit]

Partner [edit]

Topic /descriptor [edit] link to wiki attachment

Retrieved from "http://qviz.humlab.umu.se/index.php/SOTA_Attachment_Cross_Reference"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

http://qviz.humlab.umu.se/index.php/SOTA_Attachment_Cross_Reference (1 of 2)2006-09-29 08:49:12 SOTA Attachment Cross Reference - QVIZ

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/SOTA_Attachment_Cross_Reference (2 of 2)2006-09-29 08:49:12 Relvant State-of-the-Art Reports - QVIZ

Relvant State-of-the-Art Reports

From QVIZ

Jump to: navigation, search [edit] Most relevant State-of-the-Art Reports

● Knowedge Web http://knowledgeweb.semanticweb.org

❍ "D2.1.1: State of the art on the scalability of ontology-based technology":http:// knowledgeweb.semanticweb.org/semanticportal/home.jsp?_origin=%2Fhome. jsp&instance=D2.1.1%3A+State+of+the+art+on+the+scalability+of+ontology-based +technology&ontology=Documentation+Ontology&content=instance. jsp&instance_set=kweb&var_name=instance

❍ "D2.1.2.2v1: Report on realizing practical approximate and distributed reasoning for ontologies":http://knowledgeweb.semanticweb.org/semanticportal/home.jsp?_origin=% 2Fhome.jsp&instance=D2.1.2.2v1%3A+Report+on+realizing+practical+approximate +and+distributed+reasoning+for+ontologies&ontology=Documentation +Ontology&content=instance.jsp&instance_set=kweb&var_name=instance

❍ "D2.1.2: Report on methods for approximate reasoning, using knowledge compilation, language weakening and approximate deduction":http://knowledgeweb.semanticweb. org/semanticportal/home.jsp?_origin=%2Fhome.jsp&instance=D2.1.2%3A+Report+on +methods+for+approximate+reasoning%2C+using+knowledge+compilation%2C +language+weakening+and+approximate+deduction&ontology=Documentation +Ontology&content=instance.jsp&instance_set=kweb&var_name=instance

❍ "D2.1.3.1: Report on modularization of ontologies ":http://knowledgeweb.semanticweb. org/semanticportal/home.jsp?_origin=%2Fhome.jsp&instance=D2.1.3.1%3A+Report +on+modularization+of+ontologies&ontology=Documentation +Ontology&content=instance.jsp&instance_set=kweb&var_name=instance

● Bricks http://www.eswc2006.org/technologies/usb/proceedings-workshops/eswc2006- workshop-semantic-wikis.pdf

❍ See also ontologies mentioned such SWRC, COIN, DILIGENT ❍ See SOA Section 4.1 - service oriented architecture ❍ See Content Management Section 4.2 ❍ See Ontologies ( 4.2.3) ❍ See Annotations (4.2.4) ❍ See collections (4.2.5) ● SEKT ❍ See list http://www.sekt-project.org/rd/deliverables

■ Ontology evaluation http://www.sekt-project.org/rd/deliverables/wp01/sekt-d-1-

http://qviz.humlab.umu.se/index.php/Relvant_State-of-the-Art_Reports (1 of 3)2006-09-29 08:49:15 Relvant State-of-the-Art Reports - QVIZ 6-1-Ontology%20Evaluation.pdf

❍ DIP ■ DIP is primarily about Semantic Web Services, but not so relevant to QVIZ ■ http://dip.semanticweb.org/deliverables.html

Retrieved from "http://qviz.humlab.umu.se/index.php/Relvant_State-of-the-Art_Reports"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

http://qviz.humlab.umu.se/index.php/Relvant_State-of-the-Art_Reports (2 of 3)2006-09-29 08:49:15 Relvant State-of-the-Art Reports - QVIZ

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 15 times.

http://qviz.humlab.umu.se/index.php/Relvant_State-of-the-Art_Reports (3 of 3)2006-09-29 08:49:15 Mailing Lists - QVIZ

Mailing Lists

From QVIZ

Jump to: navigation, search

CGGR mailing list [edit]

From The Alexandria Digital Library is a rich gazetteer resource, complete with its own server architecture and access protocol. They also maintain the gazetter mailing list CGGR-L that will carry the occasional announcement from GEOBOF.

● http://listserv.ucsb.edu/lsv-cgi-bin/wa?SUBED1=cggr-l&A=1

● http://dli2.nsf.gov/archives/cggr-archive.html

● Alexandria Digital Library http://www.alexandria.ucsb.edu/

❍ see also SOTA Topic

"This conference has been publicised and looks relevant, topics including "geographical query interfaces for the web and geo-spatial libraries", "visualising the results of geographic searches" and "relevance ranking for geographical search"."

From: "Ross Purves" Subject: Workshop on Geographical Information Retrieval GIR'06 - Call for papers Date: Wed, 26 Apr 2006 14:37:24 +0200

Apologies for cross postings

Workshop on Geographical Information Retrieval GIR'06 - Call for papers ------http://www.geo.unizh.ch/~rsp/gir06/ ------

This is a first call for papers for a workshop on Geographic Information Retrieval, to be held in conjunction with the 29th ACM SIGIR Conference on Research & Development on Information Retrieval, Seattle 2006 (http://www.sigir2006.org/). The workshop is a follow-up to the previous successful workshops held in the last two years at SIGIR in 2004 and CIKM in 2005. The workshop will take place on 10th August immediately following the conference. You can find registration details for the workshop and conference on the SIGIR pages.

The purpose of this workshop is to bring together the growing community of researchers and practitioners working in the field of geographic information retrieval to discuss further progress within the field and potential future research strands. Examples of topics that are particularly relevant include,

http://qviz.humlab.umu.se/index.php/Mailing_Lists (1 of 3)2006-09-29 08:49:17 Mailing Lists - QVIZ but are not confined to:

. architectures for geographic search engines; . spatial indexing of documents and other media resources; . extraction of geographical context from documents and geo-datasets; . geographical annotation techniques for geo-referenced media; . design, construction, maintenance and access methods for geographical ontologies, gazetteers and geographical thesauri; . geographical query interfaces for the web and geo-spatial libraries; . visualising the results of geographic searches; . relevance ranking for geographical search;

We invite the submission of extended abstracts of up to 2000 words. All submissions will be reviewed by two members of the program committee, and all accepted papers will be published in the workshop proceedings. It is intended that following the workshop, presenters will be invited to submit full length papers to be considered for publication in a fully refereed journal publication. You should prepare your abstract in accordance with the SIGIR camera-ready instructions (http://www.acm.org/sigs/pubs/proceed/template.html) and submit it to Ross Purves ([email protected]) by June 22nd, 2006.

Further details of the workshop can be found at http://www.geo.unizh.ch/~rsp/gir06/

Please forward this message to anyone whom you think may have an interest in the workshop.

With best wishes,

Chris Jones (tag">c[email protected]) and Ross Purves ([email protected])

Retrieved from "http://qviz.humlab.umu.se/index.php/Mailing_Lists"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

http://qviz.humlab.umu.se/index.php/Mailing_Lists (2 of 3)2006-09-29 08:49:17 Mailing Lists - QVIZ

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 13 times.

http://qviz.humlab.umu.se/index.php/Mailing_Lists (3 of 3)2006-09-29 08:49:17 Electronic Library - QVIZ

Electronic Library

From QVIZ

Jump to: navigation, search Contents

● 1 Summary Electronic Library Topic

● 2 Electronic Library

● 3 The European Library (TEL)

● 4 BRICKS Project.

[edit] Summary Electronic Library Topic

We are interested in later enabling QVIZ to interrate archival materials and QVIZ social knowledge objects with a "central" European Library.

Electronic Library [edit]

The European Library (TEL) [edit] http://www.theeuropeanlibrary.org/

TEL was designated by the EC as the only solutuion and it is funded by a few institutions in member states.

http://www.nuk.uni-lj.si/dogodki/telmemor/nasveti.html

QVIZ comments:

Software: there are references to the software being available for open source. There is also different access strategies perhaps relevant to QVIZ (harvest, direct query... ) See also MICHAEL, there is some collaboration between TEL and MICHAEL (simple collections access accross Europe).

Rights issues discussions

From site: http://www.euractiv.com/en/culture/european-digital-library-needs-clarification-copyright-

http://qviz.humlab.umu.se/index.php/Electronic_Library (1 of 4)2006-09-29 08:49:18 Electronic Library - QVIZ issues/article-153068

The results of the stakeholder consultation on the Commission's plans to build a European Digital Library show strong support for the idea but point to the need to clarify the copyright issues. Opinions on intellectual property rights divides in particular cultural institutions and right holders. "Whatever policy the EU might favour, the most important element is a guarantee that authors are rewarded and that their moral rights are recognised and protected. It is a matter of justice that the providers of cultural content are not losing out while all other participating producers and service providers are remunerated," state the European visual artists.

"Once the digitisation is under way, contracts between rights holders and users will need to be developed in order to provide access to copyright digitised works," suggests the Hungarian publishers' and booksellers' association. By the end of 2006, a Commission Communication on 'Content Online' will address intellectual property rights management in the digital age.

European Digital Library is set to be build upon The European Library (TEL) -infrastructure, which is currently the gateway to the catalogue records of collections in a number of national libraries. The aim of the Commission is not to achieve a single database, but rather integrated access to the digitised material (books, audiovisual material, photographs, documents in archives etc.) of Europe’s cultural institutions such as libraries, archives and museums.

A recent report by an EU-funded project discovered significant gaps in digitisation capacities in the new EU member states. Barriers to digitisation include intellectual, financial and organisational issues such as technological infrastructure and the size of digital collections.

BRICKS Project. [edit]

Building resources for Integrated Cultural Knowledge Services http://www.brickscommunity.org/

Expect to be open source software for P2P, it is not clear if this is useful because of performance issues and the hype about "future" real semantic web support accross P2P network - the problem is there is no real way now to reason across a distributed network with OWL reasoners. However, they use an approach one might compare with EUDORA or BIBSTER, but use mappings to Dublin core from institutional proprietary schemas or some other standards; in some way they can query over dublin core or choose a particular schema which either queries against other like schemas or defaults to dublin core mappings. It is required to provide a map to Dublin Core when using one's own schema.

At the 2nd year's end (of a 3 year project), they have a harvest or import approach to collect data, but they say some direct query via RDF mapping would be in the future.

http://qviz.humlab.umu.se/index.php/Electronic_Library (2 of 4)2006-09-29 08:49:18 Electronic Library - QVIZ

TEL seems to make a Bricks node? However, there is no way for TEL to query into a Bricks network, only from Bricks to TEL.

Unfortunately, during a workshop, the panel leader said that Bricks was the electronic library! Our understanding would be that Bricks might provide tools for accessing institutions also with or without using the P2P solution, therefore useful to TEL for diversifying institutional access.

The user interface has interesting features, like TEL, it also does focus on collections, but it is flexible to build new virtual collections. It is not clear how they build these hierachical collections.

Searching across Bricks - currently they say that it is possible to load thesauri to support partner schemas, but it is unclear how those are shared across many search clients. Searching on text fields, as in TEL, does not utilise semantic web possibilities and thesauri. They do not solve any issues relating to the use of various controlled vocabularies (e.g. LCSH, etc).

It was mentioned that a multilingual service was possible, but that is clearly hype because machine translation on short strings (query terms) is not useful!

QVIZ Comments:

Depending on the licensing of the open source project (project ends June 2007), it might be possible to reuse software for access components. Currently, it is possible to join as a developer during the project, but we must submit a techical workplan to add new functionality to Bricks.

Retrieved from "http://qviz.humlab.umu.se/index.php/Electronic_Library"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

http://qviz.humlab.umu.se/index.php/Electronic_Library (3 of 4)2006-09-29 08:49:18 Electronic Library - QVIZ

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/Electronic_Library (4 of 4)2006-09-29 08:49:18 Relevant Projects - QVIZ

Relevant Projects

From QVIZ

Jump to: navigation, search Contents

● 1 New or recent Cultural Heritage projects

● 2 Digital library projects

● 3 TEL-ME-MOR

● 4 MICHAEL

● 5 Summary Electronic Library Topic

● 6 Electronic Library

● 7 The European Library (TEL)

● 8 BRICKS Project.

[edit] New or recent Cultural Heritage projects

● http://www.telmemor.net/projects.php

● http://www.cordis.lu/ist/digicult/projects_fp6.htm

● http://www.cordis.lu/ist/telearn/projects_fp6.htm

Digital library projects [edit]

TEL-ME-MOR [edit] http://www.telmemor.net/about.php

From the site: http://www.telmemor.net/about.php: Objectives

TEL-ME-MOR is supporting the 10 national libraries from the New Member States, which are partners in the project, in becoming full members of The European Library, an initiative, established under the aegis of the Conference of European National Librarians (CENL), providing unified access to the electronic resources of the main European National Libraries as well as to other library services.

By the end of the project, a comprehensive and easily searchable pan-European collection of top quality information resources, covering all subject areas of interest to the research community, will

http://qviz.humlab.umu.se/index.php/Relevant_Projects (1 of 6)2006-09-29 08:49:20 Relevant Projects - QVIZ be available on-line, via The European Library. Multilingual interfaces will be developed to enable users from the New Member States to access the on-line facility in their own language.

The second objective of TEL-ME-MOR is to raise awareness and disseminate information on the opportunities for participation in future projects, aimed at fostering an increased participation of institutions and organisations from the New Member States in future calls for proposals published by the European Commission within the Cultural Heritage and Learning sectors of the IST Programme.

Target audiences

TEL-ME-MOR addresses the cultural, educational, industrial and public sectors. It aims to bring together the various professional domain networks, the authorities which are responsible for the institutions and their services to the research sector, the research, scholarly and IT communities. In particular, the project targets the following audiences:

• Libraries, museums, archives

• Educational institutions (schools, universities, etc.)

• Government agencies and policy makers

• Local authorities

• Researchers

• ICT Small and Medium Enterprises (SMEs)

• Individual users.

MICHAEL [edit] http://www.michael-culture.org/

Multilingual Inventory of Cultural Heritage in Europe

Project descriptions at: http://www.michael-culture.org/project.html

From site:

MICHAEL aims to provide simple and quick access to the digital collections of museums, libraries and archives from different European countries. Work began in June 2004, with the focus on implementing an innovative multi-lingual open source platform that will be equipped with a search engine. By 2007, the MICHAEL platform will be capable of retrieving digital collections that are

http://qviz.humlab.umu.se/index.php/Relevant_Projects (2 of 6)2006-09-29 08:49:20 Relevant Projects - QVIZ dispersed across Europe. There will be many uses for MICHAEL, for example students and researchers will be able to discover information about European collections that might previously have been difficult to find. The services will also support cultural tourism, the creative industries and other interests.

From site: http://www.telmemor.net/projects.php

MICHAEL is a spin-off project from the activities carried out by MINERVA and it aims to provide simple and quick access to the digital collections of museums, libraries and archives from different European countries. The project will establish an international online service to allow its users to search across multiple national cultural portals from a single point of access. The material which will be made accessible via the project portal will include learning resources, catalogue information and description of physical collections, as well as images, 3D models and meta-data descriptions of archaeological sites, buildings, paintings, sculpture etc.

Summary Electronic Library Topic [edit]

We are interested in later enabling QVIZ to interrate archival materials and QVIZ social knowledge objects with a "central" European Library.

Electronic Library [edit]

The European Library (TEL) [edit] http://www.theeuropeanlibrary.org/

TEL was designated by the EC as the only solutuion and it is funded by a few institutions in member states.

http://www.nuk.uni-lj.si/dogodki/telmemor/nasveti.html

QVIZ comments:

Rights issues discussions

From site: http://www.euractiv.com/en/culture/european-digital-library-needs-clarification-copyright-

http://qviz.humlab.umu.se/index.php/Relevant_Projects (3 of 6)2006-09-29 08:49:20 Relevant Projects - QVIZ issues/article-153068

BRICKS Project. [edit]

Building resources for Integrated Cultural Knowledge Services http://www.brickscommunity.org/

BRICKS - Building Resources for Integrated Cultural Knowledge Services

BRICKS aims at integrating existing digital resources into a common and shared Digital Library, including as well materials from digital museums, archives and other similar cultural institutions.

http://qviz.humlab.umu.se/index.php/Relevant_Projects (4 of 6)2006-09-29 08:49:20 Relevant Projects - QVIZ to dublin core mappings. It is required to provide a map to Dublin Core when using one's own schema.

At the 2nd year's end (of a 3 year project), they have a harvest or import approach to collect data, but they say some direct query via RDF mapping would be in the future.

TEL seems to make a Bricks node? However, there is no way for TEL to query into a Bricks network, only from Bricks to TEL.

It was mentioned that a multilingual service was possible, but that is clearly hype because machine translation on short strings (query terms) is not useful!

Retrieved from "http://qviz.humlab.umu.se/index.php/Relevant_Projects"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

http://qviz.humlab.umu.se/index.php/Relevant_Projects (5 of 6)2006-09-29 08:49:20 Relevant Projects - QVIZ

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 11:48, 20 September 2006. ● This page has been accessed 15 times.

http://qviz.humlab.umu.se/index.php/Relevant_Projects (6 of 6)2006-09-29 08:49:20 Issue and Bug Tracking Software - QVIZ

Issue and Bug Tracking Software

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Trac Project

● 3 Lists of Java based solutions

● 4 scarab

● 5 jTrack

● 6 Trackit

● 7 ITracker

● 8 Trac

● 9 Jira

[edit] Summary

An issue and bug tracking solution is needed later.

Comments regarding Integration in the social collaborative tool:

We might consider how it could be useful in the collaborative environment. Another package to integrate that provides additional features.

If the URL can be linked as in a bookmark, and if we can "post data" into the system from external interfaces, then it might be useful to make semantic relations to these, etc. Can we extract content into the collaborative tool, can we capture parts of the UIs (result lists,etc)?

Trac Project [edit]

● http://trac.edgewall.org/

● Download http://trac.edgewall.org/wiki/TracDownload

● Installation http://trac.edgewall.org/wiki/TracInstall

● demo at site, but also see Dojo bug tracking at http://trac.dojotoolkit.org/

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (1 of 6)2006-09-29 08:49:22 Issue and Bug Tracking Software - QVIZ BSD license, Python

Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission; to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.

It provides an interface to Subversion, an integrated Wiki and convenient report facilities.

Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all project events in order, making getting an overview of the project and tracking progress very easy.

Trac is a lightweight project management tool that is implemented as a web-based application. Trac is written in the Python programming language and needs a database (either SQLite, PostgreSQL, or MySQL works). For HTML rendering, Trac uses the ClearSilver templating system.

Lists of Java based solutions [edit] http://java-source.net/open-source/issue-trackers scarab [edit] http://scarab.tigris.org/

Java, Apache license

jTrack [edit] http://jtrac.info/ http://sourceforge.net/project/showfiles.php?group_id=162983&package_id=184104

JTrac is a generic issue-tracking web-application that can be easily customized by adding custom fields and drop-downs. Features include customizable workflow, field level permissions, e-mail integration, file attachments and a detailed history view. jTrac is a web-based application ideal for issue tracking with built-in workflow. Designed to be generic, you can customize fields to track items (like bugs) & allocate tasks etc. jTrac is a lightweight J2EE application built on the Spring Framework.

Java, LGPL

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (2 of 6)2006-09-29 08:49:22 Issue and Bug Tracking Software - QVIZ

Trackit [edit] http://trackit.sourceforge.net/

Java, LGPL

TrackIt is a Web-based project tracking tool designed from the ground up to provide maximum flexibility, customization, and most importantly, usefulness to the developer. It has built-in support for various Extreme Programming constructs, as well as full CVS and Subversion integration. It also supports simple listings via HQL and advanced reporting via SQL.

ITracker [edit] http://trackit.sourceforge.net/

GPL

ITracker is a Java J2EE issue tracking system designed to support multiple projects with independent user bases. It supports features such as multiple versions and project components, detailed histories, per project user permissions and multiple email notifications. A brief feature list is available. Also a new ITracker roadmap is now available that provides details on the current features, and also describes features and implementation details for future releases.

Trac [edit] http://trac.blogmemes.com/trac_script/about

Sandbox http://projects.edgewall.com/trac/wiki/SandBox

Python ... Zope??? BSD License

From the site:

It provides an interface to Subversion, an integrated Wiki and convenient report facilities.

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (3 of 6)2006-09-29 08:49:22 Issue and Bug Tracking Software - QVIZ Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all project events in order, making getting an overview of the project and tracking progress very easy.

Trac has a built-in wiki engine, used for text and documentation throughout the system. WikiFormatting is used in wiki pages, tickets and check-in log messages. This allows for formatted text and hyperlinks in and between all Trac modules.

Editing wiki text is easy, using any web browser and a simple formatting system (see WikiFormatting), rather than more complex markup languages like HTML. The reasoning behind its design is that HTML, with its large collection of nestable tags, is too complicated to allow fast-paced editing, and distracts from the actual content of the pages. Note though that Trac also supports HTML, reStructuredText and Textile as alternative markup formats.

The main goal of the wiki is making editing text easier and encourage people to contribute and annotate text content for a project.

The wiki itself does not enforce any structure, but rather resembles a stack of empty paper sheets, where you can organize information and documentation as you see fit, and later reorganize if necessary.

Jira [edit]

We use it in Regio http://www.atlassian.com/software/jira/ Non-Profit & Open Source Licenses

JIRA is a bug tracking, issue tracking, and project management application developed to make this process easier for your team. JIRA has been designed with a focus on task achievement, is instantly usable and is flexible to work with.

Features

● Manage bugs, features, tasks, improvements or any issue ● A clean and powerful user interface that is easy to understand for both business and technical users ● Map your business processes to custom workflows ● Track attachments, changes, components and versions ● Full text searching and powerful filtering (customisable, saveable, shareable and subscribeable!) ● Customisable dashboards and real-time statistics ● Enterprise permissioning and security ● Easily extended to and integrated with other systems (including email, RSS, Excel, XML and source control) ● Highly configurable notification options ● Runs on almost any hardware, OS and database platform

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (4 of 6)2006-09-29 08:49:22 Issue and Bug Tracking Software - QVIZ

● Web service enabled for programmatic control (SOAP, XML-RPC and REST interfaces) ● and much more...

Retrieved from "http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (5 of 6)2006-09-29 08:49:22 Issue and Bug Tracking Software - QVIZ

● Special pages

● Printable version

● Permanent link

● This page was last modified 21:28, 28 September 2006. ● This page has been accessed 13 times.

http://qviz.humlab.umu.se/index.php/Issue_and_Bug_Tracking_Software (6 of 6)2006-09-29 08:49:22 Archive overview provenance principle - QVIZ

Archive overview provenance principle

From QVIZ

Jump to: navigation, search

Provenance dominates on the fond level. It's important to keep the records of one archival creator together. In Estonian case earlier times it has been quite a custom, to separate subunits of bigger institutions to separate independent fonds. But it doesn't mean, that we have lost context. For that kind of cases we can use the respective descriptive elements of ISADG.

http://qviz.humlab.umu.se/index.php/Archive_overview_provenance_principle (1 of 3)2006-09-29 08:49:25 Archive overview provenance principle - QVIZ

Arkis2- The central content registration tool for the National and Regional archives used in similiar way in NAE and SNA.

Selection matrix of archival content

Retrieved from "http://qviz.humlab.umu.se/index.php/Archive_overview_provenance_principle"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Archive_overview_provenance_principle (2 of 3)2006-09-29 08:49:25 Archive overview provenance principle - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 11:49, 20 September 2006. ● This page has been accessed 33 times.

http://qviz.humlab.umu.se/index.php/Archive_overview_provenance_principle (3 of 3)2006-09-29 08:49:25 Inner organization of Fonds - QVIZ

Inner organization of Fonds

From QVIZ

Jump to: navigation, search

By inner organizing of fond or archives there has been quite a big variaty of principles during the time.

Chronological principle [edit] chronological principle, then we would get for example the following structure: Fond - Estonian Historical Archives (EHA) subfond1 - EHA 1921-40 (Estonian Republic) subfond2 - EHA 1941-1944 (time of soviet-nazi occupations) subfond3 - EHA 1945-1990 - (time of Soviet Estonian Republic) ... In last case the important changes of workflow and organization of EHA are related to political contex

Functional principle [edit]

If we arrange the records of EHA by the functional principle, then we get Fond - Estonian Historical Archives (EHA) subfond1 - Management subfond2 - Collecting of records subfond3 - Preservation

Structural principle [edit] structural principle here is, that inner organization or hierarchy of archives or fond follows the structural organization of archival creator (institution). It is relevant mainly for the fond level. E.g. Fond - Estonian Historical Archives (EHA) NB! - EHA as archival creator, institution subfond1 Director subfond 2 - Department of Aquisition Subfond2 - Department of Preservation

Retrieved from "http://qviz.humlab.umu.se/index.php/Inner_organization_of_Fonds"

Views

http://qviz.humlab.umu.se/index.php/Inner_organization_of_Fonds (1 of 3)2006-09-29 08:49:27 Inner organization of Fonds - QVIZ

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/Inner_organization_of_Fonds (2 of 3)2006-09-29 08:49:27 Inner organization of Fonds - QVIZ

● This page was last modified 19:27, 20 September 2006. ● This page has been accessed 26 times.

http://qviz.humlab.umu.se/index.php/Inner_organization_of_Fonds (3 of 3)2006-09-29 08:49:27 Record Keeping Concept - QVIZ

Record Keeping Concept

From QVIZ

Jump to: navigation, search

Records Continuum Model

● http://john.curtin.edu.au/society/overview/index.html

● http://john.curtin.edu.au/society/australia/links.html

● Partner reference: ❍ http://ldb.project.ltu.se/?subpage=/projectweb/416e2881afc85/Beskrivning.html

● http://www.nla.gov.au/padi/

● http://www.naa.gov.au/recordkeeping/control/rkms/summary.htm

● OASIS ❍ http://www.oasis-open.org

❍ OASIS Reference Model 2002 http://ldb.project.ltu.se/main.php/CCSDS-650.0-B-1_OAIS.pdf? fileitem=1425539

❍ Reference Model for Service Oriented

Architecture 1.0 http://www.oasis-open.org/committees/download.php/19361/soa-rm-cs.pdf

Links from site: http://john.curtin.edu.au/society/australia/links.html

Australian ideas and management models

• Structuring the Records Continuum - Part One: Postcustodial principles and properties by Frank Upward at http://rcrg.dstc.edu.au/publications/recordscontinuum/ fupp1.html

• Records Continuum Research Group: Find out more about the Group's research and publications at http://www.sims.monash.edu.au/research/rcrg/index.html

• The Australian Commonwealth Record Series (CRS) System Summary at http://www.naa.gov.au/recordkeeping/control/CRS_summary.html For a more detailed explanation with instructions see the CRS Manual :Registration & description procedures for the CRS System. Canberra: National Archives of Australia (NAA). Recordkeeping and Descriptive Standards Section, December, 1999 at http:// naa12.naa.gov.au/manual/Introduction/CRSIntroduction.htm Access and management tools Access Tools

• National Archives of Australia: RecordSearch Access the Collection Databases at http://www.naa.gov.au/The_Collection/recordsearch. html You can search the collection or try the tutorial and do a general exploration of sources using your own search terms.

• State Records Authority of NSW. Archives Investigator This service enables users to search for records within the holdings of the State

http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept (1 of 5)2006-09-29 08:49:28 Record Keeping Concept - QVIZ

Records Authority with more precision and to display the important linkages of context. Available at http://investigator.records.nsw.gov.au/

• Queenland State Archives: ArchivesSearch Provides access to the database containing details of approved records and other information about State and local government agencies at http://www.archives.qld.gov. au/research/searchdatabase.asp

• John Curtin Prime Ministerial Library: Electronic Research Archive Provides access to personal papers, photographs, oral histories, copies of official records and other archival material relating to the life and times of John Curtin held in the JCPML collection or in other institutions around the world. The items are presented as: images (photographs, documents); full text (contents of documents); audio and video (oral histories, sound recordings, speeches, motion pictures); finding aids (text containing information about the titles and descriptions of material which has not been digitised). Available at http://dtl.lis. curtin.edu.au/.

• City of Sydney Archives: Archives Investigator Provides ambient, context and content information about archival records created by the Sydney City Council, other Councils absorbed by Sydney City, and Sydney Festival Ltd. Available at http://www.cityofsydney.nsw.gov.au/investigator/ Management tools

• Tabularium - an electronic control system for small archives at http://tabularium. records.nsw.gov.au/

• Archive Manager - A comprehensive archival documentation and management application for Windows. Designed for use in schools, clubs and commercial organisations, it caters for collections that typcially include both archival records and items of memorabilia. http://www.teigo.com.au/

• Australian Science Archives Project: Bright Sparcs This is a register of over 3,000 people involved in the development of science, technology and medicine in Australia, including references to their archival materials and bibliographic resources. Available at http://www.asap.unimelb.edu.au/ bsparcs/bsparcshome.htm

• RecFind - Business Informations Management Solutions Inc records management system at http://www.infomgtsolutions.com/RecFind.htm.

• TRIM - Tower Records and Information Management website at http://www.towersoft.co. uk/ Recordkeeping infrastructure tools Legislation

• National Archives of Australia: last legislation Archives Act 1983; the last major review completed in late 1996. See the report of the review’s findings in Australian Law Reform Commission. Review of the Archives Act of 1983 at http://www.austlii.edu. au/au/other/alrc/publications/issues/19/ALRCIP19.html

• Australian Capital Territory: Territory Records Act 2002 at http://www.legislation. act.gov.au/a/2002-18/default.asp

• New South Wales: State Records Act 1998 at http://www.records.nsw.gov.au/about/act. htm

http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept (2 of 5)2006-09-29 08:49:28 Record Keeping Concept - QVIZ

• Queensland: Public Records Act 2002. See the Plain English Guide to the State Records Act 2002 at http://www.archives.qld.gov.au/downloads/PRAplainenglishguide.pdf

• South Australia: State Records Act 1997 at http://www.archives.sa.gov.au/ management/legislation.html#State_Records_Act,_1997

• Western Australia: State Records Act 2000 at http://www.sro.wa.gov.au/about/ sra2000.html Standards

• Australian Standard for Records Management AS ISO 15489 – 2002. Available at http://www.naa.gov.au/recordkeeping/rkpubs/advices/advice58.html.

• International Standards Organisation (ISO) at http://www.iso.ch

• Design Criteria Standard for Electronic Records Management Software Applications (November 1997). The revised version of DoD 5015.2-STD, June 2002, defines the basic requirements based on operational, legislative and legal needs that must be met by records management application (RMA) products acquired by the Department of Defense (DoD) and its Components. It also defines requirements for RMA's managing classified records. Find out more at http://jitc.fhu.disa.mil/recmgt/standards.htm Metadata standards

• Australian Research Council Industry Partnership Metadata Project at http://rcrg. dstc.edu.au/research/spirt/deliverables.html

• National Archives of Australia and Office of Government Online. Australian Government Locator Service (AGLS) website, including the AGLS Metadata Standard, published as Australian Standard AS 5044 by Standards Australia in December 2002. Available at http://www.naa.gov.au/recordkeeping/gov_online/agls/summary.html

• National Archives of Australia. Recordkeeping Metadata Standard for Commonwealth Agencies at http://www.naa.gov.au/recordkeeping/control/rkms/summary.htm

• State Records Authority of NSW. NSW Recordkeeping Metadata Standard. Sydney: SRA, June 2001. Available for downloading on the SRA website at http://www.records.nsw. gov.au/publicsector/erk/metadata/rkmetadata.htm Professional knowledge, education and publications

• Australia. National Training Information Service. Competency Standard 236: Records and Archives at http://www.ntis.gov.au/cgi-bin/waxhtml/~ntis2/std.wxh? page=80&inputRef=515

• Canada. National Archives of Canada. Information Management Standards and Practices Division. Preliminary Study on the Core Competencies of the Future Records Specialist. Ottawa: National Archives of Canada. June, 1996. This report identifies distinct roles for recordkeepers as Recordkeeping Systems Analyst, Recordkeeping Educator/Consultant, Recordkeeping Strategist, Recordkeeping Policy Driver, Recordkeeping Logistician, Retrieval Expert. Available at http://www.imforumgi.gc.ca/ products/corerpt_e.pdf

• Canada. Alliance of Libraries, Archives and Records Management (ALARM) in partnership with the Cultural Human Resources Council. Competency Profile: Information Resources Specialists in Archives, Libraries and Records Management: A Comprehensive Cross-Sectoral Competency Analysis. April, 1999. Available at http:// www.culturalhrc.ca/english/document/alarmcomp_e.pdf

http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept (3 of 5)2006-09-29 08:49:28 Record Keeping Concept - QVIZ

Recordkeeping education programs in Australia

• Australian Society of Archivists website provides information about ASA accredited records and archives courses available at Australian tertiary institutions at http:// www.archivists.org.au/council/accreditedcourses.html

• The following Australian tertiary institutions currently (May 2001) offer courses in recordkeeping by distance learning, but you will need to visit the relevant institution's website for up-to-the-minute information about current offerings and fees.

* Curtin University of Technology: Department of Media and Information at http:// smi.curtin.edu.au/index.cfm * Edith Cowan University: Faculty of Communication, Health and Science: School of Computer and Information Science at http://www.scis.ecu.edu.au/ * Monash University: Faculty of Information Technology: School of Information Management and Systems at http://www.sims.monash.edu.au/index.html. * Royal Melbourne Institute of Technology: Faculty of Business. School of Business Information Technology at http://www.rmit.edu.au/browse?SIMID=i7l61p4f90ay. * University of Canberra: Faculty of Communications, Information Management and Tourism. School of Information Management and Tourism at http://comedu.canberra.edu. au/sc_details.cfm?ID=03. * University of New South Wales: Faculty of Commerce and Economics at http://www. sistm.unsw.edu.au/.

Publications

• Australian Society of Archivists publications page provides a select list of publications available for order at http://www.archivists.org.au/publications.html

Retrieved from "http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept (4 of 5)2006-09-29 08:49:28 Record Keeping Concept - QVIZ

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 10 times.

http://qviz.humlab.umu.se/index.php/Record_Keeping_Concept (5 of 5)2006-09-29 08:49:28 Partner archive systems - QVIZ

Partner archive systems

From QVIZ

Jump to: navigation, search

General access methods, data interchange formats. Metadata descriptions (data interchange) and administrative unit indexing are important. Is there Z39.50 access? If so, is admin unit an "access point"? Other access methods, other IST or nation projects to share archival information? Consider schemas, Collection Description used (ISAD(G), other?), interchange formats and where in system (EAD...), access strategies available, info regarding admin units management and access, and polygon data, etc. Digital archive solutions? How it works with archival descriptions ISAD(G)... etc.

Vision of Britain also, how are admin units managed, what are the ideas to manage them in QVIZ (update, harvest/ merge, etc) This can be the basis for to system requirements/specs. What kinds of queries are supported using admin units only (not polygon data), what can we say is need in the Comparison of admin unit issues across partners systems and some comparison to Vision of Britain model. This should lead to understanding the admin unit ontology requirements for QVIZ.

Retrieved from "http://qviz.humlab.umu.se/index.php/Partner_archive_systems"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

http://qviz.humlab.umu.se/index.php/Partner_archive_systems (1 of 2)2006-09-29 08:49:30 Partner archive systems - QVIZ

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 08:44, 19 September 2006. ● This page has been accessed 7 times.

http://qviz.humlab.umu.se/index.php/Partner_archive_systems (2 of 2)2006-09-29 08:49:30 SVAR and National Archives System Description - QVIZ

SVAR and National Archives System Description

From QVIZ

Jump to: navigation, search

Archive_structure

SNA_system_components

Retrieved from "http://qviz.humlab.umu.se/index.php/ SVAR_and_National_Archives_System_Description"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/SVAR_and_National_Archives_System_Description (1 of 2)2006-09-29 08:49:33 SVAR and National Archives System Description - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:14, 19 September 2006. ● This page has been accessed 15 times.

http://qviz.humlab.umu.se/index.php/SVAR_and_National_Archives_System_Description (2 of 2)2006-09-29 08:49:33 Vision of Britain System Description - QVIZ

Vision of Britain System Description

From QVIZ

Jump to: navigation, search

How to hold 10.5m statistics in one column of one table

Strengths and weaknesses of the DDI Aggregate

Data Extension in directly driving an on-line data visualisation system

Humphrey Southall (University of Portsmouth/ Great Britain Historical GIS)

Contents

● 1 A Vision of Britain through Time

● 2 Potential schools demand has yet to hit us

● 3 “Vision of Britain” is not just statistics

● 4 Data-centric Overview of GBH GIS:

❍ 4.1 When: Date Objects

❍ 4.2 Where: Gazetteer

■ 4.2.1 Gazetteer Overview:

■ 4.2.2 Key Source: Youngs’ Local Administrative Units of England

❍ 4.3 Sources: Source Documentation System

❍ 4.4 SDS Schematic:

❍ 4.5 What: Data Documentation System

● 5 Why we support DDI standard

❍ 5.1 January 2002 schematic:

❍ 5.2 DDI Aggregate Data Extension 101

● 6 GBH DDS: Entities and Relationships

● 7 GBH DDS Schematic:

● 8 GBH modifications to DDI

● 9 Additional presentational elements

● 10 Generating derived data

● 11 Graphing and mapping

● 12 Issue: Duplication between DDS and SDS

● 13 Columns in the 1831 Parish Table

● 14 1851 Census of Education

● 15 Issue: Categories and Variables

● 16 1841 Occupation Tables

● 17 Issue: Why hasn’t this been done before?

● 18 Issue: What use is this for academic researchers?

● 19 Our support for metadata standards ….

❍ 19.1 … is rather like the Blind Men and the Elephant

● 20 Web sites, etc

[edit] A Vision of Britain through Time

● Three year project funded by UK National Lottery ❍ Not JISC, not ESRC … ❍ Main product a web site launched 26th October 2004 ❍ Built on many earlier data and boundary digitisation projects ● A visualisation project, not a data library ❍ Created by a historical geographer, not a data librarian ● Designed to present 200 years of British census and vital registration data to a general audience: Life long Learners ❍ Much of the demand is from local and family historians

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (1 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

❍ data items often need to be disassociated from their original context ■ Original tables cover whole country for single date ■ Users want time series for single location ● A seriously popular (and populist) web site ❍ C. 30m page requests served since launch ❍ C. 40,000 distinct users per month ❍ AOL UK web site of the day in January

Potential schools demand has yet to hit us [edit]

● Key Stage 2 of the History National Curriculum for England requires that all students prepare: ‘A study investigating how an aspect in the local area has changed over a long period of time, or how the locality was affected by a significant national or local event or development or by the work of a significant individual’, using information on ‘education; population movement; houses and housing; religious practices; treatment of the poor and care of the sick …’ ● It is a legal requirement that all English children in state schools do such a project ● Key Stage 2 means ages 8-11 – typically, at age 9 ❍ No, we don’t know how to serve this audience either ● The Office of National Statistics tries to reply to all letters from schools requesting historical data for their local area

“Vision of Britain” is not just statistics [edit]

● Other content includes: ❍ Gazetteer/Geographical name authority (Over 50,000 administrative units) ❍ Descriptive Gazetteers (90,000+ entries; c. 5m words) ❍ Images of three sets of One Inch maps of Britain (20 Gb of scans) ❍ Administrative Boundaries (50,000 polygons) ❍ Text of the Preliminary and General Reports of every GB census 1801-1961 (3m. Words?) ❍ Text of Guide to Census Reports: Great Britain 1801-1966 (279 pages). ❍ 11 Travellers’ Tales (Defoe, Boswell, etc; c. 1.5m words) ● But this presentation focuses on data, and on the DDI implementation ❍ Statistical content fairly ordinary: big chunk of GB census reports since 1801, vital registration reports, etc

Data-centric Overview of GBH GIS: [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (2 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

When: Date Objects [edit]

● This is the fairly easy one ● Dates held directly within the data table ● … but we store dates in a specially defined date object (using Oracle’s object-relational capabilities), not in a conventional Oracle date value: ❍ Census data stored using simple year value ■ Means graphs, etc, treat censuses as regularly spaced ■ Exact date of each census stored elsewhere in system ❍ Unemployment counts, etc, stored using full calendar dates ❍ Vital registration data stored usually with a duration, I.e. a pair of full calendar dates ❍ Elsewhere, we store text strings within date objects, such as “around the reign of Edward II”, but with statistical data we require at least a specific year

Where: Gazetteer [edit]

● Every data value in the data table is associated with one of our 50,000 administrative units as defined in our gazetteer ❍ Quite independent of our DDI implementation ❍ UK administrative geographies too fluid to treat geographies as DDI variables, units as DDI categories ● All units in the gazetteer have an ID number, a type, and at least one name. ● All units in the gazetteer are required to be part of at least one higher level unit, but we do not necessarily know geographical locations ● If one or more boundary polygon is held for a unit, system can do choropleth mapping ● Presentation given on our gazetteer at IASSIST 2003.

Gazetteer Overview: [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (3 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

Key Source: Youngs’ Local Administrative Units of England [edit]

The main basis for populating the administrative units gazetteer So is this geographical information?

Sources: Source Documentation System [edit]

● This structure defines and provides IDs for: ❍ All the censuses taken in Britain between 1801 and 1961 ❍ All the reports published by each census ■ … and, eg for county reports, the separate publications comprising each report ❍ All the tables within each reports ❍ Column and row headings, notes to tables, etc ● The data table holds, for source tables we have computerised: ❍ “Source table IDs” ❍ Column within table ❍ Row within table ● Key point: an infinite number of source tables can be defined within a fixed set of Oracle tables ● System is able to reconstruct census reports in their entirety, including both text and tables ❍ System provides ‘drill-down’ mechanism, rather than exact reconstruction ❍ Follows hierarchies of units recorded in the gazetteer ● Non-census sources identified by simpler Dublin Core compliant system

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (4 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

SDS Schematic: [edit]

What: Data Documentation System [edit]

● Based closely on the DDI aggregate data extension ● No requirement from funding body or elsewhere for standards compliance ❍ Funding body’s only requirement was Dublin Core ❍ System is a large stand-alone web site ■ We are very interested in web services, but no one will fund us to develop them ■ Web service activity mainly to do with OGC and ADL standards ❍ Even our collaborators in the Arts and Humanities Data Service/UKDA not particularly interested ● Performance is a very large concern ❍ Large numbers of users already noted ❍ They want graphs and maps, not bulk data downloads ● So why implement the DDI?

Why we support DDI standard [edit]

● Vision of Britain system needed to be: ❍ Large ■ GB Historical DB holds c. 25 m data values ❍ Extensible ■ New funding bids adding data on ecclesiastical units, elections, industrial structure (but no money for new software) ❍ Provide direct access to individual data items ■ Users want local time series, not national maps ● Writing code to generate particular web pages from particular “data sets” impractical on this scale ● Once focus shifts from “data sets” and “census tables” to individual data values, holding all the data items in a “data items” table is

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (5 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

obvious ● But how to make it work?

January 2002 schematic: [edit]

DDI Aggregate Data Extension 101 [edit]

● Defines meaning of each data value by location within an nCube whose dimensions consist of variables, each defined as a set of categories ❍ For example, gender by age by cause of death ❍ Each different categorisation of cause of death is a different variable ■ The six Registrar General’s Decennial Supplements 1851-1901 use five different cause of death classifications, which we place in a variable group ❍ Category groups enable mapping of one variable into another ● Each nCube covers a universe ❍ Two nCubes might both combine gender and age, but one covers total population, the other total deaths ● The very highly abstract nature of this data model in itself creates practical problems

GBH DDS: Entities and Relationships [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (6 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

GBH DDS Schematic: [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (7 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

GBH modifications to DDI [edit]

● New concept: Cell references ❍ ID values (text strings) linking data table to data map ■ A/T DE designed to work with flat and hierarchic text files, not RDBMS ■ Discussed with Wendy Thomas! ❍ Generally mnemonic (e.g. “Tot_Pop”) ■ For system, could just as well be “Fred” ■ But helps non-DDI-literate humans use system ● Additional entity types: ❍ Database ❍ Theme ❍ Rate ● Attributes redefined as entities: ❍ Universes ❍ Measurement Units ● Entities not used: ❍ Category Groups

Additional presentational elements [edit]

● Database and themes ❍ Everything belongs to overall “database” ■ Relatively few changes needed to system to hold whole additional web sites, eg for other countries ❍ Most other elements assigned to specific themes ■ Population – Life & Death – Industry – Work and Poverty – Social Structure – Housing – Learning & Language – Roots & Religion

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (8 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

❍ Two more to be added ■ Agriculture and Land Use – Political Life ● Rates ❍ Define most accessible level of statistical data ❍ Defined by Numerator, Denominator and Multiplier ■ eg “Unemployment rate is number out of employment, divided by number economically active, multiplied by 100 ■ Not number in employment, multiplied by 1000

Generating derived data [edit]

● Variables mapped on to other variables ❍ eg detailed occupational categories mapped onto 5 social classes ❍ Defined by mapping each occupational category onto a particular social class category ● System then computes nCube to nCube mappings ❍ Defined in terms of cellRefs ❍ Checks that nCubes share universes ● We then pre-compute all derived data values implied by these mappings ❍ Currently means adding c. 2.5m additional data values ❍ This takes a long time! ❍ As does subsequent pre-computation of all rate values ❍ Could this be done by triggers within DBMS? ● NB all this means that the system includes a substantial knowledgebase on, for example, alternative occupational coding systems, and their relationships

Graphing and mapping [edit]

● Supports very general approach to creating graphs and maps ● Web site decides how to graph data based entirely on metadata: ❍ One dimension, one category, multiple dates: time series ❍ One dimension, two+ categories, one date: pie chart ❍ One dimension, two+ categories, 2+ dates: stacked chart ❍ Two dimensions, one dimension has only 2 categories: population pyramid (multiple pyramids if 2+ dates) ❍ Two dimensions, both have 3+ categories: getting tricky ❍ Three+ dimensions: currently ignored ❍ NB nCubes have to be “additive” for most of this to work ● Mapping nCubes permits very large number of logically valid maps ❍ Web site currently only maps rates ❍ One dimensional nCubes simple to maps ❍ Higher dimension nCubes raise big user interface issues ● Visualisation of more complex nCubes is seriously limited by constraints of a high volume web site

Issue: Duplication between DDS and SDS [edit]

● “Belt and braces” ❍ Some data values covered only by SDS, not DDS ■ Appear only in table reconstructions, not in maps/graphs ❍ Non-census data only in DDS ■ Appear only in maps/graphs ❍ Some duplication of information appears, in census tables organised as natural nCubes ■ eg age/sex structure tables ❍ Will be more problematic if we add tables with less geography ● But much information in DDS is interpretative ❍ Contains historical judgements that data from different censuses are broadly equivalent ■ eg “usual residence” versus “persons present” ❍ My assumptions about equivalence make it important that the SDS holds the original column/row headings ❍ Many important tables hold quite diverse data ■ Particularly true of parish tables

Columns in the 1831 Parish Table [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (9 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

1851 Census of Education [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (10 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

Issue: Categories and Variables [edit]

● Basic DDI principle: New set of categories => new variable ● It is good that GBH system includes: ❍ Variable group “Age”, with (currently) 12 categorisations ❍ Variable group “Cause of Death”, with 5 categorisations ❍ Variable group “Occupation”, etc ● But what to do where the same table from a particular census lists different sets of categories for different areas? ❍ Done for sensible reasons ❍ Not uncommon in occupation tables ❍ Also a major issue if we add electoral data ■ Candidates differ between constituencies

1841 Occupation Tables [edit]

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (11 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

Issue: Why hasn’t this been done before? [edit]

● This approach is very wasteful of disk space ❍ Largest users of space are, in fact, the seven indexes that we have built on the data table ● But does this matter? ❍ Entire Oracle content, including polygons, text, etc, fits into 10 Gb ❍ Scanned maps occupy 20 Gb even in down-sampled versions used in web site ❍ Our server came with 6 x 73 Gb disks, by default ❍ Oracle content is held permanently within the 32 Gb of RAM ● In general, social science data occupies what are now pretty trivial amounts of disk space ● Have conventional data library practices adapted to this?

Issue: What use is this for academic researchers? [edit]

● One answer is that we need to find out ❍ We were able to build this system only through lottery funding ❍ System paid for by the general public, so they had to be our primary audience ❍ In practice, the same interface is very useful to many academic historians doing local case studies ● System can provide full audit trail for otherwise ad hoc manipulations ❍ Tidying up and matching of geographical names done when loading data ❍ Geography conversion tables, for redistricting, held as unit-to-unit relationships ❍ Recodings held as category-to-category mappings ● Very regular data architecture makes system accessible to automated pattern seekers, including web crawlers ❍ Can use data to find metadata, as well as vice-versa ❍ Partly done to enable Google to explore the system ❍ But can also let the Geographical Analysis Machine in ❍ Seeking funding under e-social science programme

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (12 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

Our support for metadata standards …. [edit]

● Data Documentation System inspired by the DDI Aggregate Data Extension: http://www.icpsr.umich.edu/DDI

● Spatial data handling based closely on Open Geospatial Consortium (OGC) standards -- web services potentials: http://www.opengeospatial.org

● Data model for core gazetteer based on Swedish National Topographical Database, but details then heavily influenced by Alexandria Digital Library Gazetteer Content Standard: http://alexandria.sdc.ucsb.edu/~lhill/adlgaz

● Funding body required support for Dublin Core ❍ Most table references g_authority table, with DC-based columns: http://www.dublincore.org

● Text mark-up reflects Text Encoding Initiative guidelines http://www.tei.org

… is rather like the Blind Men and the Elephant [edit]

● This system probably provides more support for open standards than any other GIS in the social sciences or humanities ● Standards support is not simply to let us tick boxes on a funding application, but has deeply influenced system architecture ● But the view of the system provided by any one of those standards is very partial. ● System as a whole is a description of Britain designed by a historical geographer, and only incidentally a collection of data and metadata

Web sites, etc [edit]

● Vision of Britain: www.VisionOfBritain.org.uk ● Great Britain Historical GIS: www.gbhgis.org www.port.ac.uk/research/gbhgis ● Mailing list: www.jiscmail.ac.uk/lists/gbhgis

See original: http://www.iassistdata.org/conferences/2005/presentations/g2southall.ppt

Retrieved from "http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (13 of 14)2006-09-29 08:49:38 Vision of Britain System Description - QVIZ

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 14:14, 19 September 2006. ● This page has been accessed 80 times.

http://qviz.humlab.umu.se/index.php/Vision_of_Britain_System_Description (14 of 14)2006-09-29 08:49:38 Comparison of admin unit issues across partners systems - QVIZ

Comparison of admin unit issues across partners systems

From QVIZ

Jump to: navigation, search

Requirement question admin ontology

See also spreadsheet example:

Estonia

● scottish_ex_estonia.xls See requirements questions.

● Estonian_manors.xls

● Notes about these manors

● Estonian Administrative Units

Link to posts in WP3 index:

Sweden

● Swedish GIS-data set description

❍ Fredrik's database table for parishes: DBdata page fredrik_DB.zip

● Swedish admin unit's structure

● Regterra codes for admin types

● Admin unit coding schema Sweden

Great Britain

● British admin unit's structure

● British Administrative Districts

● Vision Of Britain Unit Relationships

● Admin unit coding schema in Vision Of Britain

To be added:

● Estonian structure diagram?

http://qviz.humlab.umu.se/index.php/Comparison_of_admin_unit_issues_across_partners_systems (1 of 3)2006-09-29 08:49:40 Comparison of admin unit issues across partners systems - QVIZ

Retrieved from "http://qviz.humlab.umu.se/index.php/ Comparison_of_admin_unit_issues_across_partners_systems"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

http://qviz.humlab.umu.se/index.php/Comparison_of_admin_unit_issues_across_partners_systems (2 of 3)2006-09-29 08:49:40 Comparison of admin unit issues across partners systems - QVIZ

● Special pages

● Printable version

● Permanent link

● This page was last modified 13:34, 15 September 2006. ● This page has been accessed 23 times.

http://qviz.humlab.umu.se/index.php/Comparison_of_admin_unit_issues_across_partners_systems (3 of 3)2006-09-29 08:49:40 Trackback - QVIZ

Trackback

From QVIZ

Jump to: navigation, search

Trackback functionality is needed http://www.ancestry.com/

Trackback and their use in CoP:s [edit]

Needed! For example saving searches.

Note: we must understand how we all interpret "trackback" and eventually document it by linking to a future specification page.

Refering to "saving searches", that note is good to see so that we better elaborate and categorise "trackback" features. It could be to the page (result list) or to a "user selected" specific resource (image) on the page. In the latter case, it might be that we only need identifiers to access the image or resource again and then we determine how we can access this resource again. In the former case, one can say that the page was a result of a querying or a browsing, of course.

Trackback SNA [edit]

The trackback functionality will be developed in the Project. This functionality is most needed in reference to digital images and and to extensively registered document databases (e.g. Swedish census database). Possibilities for trackback functions in catalouges (e.g. NAD) and search aides (e.x. estate inventory databases) will be investigated.

Retrieved from "http://qviz.humlab.umu.se/index.php/Trackback"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

http://qviz.humlab.umu.se/index.php/Trackback (1 of 2)2006-09-29 08:49:41 Trackback - QVIZ

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 16:41, 26 September 2006. ● This page has been accessed 25 times.

http://qviz.humlab.umu.se/index.php/Trackback (2 of 2)2006-09-29 08:49:41 Archive Standards - QVIZ

Archive Standards

From QVIZ

Jump to: navigation, search Contents

● 1 Image Format Standards for Digitised Materials

● 2 A Glossary of Archival and Records Terminology

● 3 Standards

● 4 Authorities

● 5 ISAD(G)

● 6 MARC-AMC

● 7 EAD

● 8 EAC

● 9 Thesauri Format Standards

[edit] Image Format Standards for Digitised Materials

In common usage is DjVu

A Glossary of Archival and Records Terminology [edit]

● http://www.archivists.org/glossary

Standards [edit]

● International Council on Archives ❍ http://www.ica.org/

❍ Committee on Descriptive Standards, a committee of the International Council on Archives. ■ http://www.icacds.org.uk/icacds.htm

Authorities [edit]

● ISAAR(CPF) International Standard Archival Authority Record for Corporate Bodies, Persons

http://qviz.humlab.umu.se/index.php/Archive_Standards (1 of 4)2006-09-29 08:49:43 Archive Standards - QVIZ and Families

● Metadata Authority Description Schema (MADS)

● EAC Encoded Archival Context

ISAD(G) [edit]

● ISAD(G) General International Standard Archival Description

● Standards for archival data interchange (system, presentation,etc)

MARC-AMC [edit]

● MARC-AMC (No longer in user at Swedish National Archive) ❍ MARC-AMC defined

EAD [edit]

Provides the means for encoding (XML) the archive description for materials. Common use for Finding Aids and also found as data interchange within certain archives.

● EAD (Electronic Archive Description) ❍ EAD defined

See XTF software and University of California

EAC [edit]

Standard structure for the recording and exchange of information about the creators of archival materials.

● EAC Encoded Archival Context

Thesauri Format Standards [edit]

● SKOS

The UKAT Subject Thesuarus does provide a SKOS formatted version, therefore, SKOS is one possible format for either exchange and likely use to support QVIZ thesauri.

Basic definition: A set of terms representing concepts which can include relationships among the

http://qviz.humlab.umu.se/index.php/Archive_Standards (2 of 4)2006-09-29 08:49:43 Archive Standards - QVIZ concepts, such as equivalence, hierarchy, and associative relationships.

See SKOS based thesauri http://www.w3.org/2004/02/skos/ and this SOTA.

Retrieved from "http://qviz.humlab.umu.se/index.php/Archive_Standards"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

http://qviz.humlab.umu.se/index.php/Archive_Standards (3 of 4)2006-09-29 08:49:43 Archive Standards - QVIZ

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 11:29, 27 September 2006. ● This page has been accessed 48 times.

http://qviz.humlab.umu.se/index.php/Archive_Standards (4 of 4)2006-09-29 08:49:43 Image annotation - QVIZ

Image annotation

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Relevant Publications, Standards related

● 3 Standards

● 4 Standards and Interoperability

● 5 Tools: Fotonotes

● 6 Image map related

[edit] Summary

The overall strategy is to build image maps for images that contain references to semantic links (queries), any semantic description, annotations (perhaps typed e.g. type=question, comment, etc).

Some tools can only annotate rectangular shapes (online too), others where the user can trace around the image segment, or even where the program guesses what shapes to draw (offline or java applets). Bricks prototype from the Austrian National Library, demonstrated a advanced tool to draw freehand shapes.

Relevant Publications, Standards related [edit]

● MIX (NISO Metadata for Images in XML) - XML schema for encoding technical data elements required to manage digital image collections http://www.loc.gov/standards/mix//

● PREMIS (Preservation Metadata) - A data dictionary and supporting XML schemas for core preservation metadata needed to support the long-term preservation of digital materials. http://www.loc.gov/standards/premis

● Semantic Web Image Annotation Interoperability http://www.w3.org/2001/sw/BestPractices/MM/interop.html

● Multimedia annotations on the Semantic web http://www.cs.vu.nl/~guus/papers/Stamou06a.pdf

● Image Annotation on the Semantic Web: Vocabularies Overviewhttp://www.w3.org/2001/sw/BestPractices/MM/ resources/Vocabularies.html ● See Annotea where they annotated SVG based images http://www.jibbering.com/svg/AnnotateImage.html

● SWAD-Europe Deliverable 9.3: Semantic Web tools to help authoring: A Semantic Web image annotation tool http:// www.w3.org/2001/sw/Europe/reports/report_semweb_access_tools/

● FOAF and Image annotation ❍ 'foaf:Image' ❍ FOAF and copiction -- Photo metadata: the co-depiction experimenthttp://rdfweb.org/2002/01/photo/

❍

❍ http://www.ilrt.bris.ac.uk/discovery/2003/07/staffdev/imageannotation.html

❍ http://www.kanzaki.com/docs/sw/img-descr20030827.html

● Easy annotation http://www.ilrt.bris.ac.uk/publications/researchreport/rr1065/report_html

From site http://www.ilrt.bris.ac.uk/publications/researchreport/rr1065/report_html

Issues for the Future

http://qviz.humlab.umu.se/index.php/Image_annotation (1 of 6)2006-09-29 08:49:46 Image annotation - QVIZ

'''Trust and Privacy'''

RDF can be used to say anything about anything, and coupled with the ability to annotate any image on the web, this could lead to both

* people annotating images that were not intended to be annotated - that were pehaps hidden by obscurity, and * people annotating images incorrectly or maliciously.

Retaining the source of these annotations within the application and the sotware is therefore essential, in order to be able to remove annotations where there are privacy implications.

'''Provenance Data'''

To handle the aforementioned issues of trust and privacy, tools will have to encode and process information about the provenance of data. As discussed above, the present application made use of the properties '''foaf:annotator''' and '''foaf: creationEvent''', which are '''not''' in the '''official FOAF schema'''. They are here as an experiment and will be probably moved into another namespace.

Extensions

Further kinds of data that we might want to include in annotations include:

* the identity of the Creator of the image * a URL relating the image to some event's homepage * EXIF data

Standards [edit]

From Semantic Web Image Annotation Interoperability http://www.w3.org/2001/sw/BestPractices/MM/interop.html

2. Image annotation standards: an inside view

An inside view: Short descriptions of the standard to be covered by this document such as MPEG-7, VRA, EXIF, DC, IPTC for "JPEG images", XMP, JPEG-2000 metadata, etc ... We should provide the details that are important for the interoperabilty !

MPEG-7: The MPEG-7 standard, formally named "Multimedia Content Description Interface", provides a rich set of audiovisual Description Tools (Descriptors and Description Schemes) and a Description Definition Language (DDL) that can be used to create the metadata for multimedia documents and can be the basis for applications enabling search, filtering, browsing and retrieval of multimedia content. MPEG-7 provides terms for the description of the creation and production process of the content (director, title), terms related to the usage of the content (copyright pointers, usage history, broadcast schedule), terms related to the storage features of the content (storage format, encoding), terms representing structural, spatial, temporal or spatiotemporal relationships of the content (scene, regions, region motion tracking), terms relevant to low level features(color, texture, sound timbre, melody description), terms representing objects, events, interactions among objects, summaries, variations, user preferences, usage history etc.(MPEG7)

http://qviz.humlab.umu.se/index.php/Image_annotation (2 of 6)2006-09-29 08:49:46 Image annotation - QVIZ

VRA: The VRA Core Categories is a metadata element set appropriate for the description of works of visual culture as well as their digital representations or copies in different formats and modalities. It consists of terms suitable for the description of the title, subject, creator, location, material, dimensions, style and period of the artistic creation. (VRA )

IPTC: The IPTC collection of metadata standards is used for the improvement of news interchange. News Markup Language (NewsML) provides a structure related to a specific news event called News Item that may consist of text, photos, video, audio relevant to this event and metadata describing the content and the interrelations of these diverse modalities (http://www.newsml.org/pages/index.php ). News Industry Text Format (NITF) is an XML format for metadata describing news articles from the point of view of content, structure and preferable format for end users (http://www. nitf.org/ ), Sports Markup Language (SportsML) is an XML vocabulary for the interchange of multimedia documents concerning different kinds of sports events, such as scores, schedules, standings, statistics.( http://www.sportsml.com/ ). ProgramGuide Markup Language (ProgramGuideML) is an XML vocabulary for the interchange of Radio/TV Program Information based on NewsML (http://www. programguideml.org/pages/index.php ).

EXIF data description vocabulary: The Exif vocabulary compounds of terms that can be used for the description of very specific technical attributes of an Image, such as length, width, resolution, compression, the number of pixels per resolution unit in the image width direction, the name and version of the software or firmware of the camera or image input device used to generate the image, etc. (http://www.kanzaki. com/ns/exif)

XMP (Extensible Metadata Platform): Adobe's Extensible Metadata Platform (XMP) is a labeling technology that allows you to embed metadata about the title, creator, copyright, subject of an image. XMP is flexible and extensible, so it can be used to manage and organize files, simplify permissions and copyright issues, and even to view camera settings for digital photo graphs. (http://www.adobe.com/products/xmp/ main.html)

CIDOC-Conceptual Reference Model (CRM): CIDOC-CRM facilitates the integration of interchange of heterogeneous cultural heritage information. The CRM is the culmination of more than a decade of standards development work by the International Committee for Documentation (CIDOC) of the International Council of Museums (ICOM). CIDOC-CRM consists of terms describing entities, physical objects, man-made objects, events, places depicted on an image, etc. ( http://cidoc.ics.forth.gr/ )

Web Content Accesibility Guidelines 2.0 (WAI-WCAG 2.0): WCAG 2.0 contains principles, guidelines, success criteria, benefits, and examples that define and explain the requirements for making Web-based information and applications usable to a wide range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning difficulties, cognitive limitations, limited movement, speech difficulties, older people and people who use a wide variety of assistive technologies. (http://www.w3.org/TR/WCAG20/ )

Composite Capabilities/Preference Profiles (CC/PP): CC/PP vocabularies provide descriptions of device capabilities and user preferences. They are often referred to as devices• delivery context and can be used to guide the adaptation of content presented to that device.( http://www.w3.org/TR/2004/REC-CCPP-struct-vocab- 20040115/ )

Standards and Interoperability [edit]

http://qviz.humlab.umu.se/index.php/Image_annotation (3 of 6)2006-09-29 08:49:46 Image annotation - QVIZ

● EXIF Semantic Web Ontologies

From Semantic Web Image Annotation Interoperability http://www.w3.org/2001/sw/BestPractices/MM/interop.html

.1 EXIF Interoperability

One of today's commonly used image format and metadata standards is the Exchangeable Image File Format [EXIF]. This file format provides a standard specification for storing metadata regarding image. Metadata elements pertaining to the image are stored in the image file header and are marked with unique tags, which serves as an element identifying.

As we note in this document, there is ongoing interest in representing image metadata using Semantic Web representation language, such as RDF and OWL. There has recently there has been efforts to encode this EXIF metadata in such Web standards. Encoding EXIF metadata in Semantic Web standards will provide a variety of benefits:

* As the Semantic Web grows, EXIF data encoded in RDF will provide the ability to link to existing metadata on the Web. For example, details regarding specific cameras referenced in EXIF data can be represented using RDF. This will provide automatic integration of EXIF with other data on the Web. * Ability to share metadata on the Web in a standards compliant representation format

EXIF Semantic Web Ontologies

Recently, there have been various efforts to represent the EXIF metadata specification using RDFS. Below, we are the results of two of these efforts:

* Kanzaki EXIF RDF Schema [Kanzaki-EXIF] * Norm Walsh EXIF RDF Schema [Walsh-EXIF]

The [Kanzaki-EXIF] RDFS ontology provides an encoding of the basic EXIF metadata tags in RDFS. Essentially these are the tags defined from Section 4.6 of [EXIF]. We also note here that relevant domains and ranges are utilized as well.

The [Walsh-EXIF] RDFS ontology provides another encoding of the basic EXIF metadata tags in RDFS. Again, these are the tags defined from Section 4.6 of [EXIF].

We note here that both of these ontologies are semantically very similar, thus this issue is not addressed here. Essentially both are a straightforward encodings of the EXIF metadata tags for images (see [EXIF]). There are some syntactic differences, but again they are quite similar; they primarily differ in their naming conventions utilized. EXIF Conversion Services

The creators of the previously mentioned EXIF RDFS ontologies ([Kanzaki-EXIF] and [Walsh-EXIF]) additionally provide conversion services to their defined schemas. Exif-to-RDF Converter

EXIF-to-RDF ([Kanzaki-Converter]) is a metadata extractor for EXIF images. In particular the service takes a URL to an EXIF image and extracts the embedded EXIF metadata. The service then converts this metadata to the [Kanzaki-EXIF] schema and returns this to the user.

http://qviz.humlab.umu.se/index.php/Image_annotation (4 of 6)2006-09-29 08:49:46 Image annotation - QVIZ

Tools: Fotonotes [edit] http://fotonotes.net/

Flicker credits this tool.

1. Ajax/DHTML fnclient.js javascript client. 2. Re-written PHP4/5 server-side fotonotes.php script. 3. Stores annotation in JPEG file headers. 4. Abstract/concrete classes stub code for alternate storage strategies (e.g., database).

Dependency on jpeg files and it writes annotations into the file. This is not an issue, since the annotations can be redirected anywhere and potentially recombined later.

Example at http://fotonotes.net/

Image map related [edit]

Retrieved from "http://qviz.humlab.umu.se/index.php/Image_annotation"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Image_annotation (5 of 6)2006-09-29 08:49:46 Image annotation - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 13:18, 21 September 2006. ● This page has been accessed 18 times.

http://qviz.humlab.umu.se/index.php/Image_annotation (6 of 6)2006-09-29 08:49:46 Web Tools: Screen Capture - QVIZ

Web Tools: Screen Capture

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background:

● 3 dompdf

● 4 RealObjects: PDFreactor, Edit-on ...

[edit] Summary

We look at a means to make references to content that may contain actual text or text and images. This might be on an external page or even with QVIZ content itself. One issue is preservation, if the content changes, any references to actual text would become a dead link.

TODO: Experiment with Diigo bookmarks and annotations on "changing content" ... what is their means to handle references to changed content? In some engines, the reference is orphaned, but remains somewhere on the page.

Some options:

HTML --> JPEG

XHTML or HTML --> PDF --> JPEG

PDF is not so usable to users for viewing web content, therefore one path is to convert the PDF to JPEG and then perform image annotations - image annotations would be required for thematic maps and other interactive image building by users.

PDF --> JPEG, there are many tools, but for (X)HTML --> PDF, there are few. One PHP5 based and other commercial. With the commerical versions, that can be restricted to the OS, such as windows.

QVIZ: If the PDF solution must be done, then PHP transformation version would be fine, we set up special servers to perform special functions and that would help reduce load on the central server.

http://qviz.humlab.umu.se/index.php/Web_Tools:_Screen_Capture (1 of 4)2006-09-29 08:49:48 Web Tools: Screen Capture - QVIZ

Background: [edit]

● http://devzone.zend.com/node/view/id/226

● http://digg.com/programming/Convert_HTML_to_PDF_with_PHP

[edit] dompdf dompdf - the PHP 5 HTML to PDF converter. dompdf is a (mostly) CSS compliant HTML rendering engine written in PHP. It supports external stylesheets, inline style tags, and the style attributes of individual HTML elements. Requires PHP 5. http://www.digitaljunkies.ca/dompdf

FAQ: http://www.digitaljunkies.ca/dompdf/faq.php

Blog reference from: http://digg.com/programming/Convert_HTML_to_PDF_with_PHP

PHP5, plus DOM extention. LGPL

Downloads: http://www.digitaljunkies.ca/dompdf/downloads.php http://sourceforge.net/projects/dompdf

Note: the online installation description also describes various sourceforge downloads to install additional fonts, etc

RealObjects: PDFreactor, Edit-on ... [edit] http://www.realobjects.com/Overview.422.0.html

Commercial, too expensive for project and multiple installations.

http://qviz.humlab.umu.se/index.php/Web_Tools:_Screen_Capture (2 of 4)2006-09-29 08:49:48 Web Tools: Screen Capture - QVIZ

● PDFreactor is a powerful formatting processor for converting XML and XHTML/HTML documents into PDF. It uses Cascading Style Sheets (CSS) to define page layout and styles. The brand new server-side tool enables a great variety of applications in the fields of ERP, eCommerce and Electronic Publishing. It allows you to dynamically generate PDF documents such as invoices, delivery notes and shipping documents on-the-fly. Fully integrated clean-up processes also enable the processing of legacy HTML web content, allowing you to easily add server-based PDF generation functionality to your application or service.

● Edit-on Pro is a Java Applet Rich Text Client that adds comprehensive WYSIWYG XHTML/ XML editing functionality to a wide range of Content Management, Knowledge Management, e-Learning and other Web-based applications. It empowers business users with an intuitive, word processor-like interface for authoring and publishing web content using a browser.

● Edit-on is the JavaBean Rich Text Client that provides the same WYSIWYG XHTML/XML editing functionality as edit-on Pro 4. It enables developers to quickly integrate comprehensive and robust rich text authoring functionality into Java Swing-based desktop applications using Sun JavaBean-compliant visual development environments.

Retrieved from "http://qviz.humlab.umu.se/index.php/Web_Tools:_Screen_Capture"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

http://qviz.humlab.umu.se/index.php/Web_Tools:_Screen_Capture (3 of 4)2006-09-29 08:49:48 Web Tools: Screen Capture - QVIZ

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:03, 15 September 2006. ● This page has been accessed 8 times.

http://qviz.humlab.umu.se/index.php/Web_Tools:_Screen_Capture (4 of 4)2006-09-29 08:49:48 Prominent digital repositories Technologies - QVIZ

Prominent digital repositories Technologies

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Fedora

● 3 Fedora Related Tools

● 4 Fedora based Application/VALET

● 5 Fedora based Application/ELATED

● 6 Fedora based Application/VUE

● 7 Fedora based Application/...

● 8 Fedora based Application/...

● 9 midgard

[edit] Summary

Noteworthy digitial repository software. In the US and Europe, DSPACE and Fedora are popular, however, Fedora architecture does enable its reuse and might enable QVIZ to build upon. Fedora does have more potential to build upon as evidenced by projects that have already built upon it. DSPACE does have a fixed workflow and was initially not meant as a repository where users constantly update existing materials.

Fedora [edit]

● http://www.fedora.info/

● info sheet [1]

● brochure http://fedora.info/documents/brochure/Fedora%20Page%20Final.htm

● Useful blog entry ❍ http://feeds.dltj.org/DisruptiveLibraryTechnologyJester

Of interest to QVIZ:

● The user of web services to work with Fedora ● It uses or can use METS for describing digital objects, however, Fedora objects can be defined. Additional appliations have been made - built upon Fedora (see link below)

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (1 of 6)2006-09-29 08:49:50 Prominent digital repositories Technologies - QVIZ

● Do not confuse with Fedora from Redhat when googling!

Overview

Fedora open source software gives organizations a flexible service-oriented architecture for managing and delivering their digital content. At its core is a powerful digital object model that supports multiple views of each digital object and the relationships among digital objects. Digital objects can encapsulate locally-managed content or make reference to remote content. Dynamic views are possible by associating web services with objects. Digital objects exist within a repository architecture that supports a variety of management functions. All functions of Fedora, both at the object and repository level, are exposed as web services. These functions can be protected with fine- grained access control policies.

Web Services Interfaces

● Web services and RESTFul services ● http://fedora.info/documentation/

❍ API-M ❍ API-M-LITE (API-M-LITE Users Guide) ❍ API-A ❍ API-A-LITE (API-A-LITE Users Guide) ❍ Search: Repository Search via API-A-Lite (REST) Users Guide ❍ Simple OAI: OAI-PMH Provider (REST) Users Guide ❍ RISearch: Resource Index Search (REST) Users Guide

Fedora Related Tools [edit]

Fedora-OKI Bridge http://shiva.tcs.tufts.edu/~akumar03/vue/fedora/

The Fedora-OKI Bridge was developed to connect an OKI-compliant application to a Fedora repository service.

● OKI-compliant software bridge for connecting to Fedora repositories ● Access Fedora 1.2.1 repositories ● Publish to Fedora 1.1.1 repositories

VTLS Open Source Components (OSC)

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (2 of 6)2006-09-29 08:49:50 Prominent digital repositories Technologies - QVIZ http://www.vtls.com/Products/osc.shtml

VTLS Open Source Components (OSC) provides a suite of useful tools and services that integrate with Fedora repositories. These services include:

● SRU/SRW Interface (see SOTA Access Strategies Access_Stategies Search/Retrieve via URL) is a standard search protocol for Internet search queries, ) ● Metadata Extraction Service via JHOVE ● Handle System Integration for Fedora ● Content Model Configuration Service ● Web Crawler Exposure Service (e.g., to Google)

Fedora based Application/VALET [edit]

● Applications/tools based on Fedora (see how they built on Fedora) ❍ http://fedora.info/tools/index.shtml

Application/VTLS

VALET for ETDs is a customizable, web-based interface to Fedora. Based on Fedora 2.0

It allows remote users to submit content into a VITAL or FEDORA digital object repository. VALET for ETDs features include:

● Handling of any file format ● Configurable metadata entry ● Staged submission process whereby any number of review stages can be integrated ● Authorization of edit, delete, or approval for submitted content prior to ingest

VALET for ETDs is a customizable, web-based interface that allows remote users to submit Electronic Theses & Dissertations into a FEDORA™ digital object repository. VALET for ETDs has been designed to handle submission of any file format and allows contributors and other content creators to enter metadata into configurable, form-based templates. VALET for ETDs is designed to allow for a staged submission process whereby any number of review stages can be integrated to ensure that authorized staff have the ability to edit, delete or approve submitted ETDs prior to ingest into the repository.

VALET for ETDs is offered as a free, open-source solution for web self-submission of ETDs. This solution builds upon our collaborative experience with the NDLTD Project at Virginia Tech, the ADT Program and the ARROW Project in Australia to build a 'best of breed' solution for web submission of ETDs. VALET for ETDs is bundled with a FEDORA™ digital object repository and a Mckoi database (MySQL or Oracle may also be used). VALET for ETDs has pre-configured

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (3 of 6)2006-09-29 08:49:50 Prominent digital repositories Technologies - QVIZ templates for metadata capture in Dublin Core and ETD-MS formats, but can be extended to support other metadata formats or schemas such as MARCXML.

VALET for ETDs has also been designed to allow administrators to carefully control who can submit content and how that content is submitted. VALET for ETDs provides support for integration with an institution's user authentication and authorization system and allows for restrictions to be placed on the number and types of content allowed for submission. VALET for ETDs further supports e-mail notifications to content aggregators and reviewers.

VALET for ETDs is an open-source version of VALET, our web-based interface for submission of content into VITAL. The full version of VALET, used in conjunction with VITAL, enables enhanced functionality including additional templates for various content types, full-text indexing, citable Handles DOIs (Digital Object Identifiers) and other features.

Fedora based Application/ELATED [edit] http://elated.sourceforge.net/

ELATED is a lightweight, general-purpose application for managing digital files. ELATED is built on top of the Fedora Repository system, and can be used as a digital assets management system, an institutional repository, or to meet other collection archiving, publishing and searching needs.

● Dublin Core metadata entry and search ● Custom metadata by collection ● Automatic previews for images ● Collections with simple editorial workflow ● Indexing and searching of content ❍ (e.g. text in MS Word or PDF document) ● User feedback, enabled by collection ● Select and import existing Fedora objects

Fedora based Application/VUE [edit] http://vue.tccs.tufts.edu/

The Visual Understanding Environment (VUE) project at Tufts UIT Academic Technology is focused on creating flexible tools for integrating digital resources into teaching and learning. VUE provides a visual environment for structuring, presenting, and sharing digital information. Using VUE's concept mapping interface, faculty and students design semantic networks of digital resources drawn from digital libraries, local and remote file systems and the Web. The resulting content maps can then be viewed and exchanged online.

Release 1.5 is a major step torward VUE 2.0 which will provide a range of new features including

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (4 of 6)2006-09-29 08:49:50 Prominent digital repositories Technologies - QVIZ presentation tools, support for RDF and integration support for learning management systems (LMS/ VLEs) and other educational software environments. The goal is to define a new genre of educational software focused on the direct support of exploring, connecting and thinking with digital content.

● Visual environment for structuring, presenting, and sharing digital info ● OKI-compliant software bridge for connecting to FEDORA repositories ● Concept mapping interface ● View and exchange content maps online

Fedora based Application/... [edit]

Fedora based Application/... [edit] midgard [edit]

CMS based on fedora. See also image annotation tools http://www.midgard-project.org/midgard/1.7/

Retrieved from "http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (5 of 6)2006-09-29 08:49:50 Prominent digital repositories Technologies - QVIZ

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 14:52, 21 September 2006. ● This page has been accessed 36 times.

http://qviz.humlab.umu.se/index.php/Prominent_digital_repositories_Technologies (6 of 6)2006-09-29 08:49:50 Digital Object Metadata - QVIZ

Digital Object Metadata

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 1.1 Digital archives

● 3 1.2 METS (Metadata Encoding and Transmissio Standard)

● 4 Discovery

[edit] Summary

We reference digital objects from partner archives, we upload or reference objects external to archives. What metadata standards might we use or integrate?

1.1 Digital archives [edit]

See Digital archive repositories such as DSPACE, FEDORA, OAC,CDL METS Repository (uses METS)

Usually, all provide OAI access to provide Dublin Core records describing the digital objects.

1.2 METS (Metadata Encoding and Transmissio Standard) [edit]

METS (Metadata Encoding & Transmission Standard) - Structure for encoding descriptive, administrative, and structural metadata

XML based for search and presentation. In google,look for some XML/RDF examples also

● http://www.loc.gov/standards/mets/

● http://www.loc.gov/standards/mets/mets-schemadocs.html

● Extentions: http://www.loc.gov/standards/mets/mets-extenders.html

METS is used by OAC archives (finding aids) to describe objects reference in the EAD finding aids, and other University of California systems (library). METs can reference administrative info and other metadata objects such as EAD, MARC, etc.

http://qviz.humlab.umu.se/index.php/Digital_Object_Metadata (1 of 3)2006-09-29 08:49:51 Digital Object Metadata - QVIZ

METS - Metadata Encoding & Transmission Standard (for EAD, Digital libraries)

Discovery [edit]

Austrialia

Museum and archive. They composed a metadata schema that included EAD and Dublin Core elements. Very high level.

Retrieved from "http://qviz.humlab.umu.se/index.php/Digital_Object_Metadata"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Digital_Object_Metadata (2 of 3)2006-09-29 08:49:51 Digital Object Metadata - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 13:03, 21 September 2006. ● This page has been accessed 6 times.

http://qviz.humlab.umu.se/index.php/Digital_Object_Metadata (3 of 3)2006-09-29 08:49:51 Semantic repositories and other basis repository techologies - QVIZ

Semantic repositories and other basis repository techologies

From QVIZ

Jump to: navigation, search Contents

● 1 Some thoughts

● 2 Repositories for content, workspace, etc

● 3 Semantic Repository Infrastructure Tools

● 4 OpenLink Data Spaces

● 5 Virtuoso Open-Source Edition

● 6 OWLIM

● 7 Reasoners

[edit] Some thoughts

● Performance and scalability are a critical problem in semantic repositories and dependent on the complexity of reasoning support.

One might choose RDFS, RDF, or Owl-lite and expect better scalability then OWL-DL. To support inferencing and expect reasonable performance, in-memory models are often the main approach, but scalability is then limited to available computer RAM. What we expect to see (Technology watch) is more tools based on relatation or object-relational offering SPARQL and different levels of support for interferencing. Likely, a distributed SPARQL query would be interested, although it is not clear now how reasoning over distributed models would work. Currently, a system might only make simple RDF-based query to distributed peer models, but only use full reasoning support in queries on single models.

Eventually, we expect SPARQL query interfaces to be supported by most semantic repositories, even relational database "non- semantic repositories" could support it as another query interface.

Repositories for content, workspace, etc [edit]

● Java Content Repository ❍ Apache Jackrabbit

An Apache implementation of the open source implementation of JSR-170

With blog example: http://www.artima.com/lejava/articles/contentrepositoryP.html http://www.artima.com/lejava/articles/examples/rabbitblog.zip http://www-128.ibm.com/developerworks/java/library/j-jcr/index.html

See deployment modes: consider sharable http://jackrabbit.apache.org/doc/deploy.html

http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies (1 of 5)2006-09-29 08:49:53 Semantic repositories and other basis repository techologies - QVIZ http://jackrabbit.apache.org/doc/arch/overview.html

Semantic Repository Infrastructure Tools [edit]

● OpenLink Data Spaces ❍ Virtuoso Open-Source Edition

● Piggy-Bank using Jena http://simile.mit.edu/piggy-bank/

● Sesame http://www.openrdf.org

● OWLIM http://www.ontotext.com/owlim/

❍ SwiftOWLIM ❍ BIGOWLIM http://www.ontotext.com/owlim/

● Jena based http://jena.sourceforge.net/

● instance store http://instancestore.man.ac.uk/

● KAON2 http://kaon2.semanticweb.org/

OpenLink Data Spaces [edit]

OpenLink Data Spaces allows SPARQL queries to be performed on ODS data via SIOC ontology mappings.

(SIOC (Semantically-Interlinked Online Communities Project) see SOTA Community and collaboration related standards)

* http://virtuoso.openlinksw.com/wiki/main/Main/ODSSIOCRef * http://swik.net/OpenLinkDataSpaces * See Virtuoso Open-Source Edition http://virtuoso.openlinksw.com/wiki/main/Main/

A distributed collaborative application suite aimed at simplifying the creation of points of presence on the web for exposing, exchanging, and creating data. It uses the power of multi-model (Relational and Graph) data management to provide integrated views of data that resides in Blogs, Wikis, Feed Aggregators, Discussion Forums, Bookmark Managers, and other online community application realms. It uses relational data to shared ontology (e.g SIOC, FOAF, and Atom OWL) mapping and an in-built Triple Store (with Virtual Graph capability) to expose its SQL data to SPARQL clients via instance specific SPARQL Query endpoints. It also supports GData and OpenSearch query access to the same data

See Virtuoso Open-Source Edition

Virtuoso Open-Source Edition [edit]

Language Runtime Hosting PHP, java ,mono

OpenLink Software announces the open source licensing of most of its Virtuoso product. All the database, WebDAV/web server and SOA functions of Virtuoso are part of the open source release. There is a commercial release which additionally features virtual database and replication capabilities.

What is Virtuoso

http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies (2 of 5)2006-09-29 08:49:53 Semantic repositories and other basis repository techologies - QVIZ

Virtuoso is at the core a high performance object-relational SQL database. As a database, it provides transactions, a smart SQL compiler, powerful stored procedure language with optional Java and .Net server side hosting, hot backup, SQL 99 and more. It has all major data access interfaces, as in ODBC, JDBC, ADO .Net and OLE/DB.

Virtuoso has a built-in web server which can serve dynamic web pages written in Virtuoso's web page language as well as PHP, ASP .net and others. This same web server provides SOAP and REST access to Virtuoso stored procedures, supporting a broad set of WS protocols such as WS-Security, WS-Reliable Messaging and others. A BPEL4WS run time is also available as part of Virtuoso's SOA suite.

Virtuoso has a built-in WebDAV repository. This can host static and dynamic web content and optionally provides versioning. The WebDAV repository is tested to interoperate with WebDAV clients built into Windows XP, Mac OSX and others and makes Virtuoso a convenient and secure place for keeping one's files on the net. Further, Virtuoso provides automatic metadata extraction and full text searching for supported content types.

Open Virtuoso supports SPARQL embedded into SQL for querying RDF data stored in Virtuoso's database. SPARQL benefits from low-level support in the engine itself, such as SPARQL aware type casting rules and a dedicated IRI data type. This is the newest and fastest developing area in Virtuoso.

The Initial Open Source Release

Virtuoso can be downloaded at this site in source and binary form for Linux and various Unix platforms. A Windows binary distribution is also available.

Future

Virtuoso is the subject of intensive ongoing development. This is divided into the following areas:

* RDF and Wemantic Web - We will extend the present RDF capability to transparently access native relational data and have more storage configuration options and inferencing support. * Packaging - We will introduce a stripped down database-only configuration of about the same size as other open source DBMS distributions * Applications - We plan to offer a blog, wiki, file sharing and other applications developed and hosted on Virtuoso OpenSource Edition. * Windows build project - Currently Virtuoso OpenSource Edition can be built on most Unix platforms. A separate build system for Win32 and Win64 will be provided as MS Visual Studio projects, complete with Windows binary installers. The commercial release is available for all current Windows operating systems. * Much new developer oriented documentation, concerning extending Virtuoso, hosting non-Virtuoso content, extending DAV, technical articles on using specific areas of functionality.

OWLIM [edit]

OWLIM is what powers PROTON ontology (IST SEKT) http://www.ontotext.com/owlim/OWLIMPres.pdf

OWLIM is a high-performance semantic repository, packaged as a Storage and Inference Layer (SAIL) for the Sesame RDF database. OWLIM uses the TRREE engine to perform RDFS, OWL DLP, and OWL Horst reasoning. The most expressive language supported is a combination of limited OWL Lite and unconstrained RDFS. OWLIM offers configurable reasoning support and performance.

http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies (3 of 5)2006-09-29 08:49:53 Semantic repositories and other basis repository techologies - QVIZ

SwiftOWLIM (the “standard” in-memory version) LGPL http://www.ontotext.com/owlim/index.html commercial version BigOWLIM - high performance & "scalable", rdbms-like - it operates directly with binary persistence files http://www.ontotext.com/owlim/big/index.html

Other sesame OWL reasoners: BOR (also from OntoText) is no longer supported - performance problems http://www.ontotext. com/bor/ A description logic (DL) reasoner that can be integrated into Sesame. BOR is a SHQ(D) reasoner (SHQ(D) is SHOQ (D) without nominals). It provides comprehensive DAML+OIL support and is compliant with the latest OWL specifications

Reasoners [edit]

1) See Sesame custom reasoners. It is common to augment existing reasoners to enable certain features.

2) Pellet (MindSwap) http://www.mindswap.org/

Retrieved from "http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies (4 of 5)2006-09-29 08:49:53 Semantic repositories and other basis repository techologies - QVIZ

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:19, 27 September 2006. ● This page has been accessed 15 times.

http://qviz.humlab.umu.se/index.php/Semantic_repositories_and_other_basis_repository_techologies (5 of 5)2006-09-29 08:49:53 Semantic web services(SWS) and Service oriented architecture (SOA) - QVIZ

Semantic web services(SWS) and Service oriented architecture (SOA)

From QVIZ

(Redirected from Semantic web services (SWS) and Service oriented architecture (SOA)) Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 Future

● 4 Table of Contents

● 5 Concepts

● 6 WSDL

● 7 Web Service Semantics - WSDL-S

[edit] Summary

We investigate the service oriented architecture and contributing topics of Web services, BPEL, semantic web services. Complete SOA frameworks do appear more frequently now that combine web services, BPEL.

Regarding Web services - RESTful services, SOAP, RPC based other. Tools exist to abstract over some low level implementations such as WSIF http://ws.apache.org/wsif/

Background [edit]

● Overview OWL-S, BPEL, Web Services at http://cs.ioc.ee/~tarmo/tsem05/maigre0902-slides. pdf

● Wiki http://en.wikipedia.org/wiki/Service-oriented_architecture

● SOA explained (includes Web services, REST) ❍ What Is Service-Oriented Architecture? http://webservices.xml.com/pub/a/ ws/2003/09/30/soa.html

http://qviz.humlab.umu.se/index.php/Semantic_web_ser...28SWS%29_and_Service_oriented_architecture_%28SOA%29 (1 of 4)2006-09-29 08:49:55 Semantic web services(SWS) and Service oriented architecture (SOA) - QVIZ

● SOA article http://www.xml.com/pub/a/ws/2003/09/30/soa.html

● Good blog that reports SOA and BPEL projects and tools http://swik.net/webservice+BPEL

Future [edit]

Semantic Web Services

Table of Contents [edit]

1. Semantic Web services 2. Service Oriented Architecture (SOA) 3. Restful Services 4. OWL-S and BPEL 5. Rule Related

Concepts [edit]

WSDL [edit]

WSDL (Web Services Description Language) describes Web services as collections of "communication endpoints" or ports, which send and receive messages according to specified protocols, such as HTTP, or SOAP-RPC. WSDL aims to automate communication between Web services by distinguishing such abstract Web service descriptions from the concrete data formats and protocols that are used to implement the Web service. A WSDL binding maps between the abstract description of a Web service and its specific realization [3]. (We focus on WSDL 1.1 here, as WSDL 2.0 is still undergoing revision as of this writing.)

Web services are defined in WSDL as sets of ports, which are essentially network addresses associated with certain protocols and data format specifications. Each port is associated with a port type, which describes the message exchanges (operations) the port can take part in. Four basic kinds of operations are possible (again, in WSDL 1.1): a one-way message, a (two-way) request-response, a (two-way) solicit-response and a (one-way) notification message. Message definitions normally employ XML Schema types and thus support a broad range of type definitions. OWL-S, by contrast, implicitly defines message types (as input/output types of processes) of in terms of OWL classes, which allows for a richer, class-hierarchical semantic foundation underlying the type specifications. Port types are reusable and can be bound to multiple ports [4]. WSDL builds on SOAP by providing a binding for WSDL operations to SOAP messages and WSDL ports to SOAP endpoints.

WSDL assumes a stateless client-server model of synchronous or uncorrelated asynchronous

http://qviz.humlab.umu.se/index.php/Semantic_web_ser...28SWS%29_and_Service_oriented_architecture_%28SOA%29 (2 of 4)2006-09-29 08:49:55 Semantic web services(SWS) and Service oriented architecture (SOA) - QVIZ interactions [7]. OWL-S, by contrast, supports a richer semantic description of Web services beyond their communication interfaces and assumes long-running stateful behaviour of the Web services, specifying, for instance, logical constraints between the input and output parameters of services.

Web Service Semantics - WSDL-S [edit] http://www.w3.org/Submission/WSDL-S/

The current WSDL standard operates at the syntactic level and lacks the semantic expressivity needed to represent the requirements and capabilities of Web Services. Semantics can improve software reuse and discovery, significantly facilitate composition of Web services and enable integration of legacy applications as part of business process integration. The Web Service Semantics document defines a mechanism to associate semantic annotations with Web services that are described using Web Service Description Language (WSDL). It is conceptually based on, but a significant refinement in details of, the original WSDL-S proposal [WSDL-S] from the LSDIS laboratory at the University of Georgia. In this proposal, we assume that formal semantic models relevant to the services already exist. In our approach, these models are maintained outside of WSDL documents and are referenced from the WSDL document via WSDL extensibility elements. The type of semantic information that would be useful in describing a Web Service encompass the concepts defined by the semantic Web community in OWL-S [OWL-S] and other efforts [METEOR-S, WSMO]. The semantic information specified in this document includes definitions of the precondition, input, output and effects of Web service operations. This approach offers multiple advantages over OWL-S. First, users can describe, in an upwardly compatible way, both the semantics and operation level details in WSDL- a language that the developer community is familiar with. Second, by externalizing the semantic domain models, we take an agnostic approach to ontology representation languages. This allows Web service developers to annotate their Web services with their choice of ontology language (such as UML or OWL) unlike in OWL-S. This is significant because the ability to reuse existing domain models expressed in modeling languages like UML can greatly alleviate the need to separately model semantics. Finally, it is relatively easy to update the existing tooling around the WSDL specification to accommodate our incremental approach.

Retrieved from "http://qviz.humlab.umu.se/index.php/Semantic_web_services%28SWS% 29_and_Service_oriented_architecture_%28SOA%29"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

http://qviz.humlab.umu.se/index.php/Semantic_web_ser...28SWS%29_and_Service_oriented_architecture_%28SOA%29 (3 of 4)2006-09-29 08:49:55 Semantic web services(SWS) and Service oriented architecture (SOA) - QVIZ

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:36, 15 September 2006. ● This page has been accessed 13 times.

http://qviz.humlab.umu.se/index.php/Semantic_web_ser...28SWS%29_and_Service_oriented_architecture_%28SOA%29 (4 of 4)2006-09-29 08:49:55 Access Stategies - QVIZ

Access Stategies

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 1. Innovative standards and tools

● 3 1.1 Overview

● 4 1.2 SRU and SRW

● 5 1.3 Central Metadata QVIZ archive as EAD documents

● 6 1.4 OAC: Online Archive of California

[edit] Summary

What interesting access strategies might we exploit?

Access to metadata, to search functionalities. We do not detail Z39.50 access, as this is insufficient for archives.

1. Innovative standards and tools [edit]

1.1 Overview [edit]

Library specific - Library of Congress Information Resource Retrieval Protocols

* Z39.50 - Supports information retrieval among different information systems http://www.loc.gov/z3950/agency/ * SRU/SRW (Search and Retrieve URL/Web Service) - Web services for search and retrieval based on Z39.50 semantics http://www.loc.gov/standards/sru/ * Networked Reference (Question/Answer Transaction Protocol (QATP)) - Supports exchange between digital reference systems collaborating in the processing of a question http://www.loc.gov/standards/netref/ * CQL (Common Query Language) - Formal, user-friendly query language for use between information retrieval systems http://www.loc.gov/standards/sru/cql/

1.2 SRU and SRW [edit] http://www.loc.gov/standards/sru/

SRU is the next generation for libraries, it is used by TEL http://www.europeanlibrary.org A Z39.50 client is required at each institution in order to use SRU.

● Z39.39, SRU at http://www.loc.gov/standards/

http://qviz.humlab.umu.se/index.php/Access_Stategies (1 of 3)2006-09-29 08:49:56 Access Stategies - QVIZ

SRU (Search/Retrieve via URL) is a standard search protocol for Internet search queries, utilizing CQL (Common Query Language), a standard query syntax for representing queries. SRW (Search Retrieve Web Service) is a companion protocol to SRU. The Library of Congress serves as the maintenance agency for these standards.

* SRU: Search/Retrieve Operation * CQL: Common Query Language http://www.loc.gov/standards/sru/cql/ * Explain Operation * Scan Operation * SRW: Search/Retrieve Web Service

1.3 Central Metadata QVIZ archive as EAD documents [edit]

1.4 OAC: Online Archive of California [edit] http://www.oac.cdlib.org/ http://www.oac.cdlib.org/search.findingaid.html

Technical:

● OAC http://www.cdlib.org/inside/projects/oac/tech.html

● CDL METS Repository http://www.cdlib.org/inside/diglib/repository/

Contributor info , metadat formats and guidelines: http://www.cdlib.org/inside/projects/oac/

Digital assets are described using METS, see "administrative related aspects" http://www.loc.gov/standards/mets/ The METS schema is a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library.

The OAC brings together historical materials from a variety of California institutions, including museums, historical societies, and archives. Over 120,000 images; 50,000 pages of documents, letters, and oral histories; and 8,000 guides to collections are available.

Offering easy-to-use search and viewing tools, the OAC organizes images into thematic and institutional collections, such as historical topics, nature, places, and technology. Click on the featured images to learn more or go to our image search page.

Supports EAD and TEI (for text documents).

Software to index, upload, view & search available as BSD license on Sourceforge (java)

Partners contribute selected materials in EAD/ISAD format which is supplemented with admin units and other temporal information, and any addition data needed.

Contributors also provide images... perhaps they are linkable to institution as well.

See UOC site and contributor guidelines.

We have this CDL METS Repository software and it is open source (BSD). However, these are finding aids. In this example, they do not always describe fond, serial, etc. However, EAD is based on ISAD, and this is always possible.

http://qviz.humlab.umu.se/index.php/Access_Stategies (2 of 3)2006-09-29 08:49:56 Access Stategies - QVIZ

Possible to include this option for archives with finding aids also.

Retrieved from "http://qviz.humlab.umu.se/index.php/Access_Stategies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 14:52, 21 September 2006. ● This page has been accessed 16 times.

http://qviz.humlab.umu.se/index.php/Access_Stategies (3 of 3)2006-09-29 08:49:56 Workflow Technologies - QVIZ

Workflow Technologies

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 BEPL

● 4 Tools

● 5 Server Tools

● 6 \ActiveBPEL Engine

● 7 Client tools

● 8 \ActiveBPEL Designer

● 9 "Eclipse BPEL

[edit] Summary

...

Background [edit]

1. Wiki definition & sources 2. http://elementallinks.typepad.com/bmichelson/2005/09/view_bpel_proce.html 3. BEPL and Java

BEPL [edit]

From site: http://www.activebpel.org/info/intro.html

BPEL is an XML language for describing business process behavior based on Web services. The BPEL notation includes flow control, variables, concurrent execution, input and output, transaction scoping/compensation, and error handling.

A BPEL process describes a business process. Processes often invoke Web services to perform functional tasks. A process can be either abstract or executable. Abstract processes are similar to library APIs: they describe what the process can do and its inputs and outputs but do not describe how anything gets done. Abstract processes are useful for describing a business process to another party that wants to use the process. Executable processes do the "heavy lifting" - they contain all of the execution steps that represent a cohesive unit of work.

A process consists of activities connected by links. (A process sometimes only contains one activity but that is usually a container for more activities.) The path taken through the activities and their links is determined by many things, including the values of variables and the evaluation of expressions.

The starting points are called start activities; their createInstance attributes are set to "yes". When a start activity is triggered, a new business process instance is created. From then on, the instance is identified by data called correlation sets. These data uniquely identify a process, but they may change over time. For example, the correlation set for a process may begin as a purchase order number retrieved from a customer order. Later, when an invoice is generated, the correlation set may be the invoice number.

http://qviz.humlab.umu.se/index.php/Workflow_Technologies (1 of 5)2006-09-29 08:49:58 Workflow Technologies - QVIZ

BPEL is layered on top of other Web technologies such as WSDL 1.1, XML Schema 1.0, XPath 1.0, and WS Addressing.

Tools [edit]

1. List of engines

1. http://en.wikipedia.org/wiki/List_of_BPEL_engines

1. \ActiveBPEL Engine—a comprehensive BPEL runtime environment. Written in Java, ActiveBPEL Engine gets distributed as an open-source technology released under the GPL

Free design tool and GPL licensed community BPEL server for Tomcat and other containers

1. Community site: http://www.activebpel.org/ 2. Tutorial for BEPL Engine 3. Commercial site: http://www.active-endpoints.com 4. Design tool for any BEPL server 5. "Tour of design" tool":http://www.active-endpoints.com/products/tour/AWFPro_FlashTour_Slides.htm 6. Samples code: http://www.active-endpoints.com/samples/samples-2/samples.php 2. (not viable) Agila BPEL — an open source implementation of BPEL housed within the Apache Web Server family of products. 1. http://wiki.apache.org/agila/ 3. Eclipse BPEL Project

Server Tools [edit]

\ActiveBPEL Engine [edit]

A comprehensive BPEL runtime environment. Written in Java, ActiveBPEL Engine gets distributed as an open-source technology released under the GPL Free design tool and GPL licensed community BPEL server for Tomcat and other containers

● Community site: http://www.activebpel.org/

● Tutorial for BEPL Engine

● Commercial site: http://www.active-endpoints.com

● Design tool for any BEPL server ● "Tour of design" tool":http://www.active-endpoints.com/products/tour/AWFPro_FlashTour_Slides.htm

● Samples code: http://www.active-endpoints.com/samples/samples-2/samples.php

Client tools [edit]

\ActiveBPEL Designer [edit]

GUI based designer tool - excellent

For any BEPL server

See tutorials and sample code http://www.active-endpoints.com/products/activebpeldes/download.html?sam

http://qviz.humlab.umu.se/index.php/Workflow_Technologies (2 of 5)2006-09-29 08:49:58 Workflow Technologies - QVIZ

Free software

● "Tour of design" tool":http://www.active-endpoints.com/products/tour/AWFPro_FlashTour_Slides.htm

● Samples code useful (SOAP, direct java, complex situations,etc): http://www.active-endpoints.com/samples/samples-2/ samples.php

● http://www.active-endpoints.com/samples/samples-2/all/all.zip

Note:

Under samples link above, there is sample code, since \ActiveBPEL is based on Eclipse, WTP (Web tools project) is accessible! From Eclipse WTP, it is possible to design web services. Very nice.

\ActiveBPEL™ Designer and Eclipse Web Tools Project

The Web Tools Project is an Eclipse plugin that provides an infrastructure to ActiveBPEL Designer and other Eclipse-based development environments targeting Web- enabled applications like BPEL processes. Active Endpoints recommends that you install the Web Tools Project into ActiveBPEL Designer to enhance testing of BPEL processes and development of Web Services Description Language (WSDL) files and schema. This sample demonstrates the how to use some of the tools in WTP, such as the WSDL Editor and XSD-to-XML generator for easy testing of BPEL processes without leaving the Designer environment.

"Eclipse BPEL [edit]

Project":http://www.eclipse.org/bpel/

This is based on Eclipse versions 3.2 and requires miniumum WTP of 1.5M? As of June 30, 2006, Eclipse 3.2 is not released.

Eclipse 3.2 needed ?

Installation: http://www.eclipse.org/bpel/install.php

"Example (zip)":http://www.eclipse.org/bpel/install/SampleProject.zip

Update site: http://download3.eclipse.org/technology/bpel/update-site/

!http://www.eclipse.org/bpel/images/outline.png!

The goal of the BPEL Project is to add comprehensive support to Eclipse for the definition, authoring, editing, deploying, testing and debugging of WS-BPEL 2.0 processes. WS-BPEL (Web Services Business Process Execution Language), or BPEL, is a vendor-neutral specification being developed by OASIS to specify business processes as a set of interactions between web services. By providing these tools, this project aims to build a community around support for BPEL in Eclipse.

The key pieces of functionality that will be provided are:

* Designer. A GEF-based editor that provides a graphical means to author BPEL processes. * Model. An EMF model that represents the WS-BPEL 2.0 specification. * Validation. A validator which operates on the EMF model and produces errors and warnings based on the specification.

http://qviz.humlab.umu.se/index.php/Workflow_Technologies (3 of 5)2006-09-29 08:49:58 Workflow Technologies - QVIZ

* Runtime Framework. An extensible framework which will allow for deployment and execution of BPEL processes from the tools into a BPEL engine. * Debug. A framework which will allow the user to step through the execution of a process, including support for breakpoints.

The implementation will be extensible to third-party vendors in a number of ways. The editor will be extensible to support new activity types, property pages for extensibility of existing constructs, an extensible palette, and product-specific branding capabilities. The runtime deployment framework will be extensible so that third parties may add support for a variety of runtime engines. The model will support extensions to provide new activities or attributes, and the validator will allow for validation of these extensions.

Retrieved from "http://qviz.humlab.umu.se/index.php/Workflow_Technologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

http://qviz.humlab.umu.se/index.php/Workflow_Technologies (4 of 5)2006-09-29 08:49:58 Workflow Technologies - QVIZ

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 4 times.

http://qviz.humlab.umu.se/index.php/Workflow_Technologies (5 of 5)2006-09-29 08:49:58 Semantic web tools - QVIZ

Semantic web tools

From QVIZ

Jump to: navigation, search [edit] Overview

W3C ESW Wiki Page [edit] http://esw.w3.org/topic/SemanticWebTools

From the site:

... contains the information on RDF and OWL tools that used to be listed on the home pages of the RDF and OWL Working Groups at W3C. Keeping such list up-to-date is obviously a problem when the number of Semantic Web tools increases every day. By moving this list to the Wiki, we hope that the community at large will help maintaining these pages

Retrieved from "http://qviz.humlab.umu.se/index.php/Semantic_web_tools"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

http://qviz.humlab.umu.se/index.php/Semantic_web_tools (1 of 2)2006-09-29 08:50:00 Semantic web tools - QVIZ

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 15:28, 27 September 2006. ● This page has been accessed 6 times.

http://qviz.humlab.umu.se/index.php/Semantic_web_tools (2 of 2)2006-09-29 08:50:00 Wiki or combined social software tools - QVIZ

Wiki or combined social software tools

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 Tools

● 4 SemIPort

● 5 Relevant wikis

● 6 XWiki

● 7 Combined social software tools

● 8 SWiK

[edit] Summary

...

Background [edit]

...

Tools [edit]

SemIPort [edit] http://km.aifb.uni-karlsruhe.de/projects/semiport

The SemIPort (Semantic Methods and Tools for Information Portals) project develops innovative methods and tools for creating and maintaining semantic information portals for scientific communities. The methods combine techniques developed in the areas of metadata, knowledge management, knowledge representation, personalization, and data visualization. The methods and tools developed will

● provide an infrastructure that allows researchers to query a semantically structured data repository; ● facilitate the interpretation and management of retrieved information; and ● provide methods for manually or automatically adding annotated informat

Relevant wikis [edit]

XWiki [edit] http://www.xwiki.org/xwiki/bin/view/Main/WebHome

http://qviz.humlab.umu.se/index.php/Wiki_or_combined_social_software_tools (1 of 4)2006-09-29 08:50:02 Wiki or combined social software tools - QVIZ

Java, LGPL

XWiki is a \WikiWiki clone written in Java which supports many popular features of other Wikis like:

* Wiki syntax (uses Radeox engine) * Content management (view/edit/preview/save) * Version Control * Attachments * Rights Management * Full-text Search

XWiki also has many advanced features that many other wiki engines lack:

* Document Templates to ease creation of common documents. * Relational Database storage using Hibernate. * Design Engine for Meta-Data and Forms. * In-place (inline) editing of form information in pages. * Powerful programming API in documents (Velocity or Groovy) * Search API for more detailed searching in the Meta-Data. * Plugin System in Java. * Scalability and Performance using J2EE. * Complete Design Skin System (templates content as well as CSS) have a look to nice websites powered by XWiki * RSS output and display of external RSS feeds * Multi-Lingual capabilities * XML/RPC Remote API * Portlet Integration * Integrated Statistics * PDF Export * WYSIWYG HTML Editing

Combined social software tools [edit]

SWiK [edit]

● http://swik.net

● http://swik.net/blogs

Entries are all editable, they are viewed as either wiki, blog or bookmark list.

QVIZ comment: Interesting, expected this kind of tool, but it does break some current "unofficial rules" of wikis and blogs. Use of categories and folksonomies.

TODO: check if categories are obtained from a folksonomy list.

From the site:

SWiK is a project to help people collaboratively document open-source software.

To do this, you can create template-able SWiK wiki pages: they can act like blogs, or like lists of bookmarks, although by default they are just a simple page you can edit whichever way you want.

http://qviz.humlab.umu.se/index.php/Wiki_or_combined_social_software_tools (2 of 4)2006-09-29 08:50:02 Wiki or combined social software tools - QVIZ

SWiK is a community project with information added by people like you, anyone can edit \SWiK’s wiki pages.

SWiK uses Ajax to make editing easier and faster; try playing around with the editing capabilities in sandbox. Or register and you can try making wiki pages on your own page (click on your name in the upper right)

SWiK uses the Textile markup language to make editing easier than raw HTML. With Textile, you don’t have to type words if you want to make something strong. Instead you can just type strong, which is much more convenient.

Retrieved from "http://qviz.humlab.umu.se/index.php/Wiki_or_combined_social_software_tools"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/Wiki_or_combined_social_software_tools (3 of 4)2006-09-29 08:50:02 Wiki or combined social software tools - QVIZ

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 5 times.

http://qviz.humlab.umu.se/index.php/Wiki_or_combined_social_software_tools (4 of 4)2006-09-29 08:50:02 Blogging tools - QVIZ

Blogging tools

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Pebble

● 3 Roller

● 4 JCR Blog example from Jackrabbit

[edit] Summary

We either grow our own, integrate as a plug-in into an existing Blog software, link to a blog service, or integrate blog software into QVIZ.

Review of blog tools (Best Elearning Blogs)

● (Best Elearning Blogs) http://blog.articulate.com/the-19-best-elearning-blogs/

● German http://www.weiterbildungsblog.de/

Pebble [edit] http://sourceforge.net/projects/pebble

BSD License,

Java, BSD

Many common features, lightweight, XML files stored in file system, authentication

Comments: Consider adapting into QVIZ, but it does use the file system to store XML blog data and store indices.

From the site:

Pebble is a lightweight, open source, Java EE blogging tool. It's small, fast and feature-rich with

http://qviz.humlab.umu.se/index.php/Blogging_tools (1 of 3)2006-09-29 08:50:04 Blogging tools - QVIZ unrivalled ease of installation and use. Blog content is stored as XML files on disk and served up dynamically, so there's no need to install a database

Roller [edit] http://rollerweblogger.org/page/project

Java with Struts, Database (MySql, Postgres)

Feature rich. Multi-user blog. FCKEditor, RSS feeds.

Comments:

One of the best, but not so simple to integrate in QVIZ unless there is a plug-in solution... still, we might adapt another blogging solution.

JCR Blog example from Jackrabbit [edit]

● Overview and Simple model demonstrating Content Repository for Java technology API (JCR). ❍ http://www.artima.com/lejava/articles/contentrepository.html

■ A zip file containing the code example from this article (this is a large file because it also includes the JAR files you will need to run the example): http://www.artima.com/lejava/articles/examples/rabbitblog.zip

Retrieved from "http://qviz.humlab.umu.se/index.php/Blogging_tools"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

http://qviz.humlab.umu.se/index.php/Blogging_tools (2 of 3)2006-09-29 08:50:04 Blogging tools - QVIZ

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:55, 18 September 2006. ● This page has been accessed 5 times.

http://qviz.humlab.umu.se/index.php/Blogging_tools (3 of 3)2006-09-29 08:50:04 Applications for Semantic Communities - QVIZ

Applications for Semantic Communities

From QVIZ

Jump to: navigation, search Contents

● 1 Applications for Semantic Communities

● 2 OpenLink Data Spaces

● 3 Ning - Create and share social apps!

● 4 Google

● 5 DBin - Enabling Semantic Web Communities

[edit] Applications for Semantic Communities

Note: overlap with social bookmarking here.

OpenLink Data Spaces [edit]

See Semantic repositories and other basis repository techologies

Builds on SIOC (Semantically-Interlinked Online Communities) Community and collaboration related standards

It includes modules for wiki, blog, bookmark manager, etc

* ODS Framework (ods dav.vad) * ODS WebBlog? (blog dav.vad) * ODS Briefcase (briefcase dav.vad) * ODS Feed Manager (feeds dav.vad) * ODS Wiki (wiki dav.vad) * ODS Mail (mail dav.vad) * ODS Bookmark Manager (bookmark dav.vad) * ODS Gallery (gallery dav.vad) * ODS Community (community dav.vad)

It seems to use Virtuoso database product (open source)

OpenLink Data Spaces A distributed collaborative application suite aimed at simplifying the creation of points of presence on the web for exposing, exchanging, and creating data. It uses the power of multi-model (Relational and Graph) data management to provide integrated views of data that resides in Blogs, Wikis, Feed Aggregators, Discussion Forums, Bookmark Managers, and other online community application realms. It uses relational data to shared ontology (e.g SIOC, FOAF, and Atom OWL) mapping and an in-built Triple Store (with Virtual Graph capability) to expose its SQL data to SPARQL clients via instance specific SPARQL Query endpoints. It also supports GData and OpenSearch query access to the same data.

Ning - Create and share social apps! [edit]

A means to create sharable social apps and have them hosted

http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities (1 of 5)2006-09-29 08:50:05 Applications for Semantic Communities - QVIZ

Very community oriented

QVIZ: very important. Should QVIZ somehow offer the ability to integrate with selected sharable social applications like in Ning or in Google? http://www.ning.com/

Uses Dojotoolkit,ningbar is a Dojo widget.

Google [edit]

See Google for mail, spreadsheet, calendar, groups, etc

DBin - Enabling Semantic Web Communities [edit] http://www.dbin.org/

Java, Open source GPL There is mention of PHP - see data server scripts

P2P For Windows, \MacOS, Linux

DBin brings the Semantic Web to the end users. By joining P2P groups and communities, users can annotate any topic or subject of interest and enjoy browsing and editing in a semantically rich environment.

FAQ at http://www.dbin.org/w/tiki-index.php?page=DbinFaqs

Publications at http://www.dbin.org/papers.php

PowerPoint

Reusable DBin Components

● RDFGrowth

This API gives a way to attach "context" information to pieces of an RDF model by adding triples to the model itself. This is similar to reification but at a different, coarser, level.

These tools use the concept of MSG (Minimal Self-contained Graph) (1). Given a triple, the MSG that contains it is composed by that triple plus, recursively, for each blank node involved all the triples connected to it. An MSG therefore has a boundary consisting entirely of URIs or literals. An MSG is also the minimum "piece" of an RDF graph that can be can transferred to another peer that still allows the original graph to be incrementally reconstructed.

!http://semedia.deit.univpm.it/img/rdfn.gif!

Reusable tools

● RDFContext Tools

See also RDFSyncro Project at: http://semedia.deit.univpm.it/tiki-index.php?page=RdfSync

http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities (2 of 5)2006-09-29 08:50:05 Applications for Semantic Communities - QVIZ

● "http://sourceforge.net/projects/mpeg7audiodb":\Mpeg7AudioDB

A mpeg-7 based audio database, reads mpeg-7 descriptions (see our twin project MPEG7AUDIOENC) and allows useful database like operations.

● Jasimpa

A firewall traversing, synchronous and asynchronous Java message passing API that's easy to use. Somehow similar to jabber, messages currently go trought the central server, but in the future transparent direct P2P when connections will be established

From Semedia, Italy

DBin Beta Version 0.5 "Semerald"

Available at this time.

DBin Beta Version 0.5 "Semerald"

Not available at this time.

Builds for other platforms (64bits, solaris, motif etc..) will be made available upon request)

RDFGrowth Server

Run this Java server software to create and manage your knowledge exchange groups. Servers can go "public" (and therefore appear automatically in the DBin list of available servers) or be used for private purposes. To connect to one such private server from DBin, use the "add manual server" feature. Some documentation can be found here.

Data Publishing Server

Install this script on your PHP+MySQL server to create your a space for publishing web content within DBin (e.g a picture attachment or your public key). Installing your own publishing service (instead of using our convenience service, will give you the greatest freedom and control over the material you decide to publish. Also very useful for intranet use (e.g. to allow password protected material) Data Publishing Server

From the site:

DBin is general purpose Semantic Web application that enables power users (domain experts) to create "discussion groups" where users annotate any subject of interest (from "beers" as in our example to anything really). At low level, these annotatins are expressed using the languages defined in the Semantic Web initiative (Namely RDF) and the exchanges happen in a P2P model. But the end user doesn't have to be aware of this immediately.

For an end user, DBin is simply a way to express and retrieve knowledge with other fellow users in a much more specific and successful way than what the web usually allows.

DBin is relatively Simple to use and setup! Power users create such "discussion groups" using simple XML based configuration files (or java classes for the most advanced applications). No programming is needed for most applications but to achieve specific integrations with, e.g., existing software or business logic, DBin extensions can be programmed and plugged in as needed.

http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities (3 of 5)2006-09-29 08:50:05 Applications for Semantic Communities - QVIZ

Main features

* Based on the open standards and philosophy of the W3C Semantic Web initiative. Data can be exported and will be interoperable with any other Semantic Web tool. * P2P algorithm (RDFGrowth) designed to cause minimum computational burden to others in the network. (No distributed queries). * Digital Signatures on each annotations keep track of authorships so it is clear who said what. In this sense it can be used to distribute official information and unofficial annotations, they will appair for what they are. * Local storage allows maximally fast operations (no network waiting time, works offline as online). * Local storage means the user can apply filtering rules and trust policies as locally considered appropriate. * Local storage of metadata means that it can be integrated in a single view with information that the user has locally (And doesn't want to give out publically). The result is that join queries can be performed on an integrated view of P2P data, and local data sources such as intranet DBs and user desktop files and resources. * Responsive interface with plenty of integrated tools to search, explore and edit annotations and the data (e.g. pictures, media) attached to it. Metadata editing is guided by the ontologies. * Integrated facilities publish and retrieve data directly to/from Web publishing accounts * Tools for domain experts (not programmers!) to create the environments for the end users, Brainlets, which take care of all the knowledge engineering details and provide well focused functionalities and tools * Open Source under the GNU General License, alternative licenses are available upon request. * Based on the Eclipse Rich Client Platform so: OS native look and feel, multiplatform, expandible with a well known plugin system.

Retrieved from "http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities (4 of 5)2006-09-29 08:50:05 Applications for Semantic Communities - QVIZ

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:26, 27 September 2006. ● This page has been accessed 7 times.

http://qviz.humlab.umu.se/index.php/Applications_for_Semantic_Communities (5 of 5)2006-09-29 08:50:05 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

Browser plug-ins (social bookmarking, blogging, annotation)

From QVIZ

Jump to: navigation, search Contents

● 1 Applications, server, Browser plug-in for social bookmarking

● 2 Popular social bookmarking of interest

● 3 Akarru Social Book Marking Engine

● 4 Scuttle

● 5 CommunityNews

● 6 Frassle Blog Community System

● 7 Scrumptious

● 8 Services

● 9 Diigo - your best companion for online research

● 10 Delicious

[edit] Applications, server, Browser plug-in for social bookmarking

Features we have seen and are interested in.:

● voting ● blogging ● image folksonomy ● social bookmarking ● blogging or textual annotation over social bookmarks, threads of comments on the annotation ● RSS feed ? ● Many tools support services of commerical sites. ● Page annotation via web annotation... highlight text in page (annotation.. how do they do this if page changes??)

Tools can: user drags over text on page and gets a context menu providing options to

● bookmark & highlight, highlight and forward, "blog this", ● search features (against the collected social bookmarks) ● copy feature with or without markup (not sure why need) ● also user must highlight between 5 and 5000 characters;

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (1 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

● visit central site to see/search your bookmarks, blogs or other users; manage them too.

What if text is or include html links?

The first problem is that many are GPL. See non-GPL projects, compare with GPL based ones.

Popular social bookmarking of interest [edit]

We do not include FURL.

See open source projects for social bookmarking, etc.

Akarru Social Book Marking Engine [edit]

Software: http://sourceforge.net/projects/akarru running site: http://trac.blogmemes.com/trac_script

GPL, linux

Akarru is a social bookmarking engine, is used to build social bookmarkings sites, like www. blogmemes.com. Users posts links and promote links to front page using voting system.

Scuttle [edit]

Software: http://sourceforge.net/projects/scuttle

Runnig site: http://scuttle.org/

Comment: what gets bookmark: http://www.bobscube.com/

Web-based social bookmarking system. Allows multiple users to store, share and tag their favourite links online.

Java

GPL

CommunityNews [edit] http://sourceforge.net/projects/communitynews

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (2 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ http://www.communitynewsblog.com/communitynewsproject/

GPL

Last update August 29, 2005 (not very active...)

CommunityNews uses social bookmarking and bayesian techinques to provide periodic postings to blogs. Users can vote for or against RSS sources to increase the chances that the source is used again. Spam filtering (bayesian) is provided by spam bayes.

CommunityNews is a tool designed for small to medium sized blogs. The main concept is that these blogs can not post content as regularly as the larger blogs. A CN user can select RSS feeds from other news sources and blogs and configure CN to select 1 at random on a regular basis. For example, the CommuntiyNewsBlog posts a message once every half hour.

Your users can vote up and down on stories, which increases the usage of the stories source. Also, they can mark a message "as an advertisement", which helps train a bayesian spam filter.

In addition, once votes start registering, a collaborative filter places links to other stories users may be interested in at the bottom of future stories.(So, if I vote "yes" on http://www.foo.bar, future stories will from foo.bar will have up to three links marked as "People Who Liked This Story Also Liked" and up to 3 links marked "People Who Didn't Like This Story Liked:")

A form is also provided for users to suggest new RSS feeds, allowing them the breadth of content to grow as your user base grows.

It can also be used by people like me who want to be able to visit interesting new websites without spending hours browsing the web to find them.

Frassle Blog Community System [edit]

Frassle is no longer being actively developed, but could b e of interest. See running site at http:// frassle.net/ http://frassle.sourceforge.net/ http://sourceforge.net/project/showfiles.php?group_id=118924

Java, last update June 5, 2005

GPL

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (3 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

Frassle is an interpersonal content management and blog system. It is a complete solution for a self- organizing web community, with blog publishing, RSS aggregators, a search engine, social bookmarking, and advanced organizational features.

Scrumptious [edit]

No distributions yet, see CVS

Java

LGPL

Scrumptious is a social bookmarking web application

Services [edit]

Diigo - your best companion for online research [edit]

A service with installable plug-ins. No source code available. Use this a good example and compare with the others mentioned in this list, even the defunct projects.

Comments QVIZ:

● This is one of the best and comprehensive...this is actually what we thought of doing. We can consider a QVIZ plug-in for adding semantic annotation and a connection from the blogger to QVIZ... maybe the annotation server has relevance as well. ● Tools can: user drags over text on page and gets a context menu providing options to

❍ bookmark & highlight, highlight and forward, "blog this", ❍ search features (against the collected social bookmarks) ❍ copy feature with or without markup (not sure why need) ❍ also user must highlight between 5 and 5000 characters; ❍ visit central site to see/search your bookmarks, blogs or other users; manage them too.

It can add annotations as sticky notes to any web page. Other users can blog or comment over these sticky notes. A blog site seems to hold annotated sites and content as blogs. https://addons.mozilla.org/firefox/2792/

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (4 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ http://www.diigo.com/

Examples: http://www.diigo.com/user/irisdd/anniversary-gift?expand=1 vacations: http://www.diigo.com/user/irisdd/laketahoe-trip?expand=1

Screenshots: https://addons.mozilla.org/firefox/2792/previews/

Hightlight & Sticky Note !http://www.diigo.com/cgi-bin/1.py?cmd=3020&_playground=1&url=http:/ www.diigo.com/playground/1.html!

!https://addons.mozilla.org/images/previews/____diigo_- _your_best_companion_for_online_research-2.jpg!

Bookmark to Diigo, Delicious, Furl.. !https://addons.mozilla.org/images/previews/____diigo_- _your_best_companion_for_online_research-1.jpg!

From the site:

1. Highlight, Clip and Sticky-Note for any webpage

* just as you would on paper --> write on any webpage! * make them private or public --> interact on any webpage!

1. Share your online findings with your friends and colleagues

* complete with highlights and sticky notes * as lists, as blogs, as albums, as feeds, or via email

1. Diigo makes it easy to:

* collect and compile your research findings * provide feedback on web design Example * make wishlists Example * plan vacations Example * comparison shopping Example

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (5 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

Several powerful features are combined in the Diigo toolbar to make this a real "power extension" and must-have for anyone who browse a lot of stuffs online.

● The Best Web Annotation Service - add highlights and sticky notes on any web page, anywhere, and access them anywhere

● An All-in-One Bookmarking Tool: bookmark to Diigo, delicious, Simpy, furl, spurl.,,,, and make them permanently cached and full-text searchable

● A Powerful Blogging Platform : Annotate webpages and quickly turn them into blogs with a built-in blog editor or enhanced linkrolls.

● A Great Collaborative Tool: share and interact on online findings, complete with highlights and sticky notes

● The Most Customizable Search Toool: like google's toolbar, but fully customizable, so you can add any other specialty searches - dictionaries, music, movies, references, maps, ....

● Unique Content Selection Menu makes it extremely convenient to interact with every words on a web page - highlight, search, look up - whatever you you want!

Chances are you will find these features all compelling. But if you just want one or several of them, Diigo toolbar can be fully customized to give you just that while taking minimal screen space.

After installing the toolbar, make sure you click "sign-in" on the toolbar to create a free account

Works with: Firefox 1.0 - 2.0 ALL

Delicious [edit] http://del.icio.us/

Common to everyone now.

Use of folksonomies. QVIZ: should we also consider folksomomies for content, images? open API at http://del.icio.us/help/api/

open API, RSS feeds

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (6 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

No sources, just ideas for QVIZ.

Retrieved from "http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking% 2C_blogging%2C_annotation%29"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (7 of 8)2006-09-29 08:50:07 Browser plug-ins (social bookmarking, blogging, annotation) - QVIZ

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:38, 15 September 2006. ● This page has been accessed 6 times.

http://qviz.humlab.umu.se/index.php/Browser_plug-ins_%28social_bookmarking%2C_blogging%2C_annotation%29 (8 of 8)2006-09-29 08:50:07 Semantic wikis - QVIZ

Semantic wikis

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Most relevant publications

● 3 1.0 SOTA listings

● 4 2.0 Relevant products or projects

● 5 2.1 Ikewiki (SRFG)

[edit] Summary

Semantic wikis

Most relevant publications [edit]

● http://www.eswc2006.org/technologies/usb/proceedings-workshops/eswc2006-workshop- semantic-wikis.pdf

❍ See also ontologies mentioned such SWRL, COIN, DILIGENT

1.0 SOTA listings [edit]

● http://wiki.ontoworld.org/index.php/Semantic_Wiki_State_Of_The_Art

2.0 Relevant products or projects [edit]

2.1 Ikewiki (SRFG) [edit] http://ikewiki.salzburgresearch.at

Collaborative tool for knowledge building. Compared to the Semantic wikipedia, the goals are different.

http://qviz.humlab.umu.se/index.php/Semantic_wikis (1 of 3)2006-09-29 08:50:09 Semantic wikis - QVIZ Retrieved from "http://qviz.humlab.umu.se/index.php/Semantic_wikis"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/Semantic_wikis (2 of 3)2006-09-29 08:50:09 Semantic wikis - QVIZ

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 3 times.

http://qviz.humlab.umu.se/index.php/Semantic_wikis (3 of 3)2006-09-29 08:50:09 Other Groupware - QVIZ

Other Groupware

From QVIZ

Jump to: navigation, search [edit] ifolder

As a conceptual model for QVIZ, ifolder is interesting. However it is usable due to O/S dependencies. http://www.ifolder.com

We heard it was base on Fedora Digital repository http://fedora.redhat.com/ (see SOTA wiki), but we have not found that note in the web site documentation.

From the site: iFolder is a simple and secure storage solution that can increase your productivity by enabling you to back up, access and manage your personal files-from anywhere, at any time. Once you have installed iFolder, you simply save your files locally-as you have always done-and iFolder automatically updates the files on a network server and delivers them to the other machines you use.

Sponsored by Novell, the iFolder project is built on the Mono/.Net framework to integrate seamlessly into existing desktop environments.

Retrieved from "http://qviz.humlab.umu.se/index.php/Other_Groupware"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

http://qviz.humlab.umu.se/index.php/Other_Groupware (1 of 2)2006-09-29 08:50:10 Other Groupware - QVIZ

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 08:04, 18 September 2006. ● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/Other_Groupware (2 of 2)2006-09-29 08:50:10 Alogorithms to address scalability, site annotation,etc issues - QVIZ

Alogorithms to address scalability, site annotation,etc issues

From QVIZ

Jump to: navigation, search Contents

● 1 Search and distribution

● 2 TAP

● 3 \RDFGrowth

● 4 \RDFContextTools

[edit] Search and distribution

TAP [edit] http://tap.stanford.edu/tap/ss.html

Search algorithm first looks up graph and chooses additional concepts.

Activity Based Search (ABS) is an application of TAP to search. TAP based results complement traditional search results. Given the search query, Activity Based Search retrieves real-time data relevant to that query from TAP. Internet search engines are primarily targeted at text and not data. Further, the crawl, grab, and index model of search does not work well for searching across dynamically changing sites. ABS uses TAP to overcome these two shortcomings of search.

Users search (the Internet, a particular site, ...) in the context of an activity. Even a very shallow understanding of the potential activities that make sense in the context of a given search can make a dramatic difference in the search experience. We generalize what Google does when the user types in an address (like 2231 Fallen Leaf Ave, Los Altos, CA) into the search box. It identifies that the search term is an address and provides a link to Mapquest for that address, because getting a map is one of the common activities associated with street addresses.

Given the search term, we look up the term in the TAP Knowledge Base. If the term is found in the Knowledge Base (KB), based on the type of the concept it denotes, we determine the kinds of activities that are typically associated with that concept. Based on that, we determine the kinds of

http://qviz.humlab.umu.se/index.php/Alogorithms_to_address_scalability%2C_site_annotation%2Cetc_issues (1 of 4)2006-09-29 08:50:12 Alogorithms to address scalability, site annotation,etc issues - QVIZ data (i.e., property types of the concept) from the global graph that should be used to augment the search results. This data is fetched from the global graph using \GetData and used to augment traditional search results. In the case that the search term has multiple denotations (e.g., "jaguar" could denote the animal or the car), the system selects one and offers the user the ability to choose the other denotation.

Example: Given the search term "Yo-Yo Ma", we figure out that Yo-Yo Ma is a musician. The activities associated with a musician are (retrieving data about) his concert schedule, albums, posters, auctions, ... The system uses TAP to retrieve these pieces of data, which are then used to augment the search results. In this example, the search results are augmented with the data that Yo- Yo Ma is performing in Seattle on 5/12 (from \TicketMaster), that there is an auction for one of his CDs on EBay which ends in 3 minutes, that CDNow has his Appalachian Journey CD on sale for $14.99, ...

!http://tap.stanford.edu/images/image050.jpg!

\RDFGrowth [edit] http://www.dbin.org/rdfgrowth.php

P2P distribution of RDF and query

Server setup

The first beta release of the algorithm has been made available for downlaod as a stand alone library ready to use in Seamntic Web application.

- Read the \RDFGrowth Documentation in the DBin wiki pages

- Download latest release on sourceforge.net

\RDFContextTools [edit]

"\RDFContextTools":http://semedia.deit.univpm.it/tiki-index.php?page=RdfContextTools

This API gives a way to attach "context" information to pieces of an RDF model by adding triples to the model itself. This is similar to reification but at a different, coarser, level.

http://qviz.humlab.umu.se/index.php/Alogorithms_to_address_scalability%2C_site_annotation%2Cetc_issues (2 of 4)2006-09-29 08:50:12 Alogorithms to address scalability, site annotation,etc issues - QVIZ MSG is also the minimum "piece" of an RDF graph that can be can transferred to another peer that still allows the original graph to be incrementally reconstructed.

Retrieved from "http://qviz.humlab.umu.se/index.php/Alogorithms_to_address_scalability% 2C_site_annotation%2Cetc_issues"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

http://qviz.humlab.umu.se/index.php/Alogorithms_to_address_scalability%2C_site_annotation%2Cetc_issues (3 of 4)2006-09-29 08:50:12 Alogorithms to address scalability, site annotation,etc issues - QVIZ

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:40, 15 September 2006. ● This page has been accessed 6 times.

http://qviz.humlab.umu.se/index.php/Alogorithms_to_address_scalability%2C_site_annotation%2Cetc_issues (4 of 4)2006-09-29 08:50:12 Authentication - QVIZ

Authentication

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Overview from wiki sources

● 3 shibboleth

● 4 Guanxi

● 5 AAIportal

[edit] Summary

We are interested in a single sign on solution for servies and applications within QVIZ, and if possible to extend this approach to participating institutions.

This is relevant for services or a mix of AJAX tools that communicate with services or different applications. For example, a web page that communicates with a PHP back-end and java back-end.

Overview from wiki sources [edit]

Single sign-on (SSO) is a specialized form of software authentication that enables a user to authenticate once and gain access to the resources of multiple software systems.

(http://en.wikipedia.org/wiki/Single_sign-on)

Global Login System is a single sign-on open source protocol, designed to allow any user logged in on his account to one of the sites using it, to be authenticated when visiting any other site using it. It aims to be used universally over the Internet, so that each user only needs to have one account with login and pass on one site called his home site, in order to access anything and operate anywhere on the web that he is allowed to. Its difference with other single sign-on systems is that there is no central database of users, so that this system can scale indefinitely by allowing every site of the network to have a separate (hidden) list of users. (http://en. wikipedia.org/wiki/Global_Login_System)

The Liberty Alliance, also known as Project Liberty, is a broad-based industry standards consortium developing suites of specifications defining federated identity management and web services communication protocols. These protocols are suitable for both intra-enterprise and inter-enterprise deployments. The initial Project Liberty specifications were for Federated Single sign-on based on SAML . (http://en.wikipedia.org/wiki/ Liberty_Alliance_Project)

The Global sign on have some software (and homepage) at: http://spoirier.lautre.net/trustedforum.html

Single sign on has a number of products, e.g. a java on at: http://www.ja-sig.org/products/cas/

http://qviz.humlab.umu.se/index.php/Authentication (1 of 5)2006-09-29 08:50:14 Authentication - QVIZ

Something similar, though only for identification purpose, are the openid and LID (Leightweight Identity) projects: http:// openid.net/ (OpenID) http://lid.netmesh.org/wiki/Main_Page (LID)

Note that LID uses OpenID, more information about OpenID can be found at: http://www.openidenabled.com/ http:// iwantmyopenid.org/

OpenID is an open, decentralized, free framework for user-centric digital identity.

OpenID starts with the concept that anyone can identify themselves on the Internet the same way websites do-with a URI (also called a URL or web address). Since URIs are at the very core of Web architecture, they provide a solid foundation for user-centric identity.

The first piece of the OpenID framework is authentication -- how you prove ownership of a URI. Today, websites require usernames and passwords to login, which means that many people use the same password everywhere. With OpenID Authentication (see specs ), your username is your URI, and your password stays safely stored on your OpenID Provider (which you can run yourself, or use a third-party identity provider).

To login to an OpenID-enabled website (even one you've never been to before), just type your OpenID URI. The website will then redirect you to your OpenID Provider to login using whatever credentials it requires. Once authenticated, your OpenID provider will send you back to the website with the necessary credentials to log you in. By using Strong Authentication where needed, the OpenID Framework can be used for all types of transactions, both extending the use of pure single-sign-on as well as the sensitivity of data shared.

Beyond Authentication, the OpenID framework provides the means for users to share other components of their digital identity. By utilizing the emerging OpenID Attribute Exchange specification (see specs ), users are able to clearly control what pieces of information can be shared by their Identity Provider, such as their name, address, or phone number. (http://openid.net/)

LID is a quite simple, but powerful technology that empowers individuals to keep control over and manage their on-line digital identities. LID uses URLs as identifiers, is fully decentralized and supports multiple underlying protocols such as OpenID , Yadis and PGP/GPG. LID functionality can be easily added to a URL that you own already, such as your blog. It's also very simple, interoperable, extensible, and secure. It is the original URL-based User-centric Digital Identity technology. (http://lid.netmesh.org/wiki/Main_Page)

The problem with all these systems is that every server using it has to utilize some tool which can handle it. This would be a requirement for the archives, with global sign on (and I assume also for single sing on) they would have to have a list of users from QVIZ which are allowed to access the archive along with a key of some sort to ascertain the authenticity of the user.

shibboleth [edit]

An important and widely used solution. We might also find products that create more features and access for the project.

"Shibboleth (Internet2)":http://en.wikipedia.org/wiki/Shibboleth_%28Internet2%29 http://shibboleth.internet2.edu/

http://qviz.humlab.umu.se/index.php/Authentication (2 of 5)2006-09-29 08:50:14 Authentication - QVIZ

Based on OASIS SAML v1.1

From the site:

The Shibboleth software implements the OASIS SAML v1.1 specification, providing a federated Single-\SignOn and attribute exchange framework. Shibboleth also provides extended privacy functionality allowing the browser user and their home site to control the Attribute information being released to each Service Provider. Using Shibboleth-enabled access simplifies management of identity and access permissions for both Identity and Service Providers. Shibboleth is developed in an open and participatory environment, is freely available, and is released under the Apache Software License. The Shibboleth Roadmap and timeline are available here. Detailed information about Shibboleth is available here.

Downloads

Identity Provider Software

* Java Source with Ant-based Installer (GPG) * Extensions o Federal E-Authentication Credential Service: An extension allowing a Shibboleth 1.3 IdP to operate as a Federal E-Authentication Credential Service. o ADFS Integration: An extension allowing a Shibboleth 1.3 IdP to integrate with Microsoft's Active Directory Federation Service. o \GridShib: A project funded by the NSF Middleware Initiative (NMI) to combine Grid Security Infrastructure in the Globus Toolkit with Shibboleth. o HA-Shib: An extension for the Shibboleth 1.3 IdP that allows multiple IdP instances to be clustered together and share in-memory state for handle and artifact mapping.

Service Provider v1.3e Software

* Fedora Linux i386 RPMs * Red Hat Enterprise Linux i386 RPMs * Red Hat Enterprise Linux x86_64 RPMs * Source RPMs * Solaris Packages (Sparc, 2.8, Sun CC) * Windows Installer (GPG) (Post-Install ZIP) * Mac OS-X 10.4 (GPG) (expands to opt/shibboleth-sp) * C++ Source (GPG) (additional dependencies required)

General Notes

* Source, binaries, and some dependencies are available from http://shibboleth. internet2.edu/downloads/ * You can verify the integrity of signed files using PGP or GPG and these KEYS. * Documentation on installing, configuring, and testing Shibboleth is available on the support page. Information is available describing how to install, configure, and test the Shibboleth software. * The source is available from our anonymous CVS repository. * Older releases and dependencies can be found in http://shibboleth.internet2.edu/ downloads/archive/ * Shibboleth Trademark Guidelines and Styleguide

[edit]

http://qviz.humlab.umu.se/index.php/Authentication (3 of 5)2006-09-29 08:50:14 Authentication - QVIZ Guanxi http://sourceforge.net/projects/guanxi java, license??

Guanxi is a JAVA implementation of the SAML Spec and complies with the Shibboleth Profile extensions developed as part of an Internet2 project. Guanxi's main purpose is to faciliate inter-institutional Authentication/Authorization/and Accounting services.

AAIportal [edit] http://aai-portal.sourceforge.net/ http://sourceforge.net/projects/aai-portal

Screenshots: http://sourceforge.net/project/screenshots.php?group_id=91483

Wiki: http://www.guanxi.uhi.ac.uk/index.php/Guanxi

PHP, GPL

The \AAIportal is a web portal written in PHP. It is a broker between the \SWITCHaai (based on the Shibboleth middleware) and many e-learning platforms. Adapters are available for \WebCT CE 4 and 6, \WebCT Vista, VITELS, \AdLearn, ...

Retrieved from "http://qviz.humlab.umu.se/index.php/Authentication"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

http://qviz.humlab.umu.se/index.php/Authentication (4 of 5)2006-09-29 08:50:14 Authentication - QVIZ

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 6 times.

http://qviz.humlab.umu.se/index.php/Authentication (5 of 5)2006-09-29 08:50:14 Persistent Object Identifier Technologies - QVIZ

Persistent Object Identifier Technologies

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 DOI

● 3 \OpenURL

● 4 OCLC \OpenURL Tools

● 5 Archival Resource Key (ARK)

[edit] Summary

We should offer some DOI or \OpenUrl services to access resources. It is a question what to expect from institutions also.

DOI [edit]

...

\OpenURL [edit]

A superior means to retrieve resources depending on user and user's local institution dependencies or offerings. Ability to find one resource among many copies.

Supported by many applications. See DSPACE

OCLC \OpenURL Tools [edit] http://www.oclc.org/research/software/openurl/default.htm http://alcme.oclc.org/openurldemo/dist.html

Apache license

The open-source \OpenURL 1.0 distributions consist of a jar file and a Java Servlet web application ("war" file) providing \OpenURL 1.0 resolution capability. The default installation demonstrates its application by echoing OpenURL requests formatted in HTML. In practice, though, this service can be configured to support any context-sensitive service within the confines of the \OpenURL 1.0 protocol.

Archival Resource Key (ARK) [edit] http://www.cdlib.org/inside/diglib/ark/

Used by CDL for example: See CDL METS Repository http://www.cdlib.org/inside/diglib/repository/

Objects in the repository are assigned persistent identifiers according to a naming scheme called the Archival Resource Key

http://qviz.humlab.umu.se/index.php/Persistent_Object_Identifier_Technologies (1 of 4)2006-09-29 08:50:16 Persistent Object Identifier Technologies - QVIZ

(ARK). The ARK scheme was developed at the National Library of Medicine and is currently in production use at the CDL.

The Archival Resource Key (ARK) identifier is a naming scheme for persistent access to digital objects (including images, texts, data sets, and finding aids), currently being tested and implemented by the California Digital Library (CDL) for collections that it manages.

An identifier is an association between a string (a sequence of characters) and an information resource. That association is made manifest by a record (in the case of this service, a METS record ) that binds the identifier string to a set of identifying resource characteristics. The ARK identifier is a specially constructed, globally unique, actionable URL. Each ARK links end-users to three things:

* Digital object metadata * Digital object content files * A commitment statement made by the CDL concerning the digital object.

Entering the ARK in a web browser produces an object. Entering the ARK followed by a single question mark ("?") produces the metadata only. Entering the ARK followed by a double question mark ("??") produces a CDL commitment statement. At this time the CDL commitment statement is in development and under final review.

An ARK is represented by a sequence of characters (a string) that contains the label, "ark:", optionally preceded by the beginning part of a URL. The URL, or the "Name Mapping Authority Hostport" (NMAH), is mutable and replaceable. The immutable, globally unique identifier follows the "ark:" label. This includes the "Name Assigning Authority Number" (NAAN) for the CDL, followed by the name that CDL assigned.

Here is a diagrammed example:

The ARK syntax can be summarized, The ARK syntax can be summarized,

[1]ark:/NAAN/Name[Qualifier] where the NMAH part is in brackets to indicate that it is optional and replaceable. The immutable, globally unique, core identity follows the "ark:" label. Assignment and Support Policy Statements

The CDL assigns identifiers within the ARK domain, 13030 (California Digital Library), according to the following principles:

* No ARK shall be re-assigned; that is, once an ARK-to-object binding has been published, that binding shall be considered unique into the indefinite future. * To help them age and travel well, CDL-assigned ARKs shall contain no widely recognizable semantic information (to the extent possible). * CDL-assigned ARKs shall be generated with a terminal check character that guarantees them against single character errors and transposition errors.

The CDL commitment statement is in development and under review. While the CDL will ultimately honor its commitment, some change is still possible. First, managing a digital object may require altering it as appropriate to ensure its stability. Second, the declared level of commitment may change as the requirements and policies for persistence become better

http://qviz.humlab.umu.se/index.php/Persistent_Object_Identifier_Technologies (2 of 4)2006-09-29 08:50:16 Persistent Object Identifier Technologies - QVIZ understood over time, and as the CDL implements procedures for maintaining those commitments and associating them with the objects that it manages.

Some CDL collections mirror parts of collections at external institutions. At this time, CDL collections are not mirrored in any external preservation repositories. Generating ARKs

Any institution may obtain a NAAN (identifying an ARK domain) and begin minting ARKs. To generate ARKs, you may use any software producing identifiers that conform to the ARK specification, referenced below. CDL uses the open-source "noid" (nice opaque identifiers) software, also referenced below, which creates minters and accepts commands that operate them. In addition to generating identifiers, a noid minter can bind arbitrary metadata to identifiers with individual stored values or rule-based values, and it comes with instructions for setting up a URL interface and a name resolver.

For ARKs under the CDL's NAAN (13030), whether minted by the CDL or by an institution submitting objects to the CDL, there are three generating methods:

* Utilize the CDL-based Noid minter interface to generate one ARK at a time or a block of ARKs at a time. * Manage a local instance of a Noid minter to generate ARKs directly. * Request that the CDL supply ARKs to digital assets upon ingest; in this case the institution is not responsible for encoding and transmitting ARKs when submitting objects to the CDL.

Retrieved from "http://qviz.humlab.umu.se/index.php/Persistent_Object_Identifier_Technologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Persistent_Object_Identifier_Technologies (3 of 4)2006-09-29 08:50:16 Persistent Object Identifier Technologies - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 3 times.

http://qviz.humlab.umu.se/index.php/Persistent_Object_Identifier_Technologies (4 of 4)2006-09-29 08:50:16 Technologies for Rich Internet Applications - QVIZ

Technologies for Rich Internet Applications

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Javascript libraries

● 3 Cometd

● 4 Cross Domain XMLHttpRequests using an IFrame Proxy

● 5 DOM Content Loaded (onLoad)

● 6 vector 2D APIs

● 7 JSON-RPC

● 8 AJAX Toolkits

● 9 dojo toolkit

● 10 ZK (XUL and AJAX)

● 11 cforms?

● 12 Flash AJAX tools

● 13 Supplementary tools

● 14 User Interface (move to visualisation)!!

● 15 RSS support

[edit] Summary

...

Javascript libraries [edit]

● jQuery *

● http://jquery.com/

● http://codylindley.com/blogstuff/js/jquery/ jQuery is a Javascript library that takes this motto to heart: Writing Javascript code should be fun. jQuery achieves this goal by taking common, repetitive, tasks, stripping out all the unnecessary markup, and leaving them short, smart and understandable.

Cometd [edit] http://www.cometd.com/

"Cometd support is found in the Dojo Toolkit in the dojo.io.cometd package, found in current nightly builds and in Subversion.

http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications (1 of 5)2006-09-29 08:50:17 Technologies for Rich Internet Applications - QVIZ

Cometd is a scalable HTTP-based event routing bus that uses a push technology pattern known as Comet. The term 'Comet' was coined by Alex Russell in his post 'Comet: Low Latency Data for the Browser'. The letter d is for 'Daemon', as described by Answers.com, Daemon is a program or process that sits idly in the background until it is invoked to perform its task. Cometd consists of a protocol spec called Bayeux, javacript libraries (dojo toolkit), and an event server."

Cross Domain XMLHttpRequests using an IFrame Proxy [edit]

As of today, the Dojo codebase can do cross domain XMLHttpRequests (XHR) using an iframe proxy.

DOM Content Loaded (onLoad) [edit]

From the Dojo blogspace:

"DOMContentLoaded now the onload event for Dojo

This last weekend I finally implemented Dean Edwards’ DOMContentLoaded (with Matthias Miller and John Resig) solution for the dojo.addOnLoad event, as opposed to using the window.onload event to fire all initialization…and so far (with the exception of some minor side effects, notably with widgets that use images for layout) it is working very well–and the bottleneck of initial load performance (you know, where the page seems to take forever to load) has been markedly improved." http://dean.edwards.name/weblog/2006/06/again/

"For those who think that this is not a real issue, consider the following scenario. You have a cute web app called www. TickleMyKittens.com. Of course, it uses Ajax, Comet and Domestos to provide a super-slick interface, this is 2006 after all. But your site is full of kitty images many of which are hosted on a server beyond your control. Your interface is not active until all of those kitties have downloaded. You try to drag a kitty to the litter but she’s just not moving. The page has loaded, what gives? That my friend, is the window.onload problem. The onload event waits for all binary content to download before firing. No kitty-tickilng until then."

vector 2D APIs [edit]

No Flash, Interactive browser graphics

● http://www.sitepoint.com/blogs/2006/07/29/oscon-2006-no-flash-required-interactive-browser-graphics/

JSON-RPC [edit] http://oss.metaparadigm.com/jsonrpc/

JSON-RPC-Java is a key piece of Java web application middleware that allows JavaScript DHTML web applications to call remote methods in a Java Application Server without the need for page reloading (now refered to as AJAX). It enables a new breed of fast and highly dynamic enterprise Web 2.0 applications (using similar techniques to Gmail and Google Suggests).

http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications (2 of 5)2006-09-29 08:50:17 Technologies for Rich Internet Applications - QVIZ

AJAX Toolkits [edit]

● JSEclipse *

JSEclipse to the list of authoring tools that support Dojo. The JSEclipse integration appears to be particularly complete, as it includes auto-completion for Dojo APIs. dojo toolkit [edit] http://www.dojotoolkit.org

ZK (XUL and AJAX) [edit] http://ajaxpatterns.org/XUL_Ajax_Frameworks

LGPL

XUL and AJAX together...

See XUL resources at http://www.xulplanet.com/

See editor http://xulplanet.com/downloads/xabyl/

cforms? [edit] todo

Flash AJAX tools [edit]

...

Supplementary tools [edit]

User Interface (move to visualisation)!! [edit] http://tango.freedesktop.org/Tango_Desktop_Project

● Icon gallery: http://tango.freedesktop.org/Tango_Icon_Gallery

● Style guidelines: http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines

Icons are free to use, the icon spec is GPL

http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications (3 of 5)2006-09-29 08:50:17 Technologies for Rich Internet Applications - QVIZ

From the site:

The Tango Desktop Project exists to help create a consistent graphical user interface experience for free and Open Source software.

While the look and feel of an application is determined by many individual components, some organization is necessary in order to unify the appearance and structure of individual icon sets used within those components.

The Tango Desktop Project defines an icon style guideline to which artists and designers can adhere. Work has begun with the creation of a new icon theme based upon a standardized icon naming specification. In addition, the project provides transitional utilities to assist in creating icon themes for existing desktop environments, such as GNOME and KDE.

Eventually, the Tango Desktop Project will provide the following initiatives:

* A suggested default native look. * A subsystem to help standardize toolkits on a common icon naming structure. * A complete set of application, mimetype, and stock icons designed using a defined style guide. * A general, cross-desktop human interface guideline.

One of the major components in establishing a look and feel for the desktop is the icon theme. This page describes the proposed standardisation of icon names to use when creating icon themes for desktops and applications which implement the freedesktop.org Icon Naming Specification. This proposed Icon Naming Specification complements the existing freedesktop.org Icon Theme Specification. (docbook2html can be used to convert the xml to a more readable form).

The Tango icons are licensed under the Creative Commons Attribution Share-Alike license. The palette is public domain, it can be used and distributed freely. Developers, feel free to ship it along with your application. The icon naming utilities are licensed under the GPL

RSS support [edit]

● MagpieRSS http://swik.net/MagpieRSS

== Miscellaneous==

● GNU Diff

● codezoo

Retrieved from "http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications"

Views

● Article

● Discussion

● Edit

http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications (4 of 5)2006-09-29 08:50:17 Technologies for Rich Internet Applications - QVIZ

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 10:06, 18 September 2006. ● This page has been accessed 12 times.

http://qviz.humlab.umu.se/index.php/Technologies_for_Rich_Internet_Applications (5 of 5)2006-09-29 08:50:17 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

Technologies for Collaboration and Presentation in Rich Internet Applications

From QVIZ

Jump to: navigation, search

TODO:

● Help: We also need any tools for manipulating or enhancing objects or their matadata through Flash. (QVIZ GIS Maps)

Contents

● 1 Summary

● 2 Collaborative services

● 3 Google

● 4 \AjaxXLS

● 5 Dojotoolkit and widgets

● 6 Ning - Create and share social apps!

● 7 Sharing/collaborating over Worksheet objects

● 8 SERVICE: Google worksheets

● 9 SERVICE: \AjaxXLS and other Ajax services

● 10 Interesting Collaborative Applications besides Google

[edit] Summary

Intially, we decided to bring a means for users to assemble content and data. A "semantic" collaborative worksheet was the vision and we expected that during the project more tools would become available to support different types of objects using rich internet application technologies such as AJAX.

In this section, we track tools to support (please update list)

● collaboration over worksheet objects that user(s) can contribute data from archival materials (perhaps even extract automatically from an HTML table (later), but for now where users manually assemble their extracted data and can label AND insertsemantic annotations on columns, rows, cells, perhaps groups of rows and columns. We would require also additional vocabularies that the user community could grow that are appropriate to worksheet applications.

Worksheets can themselves contain other data objects and we will need to provide first only a basic functionality, but later more advanced tools for authoring these kinds of collaborative archival objects.

In most applications, Google or \AjaxXLS (using XUL ), users can upload their Word based worksheets, we must investigate the OpenOffice support.

Can we offer both Google and other solutions... in future, yes, but the issue is really that we should not reinvent all possible collaborative features when other free services are available. Our issue is reuability, but we would be critised on the issue of vendor-lockin.

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (1 of 6)2006-09-29 08:50:19 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

QVIZ Comments

Ajax services are now a strong business model, but how can we offer flexible, but lighter weight semantic objects that might be edited with certain Ajax editor components e.g. Custom DOJO editor that edits objects appropriately. To offer basic features for worksheet, we might just simple exploit Ajax editors to enable worksheet building using CSS and HTML or XML. CSS is required to prevent HTML table lockin. Semantic annotation features are then considered based on user requirements. The editor would recogise that this type of page object (perhaps commented) should only be edited by a particular AJAX editor component.

QVIZ comments: Google services and APIs

It is very tempting to build a strong relationship to the Google platform in order to utilise the collaboration capabilities and to enable developers to bring new features to their users of Google.

An example are the email groups and collaboration, calendar and google collaborative worksheet.

Requires GMail account. Users will need to invite each other within a community in order to user these. See tutorials and examples.

Collaboration features we have seen in one commerial product (\JotSpot)

● Blog ● Forum ● Group Calendar ● Meeting Manager ● Photo Gallery ● Simple Poll ● Personal To-Do Lists

Business Productivity

● Spreadsheets ● Project Manager ● Bug Reporter ● Company Directory ● Knowledge Base ● Contact Manager ● Recruiting ● Call Log Manager

Collaborative services [edit]

Google [edit]

A large number of tools that offer developers APIs to futher customise the tools for their customers. http://labs.google.com/

Examples relevant to QVIZ

● GMail ● Google maps ● Groups ● Sets - share sets of items - interesting idea for QVIZ

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (2 of 6)2006-09-29 08:50:19 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

...

\AjaxXLS [edit]

...

Dojotoolkit and widgets [edit]

Dojotoolkit overview and CheatSheet: http://www.get-the-answer.info/files/DojoWidgetOverview.pdf http://blog.dojotoolkit.org/

CheatSheet blog http://blog.dojotoolkit.org/2006/06/25/widget-property-cheat-sheat

Ning - Create and share social apps! [edit]

A means to create sharable social apps and have them hosted

Very community oriented

QVIZ: very important http://www.ning.com/

Uses Dojotoolkit,ningbar is a Dojo widget.

Sharing/collaborating over Worksheet objects [edit]

SERVICE: Google worksheets [edit]

Users can create new or upload spreadsheets as well as save them in .xls or .csv format. Users might then invite users to share this worksheet by "inviting" other GMail users.

Introduction: http://www.google.com/googlespreadsheets/tour2.html

Good blog description

Screenshot:

Image:SpreadsheetGoo.jpg

!http://www.j2eegeek.com/blog/2006/06/06/google-hits-a-home-run-with-google-spreadsheet/!

!http://static.flickr.com/65/161696902_92c49a4ed2_o.png!

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (3 of 6)2006-09-29 08:50:19 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

Other resources:

Blog 1

SERVICE: \AjaxXLS and other Ajax services [edit] http://www.ajaxxls.com/

Company offers Ajax tools as services where users can insert links into their pages to make them sharable such as \AjaxXLS or \ajaxTunes.

A list of ajax services.

● ajaxWrite ● ajaxSketch ● eyespot ● ajaxXLS (worksheet sharing) ● ajaxTunes ● ajaxOS

Issue: support for Microsoft Excel, but what about \OpenOffice?

Examples:

!http://res.sys-con.com/story/apr06/208038/ajaxXLS_0.05.jpg!

Examples of how to link to their services to share a user's objects

Requires "player" plug-in (currently Firefox, but IE is likely possible)

Editor is still in development.

From the site: ajaxXLS Viewer is a web-based spreadsheet viewer that allows you to easily open any . xls file within your Firefox browser. Compatibility with Microsoft Excel and OpenOffice allows ajaxXLS to preserve all your common cell formatting categories such as text styles, decimals, currencies, dates, and times as well as formulas, backgrounds and borders from the original documents.

The ajaxXLS web-based editor is still in the early stages of development. With it you can write, edit and save standard spreadsheet files to your local machine. If you would like to try the sneak peak pre-release version of the ajaxXLS editor, please visit the link below.

From http://www.ajaxlaunch.com/support/launch_codes.html

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (4 of 6)2006-09-29 08:50:19 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

For ajaxXLS:

Insert the following code into your website's code to provide a link for people to view your spreadsheet file using ajaxXLS. Replace the URL after "doc=" with the address to your publicly available spreadsheet file.

For USA: Launch ajaxXLS

For International: Launch ajaxXLS

From article

The line between online and offline software continues to blur as Michael Robertson’s latest Web-based software release, \AjaxXLS, hit the streets recently. Ostensibly an Ajax application, \AjaxXLS is a XUL-based Web application that can display virtually any Excel spreadsheet with ease, providing an easily used viewer available to anyone with an available Internet connection. Even the spreadsheets created with the most recent version of Excel are supported.

Robertson claims that \AjaxXLS is the very first free service on the Web that allows people to open up and view any Microsoft Excel document. This is certainly represents a useful public service given the ubiquity of Excel spreadsheets in daily e-mail these days.

Interesting Collaborative Applications besides Google [edit]

● JotSpot

● Writely - The Web Word Processor

Writely moves to the Google systems and registration is closed temporarily!

❍ Share documents instantly & collaborate real-time. ❍ Pick exactly who can access your documents. ❍ Edit your documents from anywhere. ❍ Nothing to download -- your browser is all you need. ❍ Store your documents securely online. ❍ Offsite storage plus data backup every 10 seconds. ❍ Easy to use. ❍ Clean, uncluttered screens with a familiar, desktop feel.

Retrieved from "http://qviz.humlab.umu.se/index.php/ Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications"

Views

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (5 of 6)2006-09-29 08:50:19 Technologies for Collaboration and Presentation in Rich Internet Applications - QVIZ

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 3 times.

http://qviz.humlab.umu.se/index.php/Technologies_for_Collaboration_and_Presentation_in_Rich_Internet_Applications (6 of 6)2006-09-29 08:50:19 AJAX and FLASH Together - QVIZ

AJAX and FLASH Together

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Relvevant discussions

● 3 FLASH and AJAX?

● 4 Discussion from 2005

[edit] Summary

There is a debate of using AJAX or FLASH technologies, and integration with client side javascript. We look in this section to materials (blogs, examples, tools, any info sources) that will help us with this topic because QVIZ is interested in FLASH based GIS visualisation and there will also be AJAX incorporated into the UIs as well.

Relvevant discussions [edit]

FLASH and AJAX? [edit]

Products or solutions

● AJAX + Flash = AFLAX ❍ Blog: http://digg.com/design/AJAX_Flash_=_AFLAX

❍ Ajaxian blog: http://www.ajaxian.com/archives/2005/11

● http://ajaxian.com/by/topic/flash/

● Flexstore ❍ http://ajaxian.com/archives/flexstore-flash-ajax-rails

● Flex ❍ Adobe Flex-Ajax bridge

● Better Flash Features for javascript: We Ajaxians have long talked about using Flash / Flex to create components for use within Ajax applications, and this new Flex-saavy bridge makes this scenario that much easier. Now that Flash 8.5 introduces a Just-In-Time compiling ECMAScript engine under the covers, technology that makes it seamless to utilize this runtime environment from within the slower interpreted browser environment is very interesting.

http://qviz.humlab.umu.se/index.php/AJAX_and_FLASH_Together (1 of 3)2006-09-29 08:50:21 AJAX and FLASH Together - QVIZ

Other

● SwfJax

\SwfJax is a new approach to asynchronous \JavaScript and XML applications using revolutionary Flash technology.

\SwfJax uses a lightweight SWF (Adobe's Small Web Format or simply - Flash) engine to get XML data from the server and \xPath (XML Path Language) to address a part of data it has retrieved. Data can be returned back to Javascript as an Array. You can also send multiple \xPath queries at once.

Discussion from 2005 [edit] http://radar.oreilly.com/archives/2005/05/flash_is_ajax_o.html

One of the more interesting debates at the Ajax Summit this week concerned Flash and its relationship to or inclusion in Ajax. The discussion was more interesting because of the Flash demo that Kevin Lynch (CTO of Macromedia, the makers of Flash) gave on the first day -- and maybe also simply because he was there at the table.

Kevin's demo showed a [1] interacting with \JavaScript on a web page -- both while initially loading and later, after receiving input from the user on the page (outside of the Flash movie). .... "wrote up some of the details of this" Flash graphing application.

Retrieved from "http://qviz.humlab.umu.se/index.php/AJAX_and_FLASH_Together"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

http://qviz.humlab.umu.se/index.php/AJAX_and_FLASH_Together (2 of 3)2006-09-29 08:50:21 AJAX and FLASH Together - QVIZ

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 06:21, 15 September 2006. ● This page has been accessed 11 times.

http://qviz.humlab.umu.se/index.php/AJAX_and_FLASH_Together (3 of 3)2006-09-29 08:50:21 Visualisation and Knowledge - QVIZ

Visualisation and Knowledge

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Faceted Browsing

● 3 RDF Graph Visualisation

● 4 Force Directed Graphs

● 5 FOAFMap

● 6 Fresnel RDF Display Technologies

● 7 Browser applications demonstrating visualisation

● 8 Horus

● 9 SMILE Projects

● 10 Comprehensive Tools, Frameworks

● 11 mSpace Framework Software

● 12 Another custom example with Google maps:

● 13 Archives Thesauri - example visualisation in thesauri

● 14 UKAT - UK Archive Thesaurus

[edit] Summary

Focus is on tools that we might resuse and/or user interfaces that help us capture requirements.

Faceted Browsing [edit]

Useful for semantic web

● Definitions http://en.wikipedia.org/wiki/Faceted_navigation

● Simile project Longwell http://simile.mit.edu/wiki2/Longwell_User_Guide

● Use of Faceted Classification http://www.webdesignpractices.com/navigation/facets.html

● Faceted Classification of Information http://www.kmconnection.com/DOC100100.htm

● Use of Faceted Classification http://www.digital-web.com/news/2004/09/use_of_faceted_classification/

● The Flamenco Search Interface Project http://flamenco.berkeley.edu/

● http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (1 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ

From Longwell:

Image:Longwell facets

The most important aspect of Longwell is the faceted browsing UI paradigm.

A facet is a particular metadata field that is considered important for the dataset you are browsing. Longwell can be configured to prioritize which facets are 'open' when the page loads and in what order, an/or it can analyze facets and choose heuristically which are most important and should be 'opened.'

Once the facets are selected for a specific dataset, Longwell starts processing the dataset and extracts a list of facets, their values, and the number of times each facet value occurs in the dataset. This is shown in the right hand side, where each facet is boxed independently. Clicking on the facet's title will toggle it open or closed.

Image:Screenshot of a Facet Box http://simile.mit.edu/wiki2/Image:Longwell_Facet_Box.png

Clicking on a facet value guides Longwell to add a facet restriction and display only the items that fulfill all restrictions. The facet pane on the right is also updated, showing the facets and values that are available in the resulting sub-dataset for further drill-down.

When no more facet restrictions are possible, the right pane will be empty.

Browsing by adding restrictions in the right pane has the effect of "zooming in" the dataset by locally removing from the view anything that's not of interest at that particular time. The user also has the ability to "zoom out" by removing a restriction that was previously selected (in the top left section).

Image:Screenshot of Restrictions http://simile.mit.edu/wiki2/Image:Longwell_Facet_Box.png

The result of the restriction is a subset of the items available in the dataset (what is considered "an item" is also a configurable property of Longwell). Longwell can also be configured to display particular properties of the items in various ways, and, mixing with CSS stylesheets, it is possible to obtain pleasant presentations of them without having to modify Longwell's source code. See the section below for more info on this.

Longwell also gives the ability to perform a "free text" restriction that reduces the browsed dataset to all items that contain the searched string in their properties' values. This restriction is triggered by entering text in the input box above the facet list.

From XTF experimental features: http://xtf.sourceforge.net/WebDocs/HTML/XTF_Experimental_Features/XTFExperimental.html#Faceted_Browsing

CrossQuery provides a good general-purpose solution for searching a large collection of documents. However, until now it has not provided a convenient or useful way to browse such a collection. In other words, a user who isn't quite sure what subject they're looking for, or who wants to get an idea of what is offered by the collection, would have a difficult time using just queries.

There are many possible ways to build a browsing system. CDL has chosen to explore faceted browsing, a promising method of intuitively exploring a collection that has rich meta-data. If one thinks of the collection as a bag of jewels, each meta-data field is a "facet", and items will have various values for that facet. The user can choose to explore one or many facets simultaneously.

A good example of a faceted browse system was developed by Prof. Marti Hearst at UC Berkeley. The system is called Flamenco, and the web site is quite informative and includes a good http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (2 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ demonstration. For more information the reader is encouraged to play with and read about Flamenco.

XTF's experimental browse feature has been added to the crossQuery servlet. One might ask whether it should have been a separate servlet altogether, but there is a good reason to have search and browse in the same servlet: it can be quite useful to combine the two activities. For instance, a user might enter a search for "africa", and then use the browse system to get an idea of the collection's coverage, in terms of dates (the interface might include decades and a count of documents for each one), subjects, authors, etc.

RDF Graph Visualisation [edit]

Force Directed Graphs [edit]

Force Directed Graphs based on a javascript library (no Java!)

● http://www.kylescholz.com/blog/2006/06/using_force_directed_graphs.html

● http://www.kylescholz.com/blog/2006/06/force_directed_graphs_performa.html#more

● blog item http://www.kylescholz.com/blog/2006/06/force_directed_graphs_performa.html

From the site:

"... alternative to the traditional list and tree views used in search result user interfaces ..... display tools that can show relationships among results, rather than simply ranking them by score.

Force Directed Graphs are self-organizing, visually appealing tools for representing relational data. The look is organic, because algorithms simulate the way charged particles arrange in space. They work great in user interfaces because the user has access to data nodes while the graph is being organized."

Examples here:

● http://www.kylescholz.com/blog/2006/06/first_whack_at_javascript_visu.html

● http://www.kylescholz.com/blog/2006/06/force_directed_graphs_in_javas.html#more

● http://www.kylescholz.com//projects/jsviz/0.2/a/examples/svg/example01_fd.html

How to use (for an older version):

● http://www.kylescholz.com/blog/2006/06/using_force_directed_graphs.html

FOAFMap [edit]

Relevant to our Communities and persons in communities, can we build a map of users and display on a map? How about CoP map?

Publication http://www.semanticscripting.org/SFSW2006/challenge/FOAFMap.pdf

http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (3 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ

Example see resources from ESWC conference ontology and resulting FOAF map

● http://www.eswc2006.org/technologies/index.php

● http://foafmap.net/user/28/&header=http://www.eswc2006.org/technologies/images/technologiesbanner.gif

Fresnel RDF Display Technologies [edit]

See Fresnel RDF Display technologies

!http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/tutorial/horus/images/fresnel.jpg!

Browser applications demonstrating visualisation [edit]

Horus [edit]

http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/tutorial/horus/index.htm#horus

LGPL, Java

Implements Fresnel for displaying RDF Graphs

From the site:

Horus is a simple RDF browser which supports the Fresnel display vocabulary.

Fresnel is a simple, browser-independent vocabulary for specifying how RDF graphs are presented. Fresnel's two foundational concepts are lenses and formats. Lenses define which properties of an RDF resource, or group of related resources, are displayed and how those properties are ordered. Formats determine how resources and properties are rendered and provide hooks to existing styling languages such as CSS. More information about Fresnel is found on the W3C Fresnel homepage.

!http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/tutorial/horus/images/screenshot3_large.JPG!

SMILE Projects [edit]

Longwell, etc

Comprehensive Tools, Frameworks [edit]

http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (4 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ mSpace Framework Software [edit]

mSpace

Another custom example with Google maps: [edit]

http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (5 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ

Archives Thesauri - example visualisation in thesauri [edit]

UKAT - UK Archive Thesaurus [edit]

http://www.ukat.org.uk/

We describe this elsewhere, UIs are very relevant and QVIZ should try to offer similar solutions.

Available as SKOS which includes a micro.thesausus linking entries to a concept/topic organisation.

See site, we will try to make screenshots later.

Retrieved from "http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (6 of 7)2006-09-29 08:50:24 Visualisation and Knowledge - QVIZ

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:55, 25 September 2006. ● This page has been accessed 17 times.

http://qviz.humlab.umu.se/index.php/Visualisation_and_Knowledge (7 of 7)2006-09-29 08:50:24 General functionalities - QVIZ

General functionalities

From QVIZ

Jump to: navigation, search Contents

● 1 GIS in general

● 2 Web GIS

● 3 Community-based WGIS

● 4 Benefits

● 5 Measures for the quality

● 6 Problems

● 7 References

[edit] GIS in general

A geographic information or geographical information system (GIS) is an organized collection of computer hardware, software, geographic data, and personnel designed to efficiently capture, edit, share, integrate, update, manipulate, analyze, and display all forms of geographically referenced information. GIS technology works by relating information from different sources and analyzing the connections and patterns within. GIS also allows building model scenarios to test a particular hypothesis, make scientific investigations, resource management, asset management, development planning and cartography and route planning.

Most data has a geographic component. The GIS provides a powerful, logical, and intuitive means to store, manipulate and retrieve data. GIS can be used like a traditional map to determine where features are. It can track changes over short or extended periods of time and map quantities or densities. In a more generic sense, GIS is a tool that allows users to create interactive queries (user created searches). This provides the ability to see on screen or in map form, only those features or objects that meet specific selection criteria. In an instant, you can visually identify features in a geographic representation that would take much longer to find in a printed report.

The GIS can provide accurate answers to geographic questions such as:

● Where is a feature located? ● What is it adjacent to? ● What is its relationship to other features?

[edit]

http://qviz.humlab.umu.se/index.php/General_functionalities (1 of 4)2006-09-29 08:50:26 General functionalities - QVIZ Web GIS

The Web-GIS (WGIS) is a comprehensive tool for delivering GIS and mapping functionality. In layman's terms, it is a kind of "smart map" in the World Wide Web. WGIS refers to geographic information systems that utilize the Internet to host distributed applications that can be shared and made publicly accessible. The main functionalities include map image presentation/rendering for webpages in Internet, as well as geocoding and reverse geocoding. Geocoding is the process of assigning coordinates or other geographic identifiers to map features and other data records, such as administrative units or addresses (descriptive addresses). Reverse geocoding is the conversion of coordinate data of locations into descriptive addresses.

Community-based WGIS [edit]

The web-based technologies help to meet goals of community-based or public participation GIS. Those kind systems significantly improve the ability of the public to use computer mapping and leads to greater participation. Those advances in WGIS technology will actually lead to the increased public participation, transparency in government, geographic literacy and better data-driven decision making by community-based organizations, communities of practice (CoP).

Benefits [edit]

Main advantages for communities from WGIS usage:

● _increasing richness trough increased accessibility_: community networks enable information richness to be increased by enabling information from multiple sources to be shared, correlated, fused and accepted; ● _increasing shared awareness_: community networks contribute to the generation of shared awareness by enabling richness to be shared; ● _improved collaboration_: networks enable information sharing which transforms shared awareness into collaborative planning and synchronized actions to create completive advantage, a knowledge collaboration;

Measures for the quality [edit]

The main measures for the quality of WGIS (and GIS):

● completeness – a lack of errors of omission in a database; the percentage of source or phenomena being mapped; can be described by listing what features are included in the data and whether the data are "completed" or "in progress"; ● correctness – data accurately reflects true attributes; ● commonality – track attributes of shared data are same for each user; ● continuity – proper maintenance of attributes over time; ● timeliness – data is where it’s needed, when it’s needed.

http://qviz.humlab.umu.se/index.php/General_functionalities (2 of 4)2006-09-29 08:50:26 General functionalities - QVIZ

Problems [edit]

WGIS also creates a number of new barriers that are more formidable than they first appear. For example, the range of specialized skills and knowledge required or the way in which GIS software can be empowering/disempowering may be exacerbated in WGIS.

Community-based GIS projects, especially the web-GIS ones, face a more stringent set of requirements. GIS has become more accessible to those individuals not trained as GIS professionals. These non-expert users, e.g. people with little computer experience, occasional users, GIS novices, and the interested public, are increasingly able to take advantage of mapping software. Friendlier user interfaces, substantial increases in publicly available data, public investment in training and education, and other factors contribute to wider usage of GIS by non-experts. The system architecture, user interfaces, and the development of data partnerships are key components in building sustainable, effective web-GIS projects.

A customized, distributed web services model is capable of capitalizing on economies of scale and remote technology while maintaining its commitment to serving non-expert GIS users. WGIS projects are enabling anonymous users to upload and integrate local data, facilitate inter-community cooperation, and efficiently utilize the range of publicly available data.

References [edit]

Alberts, David S.; John J. Garstka and Frederick P. Stein. "Network Centric Warfare - 2nd Edition". CCRP, 1999, 284 p. Alberts, David S.; Garstka, John J.; Hayes, Richard E.; Signori, David A. „Understanding Information Age Warfare”. CCRP, 2001, 312 p.

Retrieved from "http://qviz.humlab.umu.se/index.php/General_functionalities"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

http://qviz.humlab.umu.se/index.php/General_functionalities (3 of 4)2006-09-29 08:50:26 General functionalities - QVIZ

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 8 times.

http://qviz.humlab.umu.se/index.php/General_functionalities (4 of 4)2006-09-29 08:50:26 Visualization - QVIZ

Visualization

From QVIZ

Jump to: navigation, search Contents

● 1 1.0 Internet GIS visualization

● 2 1.1 2D maps

● 3 1.2 Half-3D maps (tilted maps)

● 4 1.3 3D maps

● 5 1.4 Animations

● 6 1.5 Advanced web based georeferenced image handling

● 7 1.6 Visualization of interactive user interfaces

● 8 1.7 User customizable visualization

● 9 1.8 Relevant applications using Semantic web technologies

[edit] 1.0 Internet GIS visualization

1.1 2D maps [edit]

Thematic maps just like traditional paper maps show diverse thematic data (e.g. distribution of phenomenon) onto a 2D-representation space. http://world.maporama.com/idl/maporama/default.aspx http://mail.google.com/maps

1.2 Half-3D maps (tilted maps) [edit]

Famous site Map24 lets you tilt a map and change direction of a map image in the window. Additional functionality is a “route flight”. A map is accomplished taking advance of Java applet. Even AJAX API is available for developers. http://www.de.map24.com/

1.3 3D maps [edit]

Generation of 3D internet maps require more complex technical solutions and are much more resource-demanding from both server and client side. Usually these web-based applications take advance of computers 3D video card.

_Web based 3D GIS viewer by David Rumsey allows users to experience the power and flexibility of desktop 3D GIS, using only their Web browsers and 3D video card capabilities. 4 maps based on historic maps that have been combined with current digital elevation models (DEMS) of the same locations_. http://www.davidrumsey.com/GIS/3d.htm

More advanced solutions have been accomplished as desktop applications. http://earth.google.com/products.html Google SketchUp lets create your own 3D objects and put them onto Google Earth. http://sketchup.google.com/index.html

1.4 Animations [edit]

1. Indian ocean tsunami 26.12.2004 http://www-dase.cea.fr/actu/dossiers_scientifiques/2004-12-26/index.html

2. Iraq War Coalition Fatalities – Visual and sound effects http://www.obleek.com/iraq/index.html Very relevant for QVIZ

3. Animated TimeMap of the Khmer Empire 100 CE - 1550 CE http://ecaimaps.berkeley.edu/animations/2003_03_khmer_animation.swf Very relevant for QVIZ

4. Control over animated content Very relevant for QVIZ http://www.socialexplorer.com/pub/maps/home.aspx

5. Combination of animated map and additional information fields http://www.seagrant.umn.edu/flashflood/

http://qviz.humlab.umu.se/index.php/Visualization (1 of 7)2006-09-29 08:50:29 Visualization - QVIZ

Animation of showing a map, animation of map interface 6. http://www.uk.map24.com/ (Animation of map navigation, route animation, animated presentation of search results, half-3D view)

7. http://atlas.freshlogicstudios.com/ (Animation of map navigation, bird’s Eye view)

8. http://maps.ask.com/maps (route animation, animation of map interface)

9. http://maps.yahoo.com/beta/index.php# (animated map navigation, GUI, route, Traffic desity)

1.5 Advanced web based georeferenced image handling [edit]

Interactive blend/fade/merge and overlay/swipe multiple map layers for enabling real-time visual change analysis over the Internet. Technologies: Maplicity™ and MapImager™, ArcIMS. Overkiller for sure! http://www.davidrumsey.com/gis/tokyo.htm

1.6 Visualization of interactive user interfaces [edit]

User can interact with the map choosing an appropriate set of thematic layers. http://tourism.tallinn.ee/map

Common features Soft zoom in, zoom out, dynamic changing of map layers according to a map scale, highlighting of requested map objects, onMouse events that change size, color, etc of map objects or toolbar buttons etc. Flash, java applet, javascript. http://www.eoy.ee/atlas/ Semitransparent vector objects http://kaardid.regio.ee/pria/index2.php?lang=0

1.7 User customizable visualization [edit]

Personalized symbol sets Users of Maporama have possibility to personalize map choosing one of the visualization templates (ca 30), scale units (km, miles) and size of map window according to screen resolution. http://world.maporama.com/idl/maporama/default.aspx

Map Symbol Brewer Creation of map symbols with SVG (Scalable Vector Graphics). http://www.svgopen.org/2004/papers/ MapSymbolBrewer/

Dot Map visualization Image:Dotmap.gif Quantity visualization of different type of resources.

1.8 Relevant applications using Semantic web technologies [edit] asemantics

Note: SPARQL based query over RDF data. SPARQL is similiar to SQL.

● Company site: asemantics http://www.asemantics.com/

● Satellite and GIS visualisations http://images.eoportal.org/

● SPARQL query example http://demo.asemantics.com/zparqler/examples/example7.html

SPARQL Example: Get latest images from images.eoportal.org This example shows how we create the bottom part of our home page. The example uses data in RDF from the eoPortal of the European Space Agency.

The HTML code of the home page contains a server side include which calls our "sparqler". The sparqler executes the SPARQL request and returns data serialized in XML according to the 'dawg-xml' format. (In this demo we use an older version of SPARQL with some experimental features like LIMIT, OFFSET and ORDER BY. This dialect is identified by http://rdfstore.sourceforge.net/sparql/extended/.) In the last step, XML data data is processed by XSLT to create the HTML code you finally see on our home page.

Smart Content Factory

http://qviz.humlab.umu.se/index.php/Visualization (2 of 7)2006-09-29 08:50:29 Visualization - QVIZ

Media:Presentation

Project goals:

● Development of a prototype of a knowledge-based audiovisual archive and navigation system for TV, radio and online broadcasts ● Increasing the utilization of audiovisual content repositories

http://qviz.humlab.umu.se/index.php/Visualization (3 of 7)2006-09-29 08:50:29 Visualization - QVIZ

http://qviz.humlab.umu.se/index.php/Visualization (4 of 7)2006-09-29 08:50:29 Visualization - QVIZ

VICODI

http://www.vicodi.org

Contextualisation and visualisation of Historical SVG based maps and textual content. Based on the content, European maps are selected according to the estimated LATCH context (Location, Time and Category). Shapes on the selected map, corresponding to locations in an European History Ontology, are contextualised by means of color coding according to relevance to the article, weighted contextual queries are embedded into the map relevant to the estimated historical context of the article, and additional features in user interface are embedded such as estimating other important events, persons, notions relevant to the article LATCH and context. Within the article, links are also color coded to denote relevance to the article and the link is an embedded contextualised query for other articles whose context is similiar to the current article.

● Finding the Context of historical Documents ● Automatic Feature Extraction ● Multilingual Contextualization ● Context Sensitive Search Engine ● Development of a European History Ontology and time model

● Article input

http://qviz.humlab.umu.se/index.php/Visualization (5 of 7)2006-09-29 08:50:29 Visualization - QVIZ

● result of article contextualisation - Map contextualisation and article contextualisation (embedded contextualised query links in both map and article)

http://qviz.humlab.umu.se/index.php/Visualization (6 of 7)2006-09-29 08:50:29 Visualization - QVIZ

Retrieved from "http://qviz.humlab.umu.se/index.php/Visualization"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 15:56, 25 September 2006. ● This page has been accessed 34 times.

http://qviz.humlab.umu.se/index.php/Visualization (7 of 7)2006-09-29 08:50:29 Service standards - QVIZ

Service standards

From QVIZ

Jump to: navigation, search Contents

● 1 OGC standards

● 2 GML

● 3 WMS

● 4 WFS

● 5 Scalable Vector Graphics

[edit] OGC standards

Web: http://www.opengeospatial.org/ wikipedia: http://en.wikipedia.org/wiki/Open_Geospatial_Consortium

OGC (Open Geospatial Consortium) is an international non-profit consensus standards organization. There are collaborating more than 300 companies, government agencies and universities. Different specifications support interoperable solutions for GIS data processing and exchange. OGC works closely together with the International Standadization Organisation (ISO). One of the specifications that have been adopted by OGC and ISO (ISO/TC 211) is GML (Geography Markup Language). The main 2 widely used specifications are WMS that handles map images on the internet and WFS handles vector and attributed GIS data.

GML [edit] wikipedia: http://en.wikipedia.org/wiki/Geography_Markup_Language

Geography Markup Language (GML) is an XML grammar written in XML Schema for the modelling, transport, and storage of geographic information. GML provides possibility for encoding of geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, generalized values and value objects. GML is key specification in OGC as for example WFS specification uses it for data exchange.

KML, Keyhole Markup Language, used by Google Earch shares some features with GML wikipedia:

http://qviz.humlab.umu.se/index.php/Service_standards (1 of 4)2006-09-29 08:50:31 Service standards - QVIZ http://en.wikipedia.org/wiki/KML

WMS [edit] wikipedia: http://en.wikipedia.org/wiki/Web_Map_Service

Web Map Service enables transfer of map images on the Internet. It is based on a tight connection between a server and a client; both implementing and following the WMS interface. Since it is recognized as a worldwide standard, WMS plays an important role in the development of different map services on the Internet. It is also an important free alternative to vendor specific formats. WMS produces designed maps mainly in pictorial formats such as PNG, GIF, JPEG or could also produce designed vector maps in formats such as Scalable Vector Graphics (SVG) or Macromedia Flash format file format (SWF). WMS requests can be submitted in the form of Uniform Resource Locators (URLs). The answer will be as a map image file or error message in XML. A WMS session consists of three different requests, \GetCapabilities, \GetMap and \GetFeatureInfo. The first two are mandatory for all WMS servers to support (so called Basic WMS), whereas the \GetFeatureInfo is optional. A WMS that also supports the \GetFeatureInfo-request is called a Queryable WMS.

WFS [edit] wikipedia: http://en.wikipedia.org/wiki/Web_Feature_Service

Web Feature Service is an interface allowing requests for geographical features across the web using platform-independent calls. The WFS specification defines interfaces for describing data manipulation operations of geographic features. Data manipulation operations include the ability to:

● Create a new feature instance ● Delete a feature instance ● Update a feature instance ● Get or Query features based on spatial and non-spatial constraints

A WFS session consists of five operations: \GetCapabilities, \DescribeFeatureType, \GetFeature, Transaction and \LockFeature. A Basic WFS only needs to support \GetCapabilities, \DescribeFeatureType, \GetFeature. WFS support both Hypertext Transfer Protocol (HTTP) methods: POST and GET. Requests use GML notation.

Scalable Vector Graphics [edit]

Web: http://www.w3.org/Graphics/SVG/ wikipedia:http://en.wikipedia.org/wiki/Svg

http://qviz.humlab.umu.se/index.php/Service_standards (2 of 4)2006-09-29 08:50:31 Service standards - QVIZ

Scalable Vector Graphics (SVG) is a language for describing two-dimensional graphics and graphical applications in XML. SVG can be either declarative or scripted. It is an open standard created by the World Wide Web Consortium (W3C). SVG has three types of graphic objects: vector, raster and text.

SVG is a platform for two-dimensional graphics. It has two parts: an XML-based file format and a programming API for graphical applications. Key features include shapes, text and embedded raster graphics, with many different painting styles. It supports scripting through languages such as \ECMAScript and has comprehensive support for animation.

SVG is used in many business areas including Web graphics, animation, user interfaces, graphics interchange, print and hardcopy output, mobile applications and high-quality design.

SVG is a royalty-free vendor-neutral open standard developed under the W3C Process. It has strong industry support; Authors of the SVG specification include Adobe, Agfa, Apple, Canon, Corel, Ericsson, HP, IBM, Kodak, Macromedia, Microsoft, Nokia, Sharp and Sun Microsystems. SVG viewers are deployed to over 100 million desktops, and there is a broad range of support in many authoring tools.

SVG builds upon many other successful standards such as XML (SVG graphics are text-based and thus easy to create), JPEG and PNG for image formats, DOM for scripting and interactivity, SMIL for animation and CSS for styling.

SVG is interoperable. The W3C release a test suite and implementation results to ensure conformance. (http://www.w3.org/Graphics/SVG/About.html)

Retrieved from "http://qviz.humlab.umu.se/index.php/Service_standards"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

http://qviz.humlab.umu.se/index.php/Service_standards (3 of 4)2006-09-29 08:50:31 Service standards - QVIZ

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 23:46, 21 September 2006. ● This page has been accessed 22 times.

http://qviz.humlab.umu.se/index.php/Service_standards (4 of 4)2006-09-29 08:50:31 Client technologies - QVIZ

Client technologies

From QVIZ

Jump to: navigation, search Contents

● 1 Web mapping

● 2 Flash

● 3 SVG

● 4 JAVA

● 5 AJAX

● 6 Javascript

[edit] Web mapping

For handling Geographic Information System over web browsers it all comes down to handle vector data . More over it’s about programmable vector graphics to achieve interactivity. Raster data handling functionality is also important, but it’s usually developed together with vector graphics.

Most used technologies for building GIS web applications are Flash, Java and SVG.

AJAX and JavaScript are supporting all of them and of course HTML, CSS, XHTML, DHTML etc are used for layout.

Flash [edit]

The Flash Player, developed and distributed by Adobe Systems, is a client application available in most dominant web browsers. It features support for vector and raster graphics, a scripting language called ActionScript and bidirectional streaming of audio and video.

Web: http://www.adobe.com/products/flash/

Examples:

Probably the most famous web map application with Flash is Yahoo maps (http://maps.yahoo.com/ beta/index.php#maxp=search&q1)

http://qviz.humlab.umu.se/index.php/Client_technologies (1 of 4)2006-09-29 08:50:32 Client technologies - QVIZ Regio applications built with Flash: Applications#Regio applications

USA Climate Summary Map (http://www.usflashmap.com/samples/USA_Climate/index_ext.html)

SVG [edit]

SVG is developed by World Wide Web Consortium (WC3) and is the standard (Service_standards#Scalable_Vector_Graphics) for GIS presentation on the web.

The source of an SVG graphic is an XML document so it can be used in conjunction with XML related technologies, processed on the server and sent to the client's browser (or web enabled device) like any other XML file. To describe the potential for information rich content delivered via SVG as HUGE would be an understatement.

Advantage to use right mouse button for map interactivity and navigation (Flash doesn’t enable that)

Exaples: Animation of path morphing: http://www.carto.net/papers/svg/samples/path_morphing. shtml

GIS with SVG: http://www.carto.net/neumann/cartography/vienna/index.svgz

More examples: http://www.carto.net/papers/svg/samples/#iact

JAVA [edit]

Vector capability has been available in principle in the form of Java applets for many years, but for whatever reason, has not been widely used in online GIS applications. Still gives all the possibilities to make interactive web map applications. http://today.java.net/pub/a/today/2004/02/16/gis.html

Possible to use with SVG and use also right mouse button (example: http://kart.nois.no/romerike/ Content/Main.asp?layout=romerike&vwr=java)

There are some libraries for GIS data handling and presentation. For example GeoTools which is an open source java toolkit for developing interactive geographical maps. The emphasis is on client side mapping applets which require little or no server side support. (http://geotools.codehaus.org/)

Examples: http://kitmaps.city.kitchener.on.ca/onpoint4/onpoint?LINK=true (IE only)

http://qviz.humlab.umu.se/index.php/Client_technologies (2 of 4)2006-09-29 08:50:32 Client technologies - QVIZ

AJAX [edit]

Google Maps is probably the best-known Ajax application.Uses AJAXSLT (http://goog-ajaxslt. sourceforge.net/) and Google Maps API (http://www.google.com/apis/maps/) AJAXSLT is an implementation of XSL-T in JavaScript, intended for use in fat web pages, which are nowadays referred to as AJAX applications. Because XSL-T uses XPath, it is also an implementation of XPath that can be used independently of XSL-T.

Google Maps example with HTML and overlaid vector layers http://www.thrall.net/maps/mbta.html

More about AJAX technology and Flash together: http://qviz.humlab.umu.se/index.php/ AJAX_and_FLASH_Together

Javascript [edit]

Example of Javascript, HTML application: http://mapserver.commenspace.org/sustainable_seattle/ demographic-map.php Here you can see also some javascript animations with map window.

Retrieved from "http://qviz.humlab.umu.se/index.php/Client_technologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

http://qviz.humlab.umu.se/index.php/Client_technologies (3 of 4)2006-09-29 08:50:32 Client technologies - QVIZ

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 02:02, 22 September 2006. ● This page has been accessed 24 times.

http://qviz.humlab.umu.se/index.php/Client_technologies (4 of 4)2006-09-29 08:50:32 Server-side technologies - QVIZ

Server-side technologies

From QVIZ

Jump to: navigation, search Contents

● 1 Developing languages

❍ 1.1 PHP

❍ 1.2 JAVA

● 2 Spatial databases

❍ 2.1 PostGIS

● 3 WEB map servers

❍ 3.1 Minnesota Mapserver

❍ 3.2 Geoserver

[edit] Developing languages

PHP [edit]

Web: http://php.net/ Hypertext Preprocessor (PHP) is an open-source, reflective programming language. Originally designed as a high-level tool for producing dynamic web content, PHP is used mainly in server-side applications. Most of PHP syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features.

PHP generally runs on a web server, taking PHP code as its input and creating Web pages as output. When running server-side, the PHP model can be seen as an alternative to Microsoft's ASP.NET/C#/ VB.NET system, Macromedia's ColdFusion, Sun Microsystems' JSP, Zope, modperl and the Ruby on Rails framework. To more directly compete with the "framework" approach taken by these systems, Zend is working on the Zend Framework - an emerging (as of June 2006) set of PHP building blocks and best practices. (http://en.wikipedia.org/wiki/Php)

JAVA [edit]

Java has been emerging as one of the programming languages of choice for GIS. There are many projects ongoing developing libraries of back-end GIS functions and GIS applications. Java could be used for example data generalization purposes.

The GeoServer

http://qviz.humlab.umu.se/index.php/Server-side_technologies (1 of 5)2006-09-29 08:50:34 Server-side technologies - QVIZ

The GeoServer project is a full transactional Java (J2EE) implementation of the OpenGIS Consortium's Web Feature Server specification, with an integrated WMS. It is free software, available under the GPL 2.0 license. Users who would like to access and modify their geographic data over the Internet using flexible, industry-approved standards should take a look at GeoServer or one of the existing commercial Web Feature Servers. Web: http://docs.codehaus.org/display/GEOS/ Home

Deegree

Deegree is a Java Framework offering the main building blocks for Spatial Data Infrastructures. Its entire architecture is developed using standards of the Open Geospatial Consortium (OGC) and ISO/ TC 211 (ISO Technical Committee 211 -- Geographic Information/Geomatics). Web: http://www. deegree.org/

JUMP

The Unified Mapping Platform (JUMP) is a GUI-based application for viewing and processing spatial data. It includes many common spatial and GIS functions. It is also designed to be a highly extensible framework for developing and running custom spatial data processing applications. Web: http://www.jump-project.org/

Spatial databases [edit]

There are two main spatial extensions for database extension: Mysql Spatial and PostGIS. Though PostGIS is far spatially enambled than Mysql. For instance Mysql Spatial doesn’t support transactional spatial tables and does not have functions like intersects or overlaps.

PostGIS [edit]

WEB: http://postgis.refractions.net/ PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRI's SDE or Oracle's Spatial extension. PostGIS follows the OpenGIS "Simple Features Specification for SQL" and will be submitted for conformance testing at version 1.0.

PostGIS has been developed by Refractions Research as a research project in open source spatial database technology. PostGIS is released under the GNU General Public License. We intend to continue development as time and resources permit. Our list of future projects includes enhanced technology for data loading and dumping, user interface tools for direct data access and manipulation, and support for advanced topologies at the server side, such as coverages, networks, and surfaces. (http://postgis.refractions.net/)

http://qviz.humlab.umu.se/index.php/Server-side_technologies (2 of 5)2006-09-29 08:50:34 Server-side technologies - QVIZ WEB map servers [edit]

Minnesota Mapserver [edit]

WEB-site: http://mapserver.gis.umn.edu/ MapServer is an Open Source development environment for building spatially-enabled internet applications. MapServer is not a full-featured GIS system, nor does it aspire to be. Instead, MapServer excels at rendering spatial data (maps, images, and vector data) for the web. Beyond browsing GIS data, MapServer allows you create "geographic image maps", that is, maps that can direct users to content. For example, the Minnesota DNR Recreation Compass provides users with more than 10,000 web pages, reports and maps via a single application. The same application serves as a "map engine" for other portions of the site, providing spatial context where needed. MapServer was originally developed by the University of Minnesota (UMN) ForNet project in cooperation with NASA and the Minnesota Department of Natural Resources (MNDNR). Presently, the MapServer project is hosted by the TerraSIP project, a NASA sponsored project between the UMN and consortium of land management interests. The software is maintained by a growing number of developers (nearing 20) from around the world and is supported by a diverse group of organizations that fund enhancements and maintenance.

Features

● Advanced cartographic output ❍ Scale dependent feature drawing and application execution ❍ Feature labeling including label collision mediation ❍ Fully customizable, template driven output ❍ TrueType fonts ❍ Map element automation (scalebar, reference map, and legend) ❍ Thematic mapping using logical- or regular expression-based classes ● Support for popular scripting and development environments ● PHP, Python, Perl, Ruby, Java, and C# ● Cross-platform support ❍ Linux, Windows, Mac OS X, Solaris, and more ● A multitude of raster and vector data formats ❍ TIFF/GeoTIFF, EPPL7, and many others via GDAL ❍ ESRI shapfiles, PostGIS, ESRI ArcSDE, Oracle Spatial, MySQL and many others via OGR ❍ Open Geospatial Consortium (OGC) web specifications ■ WMS (client/server), non-transactional WFS (client/server), WMC, WCS, Filter Encoding, SLD, GML, SOS ● Map projection support ❍ _On-the-fly map projection with 1000s of projections through the Proj.4 library

(http://mapserver.gis.umn.edu/)_

Geoserver [edit]

http://qviz.humlab.umu.se/index.php/Server-side_technologies (3 of 5)2006-09-29 08:50:34 Server-side technologies - QVIZ

Web: http://docs.codehaus.org/display/GEOS/Home GeoServer is an Open Source server that allows you to view and edit geographical data.

With GeoServer you can publish and edit data using open standards. Your information is made available in a large variety of formats as maps/images or actual geospatial data. GeoServer's transactional capabilities offer robust support for shared editing. GeoServer's focus is ease of use and support for standards, in order to serve as 'glue' for the geospatial web, connecting from legacy databases to many diverse clients. (http://docs.codehaus.org/display/GEOS/Home)

GeoServer supports transactional Web Feature Service (WFS) and Web Map Service (WMS) to produce JPEG, PNG, SVG, KML/KMZ, GML, PDF, Shapefiles and more. Geoserver is built on Geotools Java toolkit.

Retrieved from "http://qviz.humlab.umu.se/index.php/Server-side_technologies"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Server-side_technologies (4 of 5)2006-09-29 08:50:34 Server-side technologies - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 01:25, 22 September 2006. ● This page has been accessed 20 times.

http://qviz.humlab.umu.se/index.php/Server-side_technologies (5 of 5)2006-09-29 08:50:34 Applications - QVIZ

Applications

From QVIZ

Jump to: navigation, search [edit] Regio applications

1. Estonian Breeding Bird Atlas - http://www.eoy.ee/atlas/index.html 2. Historical Tartu - combines georefernced historical maps, old photographs, descriptions. http:// www.tartu.ee/vaateid_vanast_Tartust/rakendus/tartu_kaardid.swf 3. Test: Estonian manor borders on Google Map - http://kaardid.regio.ee/google/manors.php

Other applications [edit]

1. Google Map - http://mail.google.com/maps 2. Google Earth - http://earth.google.com/products.html 3. Map24 - http://www.de.map24.com/ 4. David Rumsey Map Collection - http://www.davidrumsey.com/ 5. La Bibliothèque nationale de France (click on tab "Geographic Access")

❍ America - http://gallica.bnf.fr/FranceAmerique/fr/default.htm

❍ Italy - http://gallica.bnf.fr/VoyagesEnItalie/

❍ Africa - http://gallica.bnf.fr/VoyagesEnAfrique/

1. AKTive Space http://www.aktors.org/technologies/csaktivespace/

AKTive Space (CAS) is an integrated Semantic Web application which provides a way to explore the UK Computer Science Research domain across multiple dimensions for multiple stakeholders, from funding agencies to individual researchers.

Retrieved from "http://qviz.humlab.umu.se/index.php/Applications"

Views

● Article

● Discussion

● Edit

● History

● Move

http://qviz.humlab.umu.se/index.php/Applications (1 of 2)2006-09-29 08:50:36 Applications - QVIZ

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 11 times.

http://qviz.humlab.umu.se/index.php/Applications (2 of 2)2006-09-29 08:50:36 Agent Frameworks - QVIZ

Agent Frameworks

From QVIZ

Jump to: navigation, search [edit] Jadex http://vsis-www.informatik.uni-hamburg.de/projects/jadex/features.php

Java based

"Jadex is a Java based, FIPA compliant agent environment, and allows to develop goal oriented agents following the BDI model. Jadex provides a framework and a set of development tools to simplify the creation and testing of agents.

The Jadex project aims to make the development of agent based systems as easy as possible without sacrificing the expressional power of the agent paradigm. To foster a smooth transition from traditional distributed systems to the development of (multi-) agent systems, well established object- oriented concepts and technologies should be employed wherever possible. With Jadex you are able to create agent systems without having to learn a new programming language. Jadex is designed to facilitate the implementation of agents in the widespread Java programming language, therefore allowing to reuse a vast amout of existing tools and libraries. " http://vsis-www.informatik.uni-hamburg.de/projects/jadex/images/bdi.gif

[[Image:[1]]]

Framework

The Jadex framework consists of an API, an execution model, and predefined reusable generic functionality. The API provides access to the Jadex concepts when programming plans. Plans are plain Java classes, extending a specific abstract class, which provides useful methods e.g. for sending messages, dispatching sub goals or waiting for events. Plans able to read and alter the beliefs of the agent using the API of the belief base. A special feature of Jadex is that in addition to directly retrieving stored facts, an intuitive OQL-like query language allows to formulate arbitrary complex expressions using the objects contained in the belief base.

In addition to the plans coded in Java, the developer provides an XML based Agent Definition File (ADF), which specifies the initial beliefs, goals, and plans of an agent. The Jadex runtime engine

http://qviz.humlab.umu.se/index.php/Agent_Frameworks (1 of 3)2006-09-29 08:50:37 Agent Frameworks - QVIZ reads this file to instantiate an agent model, and executes the agent by keeping track of its goals while contiunously selecting and executing plan steps, based on internal events and messages from other agents. Jadex is supplied with some predefined functionality e.g. to access a directory facilitator service. The functionality, coded in separate plans, is composed in reusable agent modules called capabilities, described in a format similar to the ADF, and can easily be plugged into existing agents.

Development Tools

An important quality aspect of any development environment is the available tool support. For one, Jadex is built on top of JADE and therefore a lot of readily available tools can also be used with Jadex. This is not only true for the tools included in JADE, such as the Sniffer or the DummyAgent, but also regards third party tools like the beangenerator plug-in for the ontology design tool Protégé.

On the other hand, the new concepts introduced by Jadex have to be supported as well. Therefore tools have been realized to aid the developer in dealing with these aspects e.g. related to the BDI model. The BDI Viewer tool allows to view the internal state of a Jadex agent, that is, its current beliefs, goals, and plans (see picture). The Jadex Introspector is similar to the JADE Introspector, allowing to monitor and influence the execution of an agent, by observing and influencing how incoming events are handled. For debugging purposes the Introspector also allows to put an agent into single-step mode (shown in the screenshot). In addition to the Jadex specific tools, a Logger Agent is provided, which allows to collect and view log messages from JADE and Jadex agents, following the Java Logging API.

Retrieved from "http://qviz.humlab.umu.se/index.php/Agent_Frameworks"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

http://qviz.humlab.umu.se/index.php/Agent_Frameworks (2 of 3)2006-09-29 08:50:37 Agent Frameworks - QVIZ

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:23, 19 September 2006. ● This page has been accessed 19 times.

http://qviz.humlab.umu.se/index.php/Agent_Frameworks (3 of 3)2006-09-29 08:50:37 Collection Description Overview and Importance - QVIZ

Collection Description Overview and Importance

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Importance to QVIZ

● 3 Collection Description Overview

● 4 Tools

● 5 QVIZ Notes

● 6 Meaning of "Collection"

● 7 RLSP and ISAD(G)

● 8 MICHAEL

[edit] Summary

Importance to QVIZ [edit]

Collections and their relationships to other collections are critical to QVIZ, especially the collection metadata provided by archives. Also, we expect users to create their own virtual collections.

Why so critical? Collections provide a more accessible way initially to discover resources and then to semantically describe resources belonging to them. We also have found that institutions are associating administrative units to collections in some fashion, either as separate fields in their database or even as part of a collection title. In ISAD(G), we assume that administrative units might be associated with any level within the ISAD(G) hierachy.

Furthermore, it is also important to enable the semantic description of collections that do not yet contain resources (digital objects).

Lastly, an expressive description might include a means to describe institutions or other organisations, digital collections and other types.

Collection Description Overview [edit]

● Relevant collection descriptions ❍ Michael ■ Site: http://www.michael-culture.org/

■ Documentation http://www.michael-culture.org/doc.html

■ links http://www.michael-culture.org/technology/collectiondescriptionmanual/links.htm

❍ RSLP (relationship to Michael) ■ RSLP Collection Description (Sept 2000) http://dlib.ukoln.ac.uk/dlib/september00/powell/09powell. html

■ http://www.ukoln.ac.uk/metadata/rslp/

❍ DCMI Collections

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (1 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

❍ Dublin Core Metadata Initiative Working Group on Collection Description

❍ Collection Descriptions: proprietary descriptions of Partners

● Relationship to RLSP, ISAD(G) and the Archives Hub, Dublin Core ❍ ISAD(G), RSLP and Dublin Core Relationship & mappings - 17 April 2000 http://www.ukoln.ac.uk/metadata/rslp/isadg/

Tools [edit]

1. Issue: are there tools for conversion to and from Michael (RLSP) and ISAD(G)? We then might adapt to also work with proprietary partner collection descriptions. 2. Michael - it was stated in 2005 that software would be released as open source... a special request can be made until it is ready for distribution. Perhaps there are conversion tools available... likely XSL based... 3. RLSP tools 1. web form, note how they get collection "partOf" relationships :( 1. http://www.ukoln.ac.uk/metadata/rslp/tool/

QVIZ Notes [edit]

● Mappings ❍ ISAD(G) and RLSP Collectin description (of Michael) at UKOLN ❍ DCMI : Our interest is in Michael and mappings to ISAD(G), however, we should be aware of any mappings between Michael and DCMI collections because there are proprietary collection structures in our partner archives. However, we should focus on Michael first.

Meaning of "Collection" [edit]

● Overview from Michael and DCMI

From site: http://www.michael-culture.org/technology/collectiondescriptionmanual/aboutcld.htm

MICHAEL-UK Collection Description Manual

What is a Collection Description?

In the simplest terms, a Collection Description is a description of a collection of items or objects. So why the capital letters? The reason is that there are many ways of describing collections. But our aim is to share the descriptions made available from many different kinds of organisation. To do this, we need to make sure that they are structured according to a common standard.

The Dublin Core Metadata Initiative Working Group on Collection Description (see the [Reference Shelf] for further information) offers the following definition:

The term 'collection' can be applied to any aggregation of physical or digital items. It is typically used to refer to collections of physical items, collections of digital surrogates of physical items, collections of 'born-digital' items and catalogues of such collections. Collections are exemplified in the following, non-exhaustive, list:

* Library collections * Museum collections

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (2 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

* Archives * Library, museum and archival catalogues * Digital archives * Internet directories and subject gateways * Web indexes * Collections of text, images, sounds, datasets, software, other material or combinations of these (this includes databases, CD-ROMs and collections of Web resources) * Other collections of physical items

A internationally agreed standard has been developed for these descriptions, which covers the following information:

* Descriptive infomation about the collection * Information about the collector * Information about the owner of the collection * Information about the physical location or point of access to the collection * Information about an administrator responsible for the collection

Each of these sets of information is divided into a number of smaller sections. A full list of these smaller sections is provided in the [MICHAEL Data Model]. To find out more, you should refer to the [Reference Shelf] for further information.

We can therefore define a Collection Description as a description of your collection that is structured according to this standard.

A note about items in more than one collection

A common question about Collection Description relates to the fact that the same item (or items) may appear in a number of different collections. This isn't a problem within Collection Description - the main thing is to remember that your descriptions should be created to serve a clear purpose, or let your users know what is in a particular collection.

To take an example - you might have a collection of books which have been donated by a B.Smith. You would probably provide a description of the 'B.Smith Collection'. However, the overall collection might include books about costume. It would also therefore be useful for your users to have a description of the 'Costume Collection' (which would include some of the same books as the 'B.Smith Collection'). Key Points

Collection Descriptions:

* Are based on a standard structure * Provide a way of describing collections or groups of objects, items or records

And remember! The same items can appear in a number of different collections - always provide Collection Descriptions where it is useful to do so.

● UKOLN ❍ Collection Description Issues Breakout session

❍ Extending the Collection Model

New Michael Heaney report on modelling the means by which users obtain access to collections. http://www.ukoln.ac.uk/ cd-focus/model-ext/CD2-principles-v2-2.pdf

❍ Metadata Collection Collection Level Description RSLP DCMI Meta

Pete Johnston, "Creating Reusable Collection-Level Descriptions", UKOLN Collection Description. 2004

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (3 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

❍ http://www.ukoln.ac.uk/cd-focus/

The aim of the Focus is to improve co-ordination of work on collection description methods, schemas and tools, with the goal of ensuring consistency and compatibility of approaches across projects, disciplines, institutions, domains and sectors. The Focus provides support for projects actively involved in collection description work and for those investigating or planning such work. One of the major strands of this support work has been the development of the CLD (Collection-Level Description) Online Tutorial. This has been created both as an aid to Implementers and as a tool for training.

The Focus will continue to promote and facilitate the use of the RSLP Collection Description Schema as the basis for collection description implementations. The Focus will also work with the Dublin Core Collection Description Working Group on the development of a DC-based schema for collection-level description, using the collection description attributes of the RSLP CD Schema as a starting point. Implementers are encouraged to join the DC-Collections list and contribute to the work.

The Focus will be supporting a range of initiatives including the continuing NOF Digitisation of Learning Materials Programme, Peoples Network Programme, Resource Regional Cross-Domain research projects, British Library Co- operation and Partnership Programme and a range of JISC projects. The Focus will also be seeking to engage with the FE sector through contact with the Regional Support Centres.

● DCMI Collection Description Working Group http://dublincore.org/groups/collections/

From site:

● library collections, ● museum collections, ● archives, ● library, museum and archival catalogues, ● digital archives, ● Internet directories and subject gateways, ● Web indexes, ● collections of text, images, sounds, datasets, software, other material or combinations of these (this includes databases, CD-ROMs and collections of Web resources),

* other collections of physical items.

RLSP and ISAD(G) [edit]

From site: http://www.ukoln.ac.uk/metadata/rslp/isadg/

● The RSLP collection description schema is not intended to be a replacement for richer archival description schemas, such as that offered by ISAD(G). Rather, it should be seen as a schema for making relatively simple collection descriptions in a wide variety of contexts - a 'Dublin Core' for collection description.

● It is noted that several of the current RSLP projects will be contributing descriptions to the Archives Hub (or will be elligible to contribute descriptions to the Hub). The RSLP collection description project recognises that it is not sensible to ask those projects to describe the same collections twice.

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (4 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

● To enable RSLP projects to describe collections once, a mapping from ISAD(G) to the RSLP collection description schema or vice versa is necessary, allowing collection descriptions in one format to be transformed into the other format.

● Mappings between ISAD(G) and the RSLP collection description schema, and tools to automate conversion between ISAD(G) conformant EAD and RSLP collection descriptions encoded in RDF are likely to be generally useful, particularly given the possibility that the RSLP collection description schema may be used outside of the RSLP context.

● An ISAD(G) to RSLP schema mapping is required to enable those collection descriptions that are contributed by RSLP projects to the Archives Hub to be gathered into the UKOLN RSLP Collection description search demonstrator. An RSLP schema to ISAD(G) mapping may be required to enable future cross-searching of RSLP and ISAD(G) repositories - however, there no obvious immediate requirement for this mapping.

MICHAEL [edit]

See http://www.michael-culture.org/doc.html for XML Schemas, documentation on MICHAEL Data Model,etc

MICHAEL Data Model Document 1.0

The focus is on digital collections, but collections have owners or creators, therefore MICHAEL describes institutions, projects, products or services. MICHAEL has 5 entities in the data model corresponding to 5 different data structures. One entity of each kind of record.

● digital collections ● physical collections ● institutions ● projects or programmes ● services or products

An entity includes a set of fields to describe the entity corresponding to the entity type. Relations between instances (or records) can be made (linking records), for example to express a relation between the digital collection "record" and the "record" of the institution that owns the collection, etc.

The set of fields can be more complex since this is an structure XML data. Hierarchies of nodes might lead to grouping of fields into a common concept, some fields might be repeatable.

Relations between records.

MICHAEL describes it all rather simply in the MICHAEL Data Model report (1.0) (see documenation link). There is no specific direction of the link... it sounds symmetric, but their description is really describing directional aspect using inverse property relations. Example: hasOwner isOwnerOf is implies a direction. (not a real MICHAEL relation)

Relations seem to include both "data and object" properties meaning there are a data based on a controlled vocabulary true, false, yes, no,etc.

Fields seem to make use of controlled vocabularies as well. Is this controlled for MICHAEL? How do institutions map their subject headings,etc to MICHAEL vocabulary?

Comments for QVIZ:

● With ISAD(G), we have the notion of both physical, and potentially, digital collections depending on digitisation

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (5 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

efforts to preserve the physical collections. ● We must handle the location aspects, at least distinguish them admin units from generic location or place name. ● It is an XML based model (XML Schema) and QVIZ should make an RDF mapping or inquire about RDF based models. Interestingly, the RSLP was based on RDF, we must contact the project MICHAEL for information regarding RDF schemas.

●

Retrieved from "http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (6 of 7)2006-09-29 08:50:41 Collection Description Overview and Importance - QVIZ

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 5 times.

http://qviz.humlab.umu.se/index.php/Collection_Description_Overview_and_Importance (7 of 7)2006-09-29 08:50:41 Communities Of Practice - QVIZ

Communities Of Practice

From QVIZ

Jump to: navigation, search

Of interest to QVIZ is to also record the "type" of CoP in each CoP. Would it also dictate the kinds of ontology support for communities planned in QVIZ, or the types of dicussions and collaboration they can perform....

CoP Definition from "wikipedia:"http://en.wikipedia.org/wiki/Community_of_practice:

The concept of a community of practice (often abbreviated as CoP) refers to the process of social learning that occurs when people who have a common interest in some subject or problem collaborate over an extended period to share ideas, find solutions, and build innovations.

Consider all the following (from wikipedia), because in QVIZ we might have the case(s) where there a more SPECIFIC interpretation of CoP.

The term Communities of Practice — though because of the words chosen for it, the term seems as though it stands just for shared practice — was created to refer to a larger whole. It is a common misconception that other types of communities are needed to refer to a different philosophical foundation. The theoretical foundation for the below-mentioned 'community types' all root in what has been described for Communities of Practice (see discussion of this article). However, it might serve a specific practical purpose to refer to a specific type of Community of Practice using more illustrative expressions such as:

* Communities of Action * Communities of Circumstance * Communities of Interest * Communities of Position * Communities of Purpose

● QVIZ Understanding or what we really mean or want. ❍ A group that collaborates within a social software environment. A community could be a group of students participating in a course. ❍ By default: ■ Social object resources created by members. ■ Should be restricted to memebers, unless certain access rights are

http://qviz.humlab.umu.se/index.php/Communities_Of_Practice (1 of 3)2006-09-29 08:50:44 Communities Of Practice - QVIZ granted to other Communities, to the world, other other ... ■ Query results by default pertain to what the community created, but, if allowed, an expanded query can return results from other selected communities or the world. ■ Has a list of default ontology schemas. ■ Is administrated by a lead person(s) to control access to the community; set roles; assigns/removes users from the community ■ A user add configuration data for the community ■ User interface choices / recommendatations to supplement "default" query/visualation features. ■ Navigational / interactive Semantic objects ■ Interactive Thematic maps

● Issues: ❍ Default communities might be accessable by all communities, but with definable access rights. ■ Examples: ■ Institutional Archivists provide core info for archive materials, administative units,etc. ❍ Certain instantces of a public or semi-public social objecct Classes might be assessable by all communities. ■ Examples: ■ Administrative unit descriptions ■ Archive ISAG(G) level descriptions (the fond, or serial, etc)

● Links for deeper understanding: ❍ http://en.wikipedia.org/wiki/Community_of_practice

❍ http://www-users.cs.york.ac.uk/~kimble/teaching/mis/Communities_of_Practice.html

❍ http://www.co-i-l.com/coil/knowledge-garden/cop/lss.shtml

❍ http://home.att.net/~discon/KM/CoPs.htm

❍ http://www.funderstanding.com/communities_of_practice.cfm

Retrieved from "http://qviz.humlab.umu.se/index.php/Communities_Of_Practice"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

http://qviz.humlab.umu.se/index.php/Communities_Of_Practice (2 of 3)2006-09-29 08:50:44 Communities Of Practice - QVIZ

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 11:35, 20 September 2006. ● This page has been accessed 14 times.

http://qviz.humlab.umu.se/index.php/Communities_Of_Practice (3 of 3)2006-09-29 08:50:44 Organisation - how might roles be organised by the community? - QVIZ

Organisation - how might roles be organised by the community?

From QVIZ

Jump to: navigation, search [edit] Summary

How could a CoP regulate certain roles within the community? In QVIZ there are roles within a CoP and also roles that apply to all communities or some system wide aspect e.g. what role can create a new CoP?

Research [edit]

The fourth of the organizational modes in Oliver Williamson's

Economic The Economic Institutions of Capitalism are Peer Groups. A Peer Group factory is communally owned, but rather than being paid for their own products which they make from start to finish under Communal-emh , each worker is compensated equally based on the factory output. Workers may rotate stations as desired. Rather than devolving into negotiation over every detail, the workers elect leaders to make tactical, operational decisions, while strategic decisions are still made collectively (consensus or majority rule). The leader elections should rotate to avoid any hierarchy.

(http://www.zianet.com/ehusman/weblog/2006/08/peer-groups.html)

The interesting part here ist that a leader is elected for tactical decisions, while the strategic decisions are still group decisions.

Possibly such a system is usable, if it is properly supported, and assuming the group which formed wants to stay this was, otherwise an administrator could make a position permanent.

Anyhow, assuming the group wants to stay 'informal' e.g. only an association of like minded people, the way to utilize this is to define goals for the group, and than elect some person to be the leader until the goal is reached. E.g. a goal could be the discussion about something, in that case the leader would be selected for the duration of the discussion as moderator. Another goal could be the accumulation of

http://qviz.humlab.umu.se/index.php/Organisation_-_how_might_roles_be_organised_by_the_community%3F (1 of 3)2006-09-29 08:50:46 Organisation - how might roles be organised by the community? - QVIZ information about a certain topic, in this case the leader would probably have to accept each submission and acts as mediator between the different viewpoints of members, etc.

In any case the question is, can it be implemented in a simple way, e.g. without having to plan for every eventuality. To answer this, the key point is that the group has to find a goal and work towards it, which goal this is doesn't matter, then an administrator is elected, this administrator stays in place until the majority of the people in this group think that the goal is reached, or until a new administrator is elected.

This administrator is obviously no official admin, but rather a spokesperson of the group, can make changes to the community resources, configuration, although he/she shouldn't have the usual admin powers, for example it would be problematic if he/she could delete the vote for the conclusion of a goal, etc.

Retrieved from "http://qviz.humlab.umu.se/index.php/Organisation_- _how_might_roles_be_organised_by_the_community%3F"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Organisation_-_how_might_roles_be_organised_by_the_community%3F (2 of 3)2006-09-29 08:50:46 Organisation - how might roles be organised by the community? - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:32, 15 September 2006. ● This page has been accessed 20 times.

http://qviz.humlab.umu.se/index.php/Organisation_-_how_might_roles_be_organised_by_the_community%3F (3 of 3)2006-09-29 08:50:46 Community and collaboration related standards - QVIZ

Community and collaboration related standards

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 1.0 Relevant publications

● 3 Social Software (SoSo) Subcluster

● 4 Conference ontology

● 5 AKT reference ontology

● 6 SIOC (Semantically Interlinked Online Communities, RDFS)

● 7 Using SKOS to describe communities (extending SIOC with SKOS)

● 8 2.1 SWRC+COIN - the community ontlogy

● 9 2.1.1 SWRC

● 10 2.1.2 COIN

● 11 2.3 DOAP Description of a Project

● 12 Project management

● 13 People’s portal environment

● 14 3.0 Discourse

● 15 3.1 DILIGENT

● 16 SWIFT

● 17 FOAF and RSS and Communities

● 18 FOAF (Friend of a Friend)

● 19 foafNaut

● 20 Fat Cats

● 21 foafingMusic

[edit] Summary

SIOC is of primary interest and we will investigate more how SWRC,COIN, SWRC+COIN (community ontology), ARC will contribute. DILIGENT is also of interest and we must compare and investigate DILIGENT and SIOC together.

http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (1 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ SIOC, as with FOAF, is beginning to attract interest and the developer communities are active. Availability of tools for storage, visualisation, and query, especially via SPARQL, will likely continue to grow. The distributed nature of SIOC repositories is also of great interest - and again the issue of more advanced reasoning in distributed must be addressed - perhaps only simple queries are currently in mind.

Mainstream wikis do not yet support this specifications, but we recommend that QVIZ should adopt and extend the specifications. However, we also should look at the arguments to using SKOS to extend SIOC (see article http:// b4mad.net/datenbrei/archives/2006/07/22/using-skos-to-describe-communication-structures/

1.0 Relevant publications [edit]

● From the SoSo: http://sw.deri.ie/soso/publications.php

● Intelligent Community Lifecycle Support http://www.eswc2006.org/technologies/usb/proceedings-workshops/eswc2006-workshop-semantic-wikis.pdf

❍ See also ontologies mentioned such SWRC, COIN, DILIGENT

Social Software (SoSo) Subcluster [edit]

● http://sw.deri.ie/soso/projects.php (see SIOC project)

● Publications http://sw.deri.ie/soso/publications.php

The Social Software (SoSo) Subcluster at DERI, NUI Galway is part of the Semantic Web Cluster.

Social software allows people to connect, communicate or collaborate by use of a computer network. It results in the creation of shared, interactive spaces. Common examples of social software systems include discussion forums, blogs, wikis and online social networks.

The Semantic Web is a vision where data on the Web can be defined and linked so that it can be processed by machines, not just for display purposes, but for use in various applications. By utilising Semantic Web technologies in social software systems, we can create new methods for connecting people to other people and also to the information that they have created.

See SIOC

Conference ontology [edit]

● Conference ontology - can this be considered a "community" ontology or a means to extend/modify SWRC+COIN ❍ Considers persons, publications, ❍ Example see resources from ESWC conference ontology and resulting FOAF map ❍ http://www.eswc2006.org/technologies/index.php

❍ http://foafmap.net/user/28/&header=http://www.eswc2006.org/technologies/images/technologiesbanner.gif http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (2 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ

AKT reference ontology [edit]

(CS AKTive Portal & Knowledge Web portal ontology)

Note: the portal and support core ontologies are also relevant to annotation and perhaps image annotation

● Ontologies at: http://www.aktors.org/publications/ontology/

● http://knowledgeweb.semanticweb.org/semanticportal/index.jsp?content=faq.html

SWRC paper indicates that AKT is closest to it and can be mapped to AKT.

The AKT Reference Ontology has been developed by the AKT partners to represent the knowledge used in the CS AKTive Portal testbed, and consists of several sub-ontologies. These are available in four formats: OWL, OCML, Ontolingua and DAML+OIL. Due to the relative expressiveness of OCML, Ontolingua, OWL and DAML+OIL, there are aspects of the OCML/Ontolingua versions that are not captured in the OWL or DAML+OIL versions.

From the site:

● Support Ontology [OWL] http://www.aktors.org/ontology/support

● Top level ontology, providing basic definitions used by the portal ontology, including a simple representation of temporal objects.

Portal Ontology [OWL] http://www.aktors.org/ontology/portal

● The main ontology, describing people, projects, publications, geographical data, etc.

Extensions Ontology [OWL][DAML+OIL] http://www.aktors.org/ontology/extension

● An ontology of definitions which are in use, but which have not been reviewed by the AKT partners and agreed for inclusion in the portal ontology.

RDF Compatibility Ontology [OWL] http://www.aktors.org/ontology/rdfcompat

● An ontology of definitions intended to improve compatibility between the AKT Reference Ontology and RDF(S).

INCA Ontology [OWL] http://www.aktors.org/ontology/inca

● An ontology which joins the <> model with the AKT Reference Ontology. I-N-C-A

http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (3 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ Note knowledege web portal http://knowledgeweb.semanticweb.org/semanticportal/index.jsp?content=faq.html

● Person Ontology: information about people related to KWeb ● Organization: information about organization related to KWeb ● Documentation: information about publication, deliverables, slides, agendas... ● Event: information about meetings, conference, workshops... ● Project: information about KWeb network: workpackages, tasks, workloads...

SIOC (Semantically Interlinked Online Communities, RDFS) [edit]

● http://sioc-project.org/

● http://rdfs.org/sioc/

SIOC (Semantically Interlinked Online Communities) is an ontology for describing discussion forums and posts in online community sites. This includes but is not limited to: blogs, bulletin boards, mailing lists, newsgroups, etc.

Additional services and tools exist and are growing - an active community.

From the site:

SIOC provides methods for interconnecting discussion methods such as blogs, forums and mailing lists to each other. It consists of the SIOC ontology, an open-standard machine readable format for expressing the information contained both explicitly and implicitly in internet discussion methods, of SIOC metadata producers for a number of popular blogging platforms and content management systems, and of storage and browsing / searching systems for leveraging this SIOC data.

Kingsley Idehen and the people at OpenLink Software have recently integrated SIOC with OpenLink Data Spaces (ODS).

OpenLink Data Spaces allows SPARQL queries to be performed on ODS data via SIOC ontology mappings.

See SOTA Applications for Semantic Communities and Semantic repositories and other basis repository techologies

See also SWRC topics for use in SWRC

● http://ontoware.org/frs/download.php/227/swrc-swtopics_v0.3.owl

● publications ❍ The SWRC Ontology - Semantic Web for Research Communities.http://www.aifb.uni-karlsruhe.de/Publikationen/showPublikation?publ_id=1003

2.1.2 COIN [edit]

Community ontology extention of SWRC

Community of Interest

2.3 DOAP Description of a Project [edit]

● http://usefulinc.com/doap

Commonly found on the internet (html meta data reference) now to describe open source projects and persons involved. Linkage to FOAF ...

other java 5 and DOAP http://www.ontogon.com/doapamine/

Project management [edit]

http://labs.semanticweb.org/textxml/vocabulary/6 Website:

http://labs.semanticweb.org/main-vocab_browser?vocab=pm&vocab_id=6

People’s portal environment [edit]

An overview of ideas on future portals. See als www.deri.org for various portal projects

● http://www.w3.org/2001/sw/Europe/events/foaf-galway/papers/fp/peoples_portal/

http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (12 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ !http://www.w3.org/2001/sw/Europe/events/foaf-galway/papers/fp/peoples_portal/image002.jpg!

3.0 Discourse [edit]

3.1 DILIGENT [edit]

● http://ontoware.org/projects/diligentarguont

DILIGENT Argumentation Ontology helps Ontology Engineers to capture the requirements and arguments ocuring during the creation and maintainance of an ontology.

SWIFT [edit]

http://ontoware.org/projects/swift

Semantic Wiki Interchange FormaT (SWIFT). RDF Schema for full export/import of Wiki content. Currently maps \SnipSnap, \MediaWiki and \JSPWiki.

No file releases at this time. Various groups consider an interchange format for Wikis

FOAF and RSS and Communities [edit]

● FOAF spec http://xmlns.com/foaf/0.1/

● Blog entry relating FOAF and RSS - communities

http://netmesh.info/jernst/Big_Picture/foaf-in-rss.html

and his ideas a bit more condensed:

● http://rss-extensions.org/wiki/RSS-FOAF

RSS-FOAF is a proposal to incorporate social networking information into RSS feeds, by introducing a small set of new XML tags in a new namespace, like other RSS extensions do. It came out of an earlier proposal for a substantially simpler FOAF called Rsfoaf that defined an entirely new file format and that is now obsolete. It has since become clear to me that extending RSS with FOAF information would be a much more promising avenue, as RSS clients are so widespread already.

e.g.: Everybody who has an RSS reader can subscribe to a FOAF feed! You've got a new friend? Pling, I know about it, because I'm suscribed to your RSS-FOAF feed. (My RSS http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (13 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ reader may not understand the FOAF extensions, but even if it only parses standard tags, it is quite usable. See example below.)

Basically this would be a usable extension to monitor (via RSS) the development of a group.

Unfortunately the support of FOAF for groups,organizations and projects ist still under status test and unstable: http://xmlns.com/foaf/0.1/#glance

FOAF (Friend of a Friend) [edit]

Overall FOAF is relevant to communities and to domain ontologies for persons and anywhere where persons are associated to other objects such as images, publications, etc. When reusing domain ontologies, we must consider to remodel proprietary person and their relations using FOAF and its relations to other typed resources.

● http://www.foaf-project.org/

● http://www.foaf-project.org/2004/world/index.html

❍ See FAOF Map, ❍ foafNaut ● FOAF spec http://xmlns.com/foaf/0.1/

● see SOTA FOAF ❍ Relevant Ontologies and Thesauri

❍ Visualisation and Knowledge FOAF Map

❍ Image annotation

Related projects of interest to QVIZ

foafNaut [edit]

an SVG project that allows you to find friends of friends in a visual environment.

Fat Cats [edit]

The Fat Cats project displays the interconnectedness between corporations and their boards of directors in a visual environment. This screenshot, from Fat Cats, gives us a glimpse of the type of cats we can see in the SVG demo. The smallest cat is a yellow tabby on the right, while the largest is a big brown tom-cat, also visible is a glimpse of an medium sized orange cat. The size of the cat indicates the number of boards that person sits on within the corporations listed in the fatcats system. Each cat is equipped with four colored circles, green expands that cats connections, blue opens the rdf data behind the display, orange performs a Google search on the person, and red hides the cat.

foafingMusic [edit]

http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (14 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ http://foafing-the-music.iua.upf.edu/index.html

See incoming musical events in the world!

Create a FOAF profile from your Blogger account

Add geolocation to your FOAF profile

foafing the music

Def. a music recommender system, based on user's profile. This means that, depending on what you like, what you listen to, where you live, etc, you get personalized music recommendations.

Based on your FOAF profile and your listening habits, foafing the music recommends you:

similar artists to the ones you like

new music releases from iTunes, Amazon, Yahoo, etc.

album reviews from your artists and from recommended artists

MP3-blogs to download music

Podcast sessions to stream/download

Automatic creation of playlists based on (only!) audio similarity

Incoming concerts near to where person lives

Retrieved from "http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (15 of 16)2006-09-29 08:50:50 Community and collaboration related standards - QVIZ

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 12:01, 27 September 2006. ● This page has been accessed 30 times. http://qviz.humlab.umu.se/index.php/Community_and_collaboration_related_standards (16 of 16)2006-09-29 08:50:50 Gazetteers - QVIZ

Gazetteers

From QVIZ

Jump to: navigation, search [edit] What is a Gazetteer?

A gazetteer is an alphabetically-arranged list of geographical names, i.e. a place-name dictionary. Saying "alphabetically-arranged" may be a problem when the list includes names in more than one alphabet, but the big problem with this definition is that it does not say what each entry CONTAINS, only what it starts with. On this there is no general agreement, and the main <>GAZETTEER CONTENT STANDARDS<> do not agree with common sense use. This page therefore discusses what we mean by "gazetteer", and what the QVIZ project might want from a gazetteer, without discussing standards.

The gazetteers that most people use most often are the gazetteers at the back of road atlases, and these days their on-line equivalents, like Multimap: http://www.multimap.com

These simply provide a geographical location for each name, without saying anything about what is at the location. There is no <>feature type information<>, and this is why they do not meet the standards. Of course, this kind of gazetteer is basically an index to a set of maps, so you would not expect there to be much information besides a reference to a point on one of the maps.

Historically, there is a long tradition of books which are mainly gazetteers, maybe with some maps at the back, rather than books which are mainly maps with a gazetteer at the back. However, there is a lot of variation in what they contain. There are two issues, both of which matter to digital gazetteers:

(A) How do they identify locations?

This may sound simple, but there are at least five possibilities:

(1) Global coordinate systems: The traditional system is latitude and longitude. The basic problem with any global system is that the earth is a sphere but paper maps are flat, so locating a point on a map from latitude and longitude is difficult.

(2) <>National coordinate systems<>: Most European countries have defined their own national system of geographical coordinates, based on flattening their own part of the sphere. The British National Grid does this using the Transverse Mercator map projection. Although individual European countries are small enough that flattening their part of the sphere creates acceptable distortions, this is

http://qviz.humlab.umu.se/index.php/Gazetteers (1 of 4)2006-09-29 08:50:52 Gazetteers - QVIZ not true of Europe as a whole.

(3) Publication coordinate systems: as has already been mentioned, many atlases define their own particular grids and use references that only make sense within that particular book. This creates a significant problem when computerising existing publications.

(4) Location by offset: Traditional gazetteers, such as those computerised by the GB Historical GIS Project, often locate one place by the direction and distance from another place. This example is taken from Bartholomew's Gazetteer of the British Isles:

Cradley.-- par., NE. Herefordshire, 3 miles N. of Colwall ry. sta.

Colwall, par. and vil. with ry. sta., SE. Herefordshire, 3 1/2 miles NE. of Ledbury

Ledbury, market town and par. with ry. sta., Herefordshire, 13 miles SE. of Hereford and 120 miles NW. of London

In other words, if we are trying to locate Cradley on a map, we have to look at two more entries before anyone who does not know Britain well knows where to look. It is an interesting question whether this kind of location could be systematically parsed.

(5) Location by relationship: Many people, and most gazetteer content standards, would say this is not a location at all, but it is very common both in historical sources and everyday speech: "Where is Uppsala?"; "It is in Sweden". "Where is Cradley?"; "It is in Herefordshire". These locations are based on "Is Part Of" relationships, but others are possible: "Herefordshire is surrounded by Gloucestershire, Worcestershire, Shropshire, Powys and Gwent". See <>relationship typologies<>. Traditional Chinese administrative gazetteers, which date back several thousands of years, provide only hierarchical relationships: this township is part of this county which is part of this province. The same is true of the taxation records which for many countries are the earliest historical documents naming administrative areas. If we want to build gazetteers which are also ontologies, we need to include this type of "location". Of course, you can see "offset locations" as defined above as a kind of "location by relationship".

There is another set of issues about the precision of geographical locations. If the entry describes a "geographical feature" -- a house, a mountain, a lake -- it should really be described by a polygon (or even a three dimensional object). This is certainly true of administrative areas. However, most large gazetteers contain only point locations. In addition, the largest collections of point locations have usually been extracted from digital mapping, and the coordinates are often not the location of the object itself but the location of the name on the map, or the left-hand end of the name. Creating clear mapping usually requires that names be re-positioned manually away from the feature itself.

(B) How do they tell us what is at the locations?

(1) Maybe they tell us nothing! This has already been discussed.

http://qviz.humlab.umu.se/index.php/Gazetteers (2 of 4)2006-09-29 08:50:52 Gazetteers - QVIZ (2) They provide a short string of descriptive text. The above example from the Bartholomew Gazetteer described the Cradley, Colwall and Ledbury as a "parish", a "parish and village with railway station" and a "market town and parish with railway station" (expanding up the abbreviations).

(3) They provide a formal "feature type", based on a controlled vocabulary. Maybe the best known of these formal vocabularies is the Alexandria Digital Gazetteer Feature Type Thesaurus. However, using any particular controlled vocabulary limits the scope of a gazetteer. In a real sense, every entity with a physical existence on earth is a "geographical feature", so why not use a general purpose thesaurus, like the UNESCO thesaurus, rather than inventing a new one? One other problem the GB Historical GIS has to deal with was that although the descriptive gazetteers we computerised already contained the kind of feature type information shown in (2), these strings often mentioned more than one kind of feature: is Colwall a parish ("countries, 4th order divisions" in the ADL FTT (maybe!)), a village ("populated places") or a railway station ("railroad features")?

(4) They contain a LONG description. Although many of the over 90,000 entries computerised by the GB Historical GIS Project from 19th century gazetteers were short -- under 100 words, the entry in the Imperial Gazetteer (1872-6) for London contains 76,101 words. Many people would call that a book in itself, and of course if describes the history of the city as well as neighbourhoods, streets and buildings within the city. As everything has location, in a sense you can include everything in a gazetteer.

(5) More formally, something which begins as a gazetteer can form the core of a much larger data structure in which additional information is linked to each geographical entity. This is how the GB Historical GIS as a whole works, making possible the Vision of Britain web site: it defines about 50,000 administrative areas, but then links to these about 50,000 polygons defining locations, over 11 million statistical data values and, via many-to-many relationships, the 90,000 descriptive entries. Another issue affecting gazetteer content standards is how far they try to include this kind of information. The ADL gazetteer content standard can include statistical information, but lacks a mechanism for describing the wide range of variables in the GBH GIS. In practice, it seems to be designed mainly for simple population totals, which are often given in traditional gazetteers.

(Humphrey Southall)

Retrieved from "http://qviz.humlab.umu.se/index.php/Gazetteers"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

http://qviz.humlab.umu.se/index.php/Gazetteers (3 of 4)2006-09-29 08:50:52 Gazetteers - QVIZ

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 12 times.

http://qviz.humlab.umu.se/index.php/Gazetteers (4 of 4)2006-09-29 08:50:52 Gazetteer Content Standards - QVIZ

Gazetteer Content Standards

From QVIZ

Jump to: navigation, search

This is about formal standards for digital gazetteers, these days necessarily defined as some kind of XML schema. It is limited to content standards, rather than web service protocols or the feature type standards which content standards may require.

Do we need gazetteer content standards?

Most existing gazetteers do not follow any kind of standard, or try to set one. This was obviously true of traditional gazetteers published on paper, but is also true of most digital gazetteers.

This includes three particularly well-known on-line gazetteers:

(a) The Getty Information Institute's Thesaurus of Geographical Names (TGN): http://www.getty.edu/research/conducting_research/vocabularies/tgn

(b) The US Geological Survey's GNIS site, containing 2m placenames within America: http://geonames.usgs.gov/domestic/download_data.htm

(c) The National Geo-spatial Intelligence Agency (NGA)'s Gazetteer, previously known as the NIMA gazetteer, containing 4m locations for the rest of the world http://earth-info.nga.mil/gns/html

Of course, these gazetteers did not need to define a content standard precisely because each aims to BE a standard, the only resource a particular community of practice needs to use (art historians, for the TGN). We only need gazetteer content standards for interoperability, i.e. we plan a network of cooperating gazetteer servers.

However, the GNIS and NGA/NIMA gazetteers are very important to any discussion of gazetteer standards, because most researchers working on standards have NOT created their own content for their demonstration systems, they have taken existing digital content, and have usually had to use digital content that was available without payment. In practice, that mainly means GNIS and NGA/ NIMA. That in turn means that any standard they developed had to fit those datasets. THERE IS THEREFORE A LARGE DANGER THAT EXISTING STANDARDS FOR DIGITAL GAZETTEERS ARE CONSTRAINED BY THE PRACTICES OF US GOVERNMENT MAPPING

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (1 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ AGENCIES AND ARE INAPPROPRIATE TO EUROPEAN CULTURAL HERITAGE NEEDS.

Existing gazetteer content standards [edit]

This is about standards whose creators have encouraged other people to use. These are all we currently know about:

(1) Alexandria Digital Library (ADL) Gazetteer Content Standard

ADL work on gazetteer standards is remarkable because it is mostly the creation of one person, Linda Hill, now retired from the University of California Santa Barbara but still very active. Her new book is the main work on the subject: Georeferencing: The Geographic Associations of Information (MIT Press, publ. 31/10/2006; ISBN 026208354X ). The home page for the activity is at: www.alexandria.ucsb.edu/gazetteer

ADL have defined three standards:

Gazetteer Content Standard http://www.alexandria.ucsb.edu/gazetteer/ContentStandard/version3.2/GCS3.2-guide.htm

Gazetteer Feature Type Thesaurus http://www.alexandria.ucsb.edu/gazetteer/FeatureTypes/ver070302

Gazetteer Service Protocol http://www.alexandria.ucsb.edu/gazetteer/protocol

Only the first is discussed here. The ADL GCS is a large standard POTENTIALLY describing a very rich resource, but its minimum requirements are quite limited, partly so that the US government gazetteers could be used. It requires that a gazetteer entry include four "core elements" :

=> A unique identifier. Of course, any database must include this, as geographical names are seldom unique, although it may be invisible to users. This therefore does not always appear in lists of the core elements.

=> A name.

=> A geographical location, which can be a point, a bounding box or a polygon.

=> A type "selected from a type scheme of categories for places/features". This does not have to be

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (2 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ taken from the ADL feature type thesaurus, but that is required for interoperability via the service protocol.

NB if any of these is missing the resource is simply not a gazetteer. There are good arguments that the ADL GCS requires both too much and too little:

=> Is a feature type essential? "Gazetteers" in road atlases do not include them. Linda Hill is insistent that gazetteers MUST be typed, but others disagree.

=> Is a geographical location essential? This is a major issue for cultural heritage applications as we may need to include places mentioned in historical documents whose locations are unknown, and maybe locations whose existence is problematic: Camelot, Avalon, Atlantis (Camelot and Avalon feature in the British myth of King Arthur. Some would argue that Camelot is an "alternate name" for the hill fort of South Cadbury, and Avalon for Glastonbury, but these identifications are highly contested).

=> More specifically, can hierarchical and other relationships substitute for a geographical coordinate? Although the ADL GCS can include such relationships, it does not require them while it does require coordinates. This is a major issue. In cultural heritage contexts, relationships are often both easier to establish and cheaper to define. They also directly support semantic web capabilities which coordinates do not.

=> While the ADL GCS allows the inclusion of rich naming histories, including recording the dates and languages of names, but none of this is required. It is understandable that an American project relying on US federal data tends to assume all names are in English, but should language be mandatory in a European gazetteer? Even more fundamentally, should the documentary sources from which names were taken be recorded? This is a big problem if we are to use the existing gazetteers created by the Americans, or by our own national mapping agencies, as information on the provenance of names was not recorded in them -- but is this acceptable?

(2) Open Geospatial Consortium (OGC) Gazetteer Service Profile

This is the main alternative to the ADL standard. The OGC brings together the largest users of geographical information systems, including the US Department of Defence and national mapping agencies such as the British Ordnance Survey, and leading vendors of GIS solutions. The latter include both creators of mainstream database software that has been spatially-enabled (i.e. Oracle, IBM, Postgres and My-SQL, all of which now support the OGC Simple Feature Specification) and creators of specialist GIS software, such as ESRI and Map-Info). In practice, database vendors are far more enthusiastic about the OGC than GIS specialists, as up to now GIS has been characterised by customers being locked into proprietary formats associated with particular vendors, especially ESRI. The fact that the OGC changed the middle word of its name from GIS to Geospatial is significant: http://www.opengeospatial.org

The OGC have established a large suite of standards for managing and communicating spatial data,

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (3 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ designed to support a dispersed network of servers communicating via web services. In practice, the W3C has tended to endorse OGC standards. Two well known OGC standards are for GML (Geographical Mark-up Language), an XML encoding for geographical information, and Web Map Servers (WMS), which serve up raster maps which can be used as base maps by other web sites. The GB Historical GIS Project's Vision of Britain site makes extensive internal use of the WMS standard, while the ADL GCS in fact uses GML to represent locations.

The OGC Web Feature Server standard (WFS) is more relevant to discussion of gazetteers. Unlike a WMS, a WFS serves up geographical information not as a raster map but as a set of objects, or geographical features, defined as coordinates. A WFS therefore sits on top of a traditional GIS, and would usually hold objects like buildings, stretches of road, pipelines or power pylons. In other words, objects accessed via a WFS can be assumed to have location and some kind of type information, but they do not necessarily have a name -- not many power pylons have an individual name! http://www.opengeospatial.org/standards/wfs

GML, WMS and WFS are all formal specifications that have been adopted by the OGC. The OGC Gazetteer Service Protocol is, however, only a draft and for a long time did not seem to be moving towards formal adoption. Its main advocate is Rob Atkinson, of Social Change On-line in Australia, and when I met him in 2003 (?) he was not optimistic about progress. However, it was heavily revised in the summer of 2006 and more may be happening: http://www.opengeospatial.org/standards/requests/36

Crucially, the OGC GSP is designed as a "service protocol" that a Web Feature Server can implement. The original GSP seemed to do little more than allow queries to select objects within the back-end database to be selected by individual name, if they had them, but the 2006 revision seems to go further and in particular does allow for optional hierarchical relationships, which can (?) be used to narrow searches. This needs to be examined further; for example, how far does it allow for information about the histories and languages of geographical names to be accessed?

Given that the OGC has the formal support of most of the GIS industry, while the ADL work is driven mainly by one retired librarian, it may seem surprising that the ADL standards have been more widely discussed and implemented. There are three reasons for this:

(a) Most of the GIS industry is not interested in names, they care about power pylons.

(b) As noted above, traditional GIS companies have mixed feelings about the OGC. ESRI, in particular, are directly supporting the ADL work (and Linda Hill is based much closer to them than Rob Atkinson is).

(c) Until the recent revision, the OGC standard was clearly too dominated by a GIS view of the world, which is concerned with locations not semantics and other attributes of words.

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (4 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ

NB since the recent revision, the OGC and ADL standards look pretty similar. Ian Turton, who worked on both the Vision of Britain web site and reference implementations of the WFS standard for the OGC believed that the ADL protocol could also be implemented on top of a WFS, and had started work on this. There is a good argument that both standards are too heavily based on a GIS view of the world.

(3) International Standards Organisation ISO19112, "Spatial referencing by geographic identifiers" : http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26017

This is more abstract than the standards discussed up to now. The OGC Gazetteer Service Protocol aims to implement it.

(4) SPIRIT

This project funded by the EU Fifth Framework researched Spatial Information Retrieval and Geographical Ontologies. In particular, they re-defined the ADL WCS in OWL.

(5) Encoded Archival Context

The standards discussed up to now all come out of some combination of GIS and librarianship/ information science, but QVIZ is focused on the needs of the archives sector. EAC is a standard developed by archivists for name authorities, and is therefore designed to cover place-names as well as personal names and corporate names. http://www.library.yale.edu/eac

The GB Historical GIS project was directed by the UK National Archives to support EAC in our work, and the Swedish National Archives were also involved in the development of EAC, but there are two major problems:

(a) EAC provides a rich framework for describing the development of names, but does not allow for the inclusion of geographical locations.

(b) It is unclear how far EAC is being adopted by the archives sector.

(Humphrey Southall)

Retrieved from "http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards"

Views

● Article

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (5 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006.

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (6 of 7)2006-09-29 08:50:54 Gazetteer Content Standards - QVIZ

● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/Gazetteer_Content_Standards (7 of 7)2006-09-29 08:50:54 Gazetteer Feature Types - QVIZ

Gazetteer Feature Types

From QVIZ

Jump to: navigation, search

WHAT KINDS OF ENTITY/OBJECT/GEOGRAPHICAL FEATURE SHOULD GAZETTEERS COVER?

The two main gazetteer content standards, from ADL and OGC, both require that every item in a gazetteer have a "feature type", so you cannot just have "places" -- and the gazetteers in road atlases are not gazetteers!

The ADL gazetteer content standard allows each individual gazetteer record to specify the feature "classification schemes" which it uses . However, the ADL project also developed a Gazetteer Feature Type Thesaurus (FTT) as their preferred classification scheme, and any gazetteer designed to inter-operate with the ADL gazetteer via the ADL gazetteer service protocol must use the ADL FTT: http://www.alexandria.ucsb.edu/gazetteer/FeatureTypes/ver070302

The OGC Gazetteer Service Profile does not specify a particular feature classification. It is designed to work on top of an OGC Web Feature Server, and a capabilities request to a WFS returns a list of the feature types that particular server supports, specified using GML.

LIMITATIONS OF THE ADL FEATURE TYPE THESAURUS [edit]

Although proposed by ADL as a general solution, the ADL FTT has been widely criticised, and the Electronic Cultural Atlas Initiative have tried to develop an alternative.

The current (2003) version of the ADL FTT includes 210 preferred terms. Of these, 102 define physical features -- mountains, rivers, seas, etc -- and 76 define man-made structures, leaving 32 terms defining "areas" and "regions" of one kind or another. In other words, this is basically a classification of the kind of geographical features that appear on conventional landscape maps. Linda Hill has said that the ADL FTT was derived mainly from the symbologies used on US Geological Survey topographical maps.

As far as we know, the ADL FTT exists in just the one English language version. Many of the terms used, however, are in common English usage in the US but not elsewhere: levees, arroyos, etc. The Geo-X-walk project proposed some revised terminology, although this has not been adopted by ADL:

http://qviz.humlab.umu.se/index.php/Gazetteer_Feature_Types (1 of 4)2006-09-29 08:50:55 Gazetteer Feature Types - QVIZ http://www.geoxwalk.ac.uk/thesaurus.html

The larger problem with the ADL FTT is that it makes very little provision for administrative units; most of the kinds of area it defines either have a special purpose, such as "school districts" or "military areas", or are the kinds of "region" defined by academic studies: "biogeographic regions", "economic regions". This leaves just six terms for classifying the items in a gazetteer of administrative units, within the broader category of "political areas":

. . countries

. . countries, 1st order divisions

. . countries, 2nd order divisions

. . countries, 3rd order divisions

. . countries, 4th order divisions

. . multinational entities

This may well be sufficient for the United States, which has a uniform and historically static system of administrative areas, essentially states, counties and townships; an additional category is left available for ad hoc urban units.

This set of terms is, however, clearly totally inadequate for a European gazetteer/ontology of administrative units. One key point is that while the "feature typing" in a topographic maps is a task for the map-maker, the "type" of an administrative unit is usually defined by law. In the GB Historical Gazetteer, behind the Vision of Britain site, 28 "unit types" are currently defined, but 13 of these types are further divided up by "status", with 70 different status values available. Although Estonia and Sweden are not as complicated as this, we already have more than four kinds of internal sub-division for each country and more may well arise in the course of the project.

It is of course possible to map more complex typologies of administrative units to the ADL scheme, and precisely this is done in the GBH system, so it could participate in a network of ADL servers. However, the ADL FTT is clearly unusable as the NATIVE typology for a European historical gazetteer/ontology of administrative units, and as a result users accessing the system via a special interface could learn more than those accessing it remotely via the ADL gazetteer service protocol: http://www.visionofbritain.org.uk/types

KINDS OF GAZETTEER [edit]

This discussion of gazetteer feature typing leads to a wider conclusion: that administrative unit

http://qviz.humlab.umu.se/index.php/Gazetteer_Feature_Types (2 of 4)2006-09-29 08:50:55 Gazetteer Feature Types - QVIZ gazetteers/ontologies are a different kind of gazetteer from gazetteers of "geographical features", which the ADL project has done a good job of defining:

=> Administrative units are NOT geographical features: you cannot see boundaries in the real world (although they often follow features you can see).

=> Administrative units are corporate bodies, created, named, delineated, altered and abolished through legal processes. Geographical features are _recorded_ by map makers, but administrative boundaries are then drawn on to maps by politicians and civil servants (and sometimes soldiers).

=> The earliest written records containing geographical names for many countries are taxation records which list administrative units such as parishes and manors, not towns and villages.

=> Administrative units generally take their names from geographical features. These are most often settlements, but current districts in Britain include "Epping Forest", "Staffordshire Moorlands" and "Malvern Hills".

Even if most research concentrates on constructing gazetteers of geographical features, at least three major "communities of practice" have a clear requirement for detailed administrative unit gazetteers/ ontologies:

=> Users of statistics, including historical demographers. Statistics can only be gathered for clearly defined entities, and in most countries reporting is by administrative unit rather than special purpose census areas. In practice, census reports can often be used as a kind of gazetteer.

=> Archivists, whose primary concern is often the records of government including local administration: administrative units matter because they are creators of records.

=> Genealogists, the largest single category of archive USER. They have a particular need to identify parishes and other units with which records about their ancestors are likely to be linked.

It is therefore inevitable that large gazetteers not based on the ADL FTT, or anything like it, will be built.

(Humphrey Southall)

Retrieved from "http://qviz.humlab.umu.se/index.php/Gazetteer_Feature_Types"

Views

● Article

● Discussion

http://qviz.humlab.umu.se/index.php/Gazetteer_Feature_Types (3 of 4)2006-09-29 08:50:55 Gazetteer Feature Types - QVIZ

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:05, 15 September 2006. ● This page has been accessed 16 times.

http://qviz.humlab.umu.se/index.php/Gazetteer_Feature_Types (4 of 4)2006-09-29 08:50:55 Administrative Unit typologies in VoB and Qviz - QVIZ

Administrative Unit typologies in VoB and Qviz

From QVIZ

Jump to: navigation, search

How we build our own system.

(1) Administrative units HAVE types, and we have to record those existing types, not invent our own typology. However, there is still a big question about how we arrange those existing legally-defined types.

(2) We have two problems with language. One is that this project is working across countries which use many different languages, and although the project works entirely in English I am not sure EXACTLY what is meant when Swedes and Estonians used words like "county", "parish" and "manor" (but Paula is finding out). The other is that within the system I am about to describe, our existing British system, the words "level", "type" and "status" have precise meanings, so from now on I will try to remember to use a spare word, "kind", when I do not mean one of those precise terms.

(3) What we are doing in QVIZ is not so very different from what we did for Britain, because for Britain we took four different existing resources and merged them into one single database. I could say much more about our sources, but what I will say quickly is that we had a very detailed book that covered England, a less detailed book for Wales, a database created by the Scottish national archives for Scotland, and an additional database created by the main national archives in London listing just manors for England and Wales.

(4) What we ended up with was a typology which we present as a thesaurus, but has just four fixed tiers, and the tiers behave in different ways. It is presented here: http://www.visionofbritain.org.uk/types

(5) The top tier are the six kinds of "political area" in the ADL feature type thesaurus, but these are not enough to describe British administrative geographies so we have as our next tier "geographical levels", of which we have 9. The result looks like this: political areas

. . multinational entities

. . . . Root

. . countries

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (1 of 6)2006-09-29 08:50:57 Administrative Unit typologies in VoB and Qviz - QVIZ

. . . . State

. . countries, 1st order divisions

. . . . Nation

. . . . Administrative Region

. . countries, 2nd order divisions

. . . . County

. . countries, 3rd order divisions

. . . . Higher-level District

. . . . Lower-level District

. . countries, 4th order divisions

. . . . Parish

. . . . sub-Parish

"Root" covers just one unit, the British Isles, which turns out to contain five "states". Most people know about the UK and the Irish Republic, but legally the Isle of Man, Jersey and Guernsey are independent states which happen to have the same queen as the UK; they are not parts of the European Union! "Nation" covers the parts of the UK: England, Wales, Scotland and Northern Ireland. Generally, "Administrative Region" is used to cover various big sub-divisions of England. "Districts" covers all sorts of geographies that divide up counties into groups of parishes, but several geographies involve two levels between counties and parishes; for example, the ecclesiastical system involves "Archdeaconries" and "Rural Deaneries". Modifying this system to cover Europe probably needs two more levels: the world at the top, then continents, then sub-continental aggregates which would include both "Scandinavia" and "British Isles", i.e. the current root. NB capturing Europe's colonial history means I think we have to include the world as a whole, and there are currently the French overseas departments, which may be legally simply parts of France but are not in Europe.

(6) These geographical levels are NOT types. For example, the level "Higher-level district" currently contains 5 types:

. . . . Higher-level District

...... Poor Law Union/Reg. District

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (2 of 6)2006-09-29 08:50:57 Administrative Unit typologies in VoB and Qviz - QVIZ

...... Division of Ancient County

...... Archdeaconry

...... District/Unitary Authority

...... 1841 Occupation reporting area

Our "types" are the key element in this typology, and they are what are recorded in the unit records: every unit has a type, and only one type so they cannot change. We define types in GIS terms: a type is like a coverage in ArcInfo, and selecting all the units of one type, or at least all those which existed at a given date, should give you a map of the whole country. We define types this way whether or not we have actual boundary polygons for them. We obviously have a table which defines what types exist, and if we do have polygons for some of the units in a type we hold a bounding box for the type in the type definition. This matters because some types cover Great Britain as a whole while others cover only England and Wales or only Scotland (so we are already most of the way to being able to hold "types" that cover only Sweden or only Estonia). Some types do not cover the whole country, and that is in fact true of the modern system of counties; there is a lower level of districts, but we also have "unitary authorities" which are basically districts which also have the powers of counties. That explains this map of 2001 census data: http://www.visionofbritain.org.uk/maps/data_map_page.jsp?data_theme=T_POP& data_rate=R_POP_DENS_H&data_year=2001&date_type=1Y&u_type=MOD_CNTY&scanned Map=none

(7) Our 28 types are still not nearly enough to cover all the different kinds of unit that existed, so we have one further tier in the typology: status. Status values are held in a child table, so the rules are much more flexible: some types do not have any associated status values; with some types, some units have associated status values but others do not; some types can have several status values at the same time, while others have only one status value but this can change over time. A good example is the system of "local government districts" which existed in England and Wales between 1894 and 1974. We define "local government district" (LG_DIST) as a type, and define it as having the geographical level "lower-level district". It then has 7 associated status values:

...... Metropolitan Borough

...... Municipal Borough

...... Urban District

...... Rural District

...... County Borough

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (3 of 6)2006-09-29 08:50:57 Administrative Unit typologies in VoB and Qviz - QVIZ

...... London City Corporate

...... London Borough

You may think that by now we are down at such a detailed level that the differences between these cannot matter, but this is far from true. Firstly, you need to know the status to identify the correct unit, as for almost every Rural District there was an Urban District, Municipal Borough or County Borough in the same county with the same name: the system was created out of an earlier system in which the country was divided up into districts centered on a market town, and named after it. In the system created in 1894, the districts were divided into an urban core and a surrounding Rural District, still usually named after the market town but NOT including it. Urban Districts, Municipal Boroughs and County Borough all covered towns, but their powers varied; for example, only County Boroughs ran their own schools. As a result, towns tried to raise their status, so over time you see them getting raised from Urban District to Municipal Borough, and from Municipal Borough to County Borough. London had a separate system which was revised in 1965: before you have Metropolitan Boroughs; after you have London Boroughs which were much bigger. Finally, the City of London -- the square mile in the middle -- has a unique system of government, which is why it is the only unit with "London City Corporate" status.

(8) I am not simply ASSUMING we will use the same data model for QVIZ, but so far I have seen no reason why we cannot, while my previous e-mail pointed out clear reasons why a system based more closely on the ADL model would not work; NB this is because our architecture already has to handle two quite separate administrative geographies, Scotland having a different history and legal system from England and Wales, as well as at least two languages, Welsh and English. The most obvious way to add the kinds of unit we are learning about from other countries is to include them as additional "types". The system would still know that one type of unit which only existed in Sweden was roughly equivalent to another type in England because they would be assigned to the same "geographical level", and of course if the data structure was accessed via an ADL server using our mappings to the ADL FTT the units' types would be exactly the same. The really detailed investigation of the Swedish and Estonian data that Paula is doing in collaboration with partners is going well, and reasons for starting to use status values are emerging.

(9) Because units can have multiple concurrent or consecutive status values, held in a child table, narrowing searches by status works a bit differently from narrowing searches by geographical level or type, and the results can appear incorrect: specifying that a unit must have the status "Urban District" does not exclude units with the status "Municipal Borough".

(10) An obvious result of the enormously complex history of British administrative geography is that you cannot say, for example, that Reading in Berkshire IS a County Borough: many different administrative units have been based on this town, and we currently list 14: http://www.visionofbritain.org.uk/place/place_page.jsp?p_id=846

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (4 of 6)2006-09-29 08:50:57 Administrative Unit typologies in VoB and Qviz - QVIZ The same is true of most villages of any size: they have both a civil and an ecclesiastical parish, with different boundaries, plus maybe a manor, all with the same name. We have dealt with this by grouping units together into places, based on similar location AND similar name. This grouping has been done in software, and it is surprisingly hard to get right; having to deal with names in different languages would make it harder. There is no current plan to do this for QVIZ, but it does make this kind of gazetteer easier to understand by ordinary people. Searching by name from the Vision of Britain home page actually uses the same table of geographical names as our more specialised "administrative unit search", but it takes you to "place" pages like the one above. The list of the 14 associated units is at the bottom of the page.

(11) What we do not currently record is the function or role of particular units. For example, from the list in (6) archdeaconries were church units while "1841 Occupation reporting area" were not administrative units at all, just units used in census reports; there is in fact a flag which identifies purely statistics units. We do record, in the table of type definitions, the dates when the types as a whole was created, by law, and when it was abolished.

(Humphrey Southall)

Retrieved from "http://qviz.humlab.umu.se/index.php/ Administrative_Unit_typologies_in_VoB_and_Qviz"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (5 of 6)2006-09-29 08:50:57 Administrative Unit typologies in VoB and Qviz - QVIZ

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 13:53, 15 September 2006. ● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/Administrative_Unit_typologies_in_VoB_and_Qviz (6 of 6)2006-09-29 08:50:57 Timeless access to time-spatial admin unit information - QVIZ

Timeless access to time-spatial admin unit information

From QVIZ

Jump to: navigation, search

Timeless access to time-spatial information: timeless access.pdf

http://qviz.humlab.umu.se/index.php/Timeless_access_to_time-spatial_admin_unit_information (1 of 3)2006-09-29 08:50:59 Timeless access to time-spatial admin unit information - QVIZ

Retrieved from "http://qviz.humlab.umu.se/index.php/Timeless_access_to_time- spatial_admin_unit_information"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

http://qviz.humlab.umu.se/index.php/Timeless_access_to_time-spatial_admin_unit_information (2 of 3)2006-09-29 08:50:59 Timeless access to time-spatial admin unit information - QVIZ

● Printable version

● Permanent link

● This page was last modified 09:31, 19 September 2006. ● This page has been accessed 12 times.

http://qviz.humlab.umu.se/index.php/Timeless_access_to_time-spatial_admin_unit_information (3 of 3)2006-09-29 08:50:59 Relevant ADL - QVIZ

Relevant ADL

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 1.0 Ontologies exploiting ADL (only relevant to QVIZ)

● 4 1.1 Proton Onology

● 5 2.0 ADL Projects

● 6 2.1 The Alexandria Digital Library

● 7 2.1.1 Gazetteer Service Protocol

● 8 2.2.2 ADL Feature Type Thesaurus (ADL FTT)

● 9 2.2.3 How to cite the ADL Gazetteer

● 10 2.2.4 Citation

● 11 Publications

● 12 2.3 ADL Software

● 13 2.4 Vision of Britain's Administrative Units Typology and the Alexandria Digital Library's Feature Type Thesaurus.

[edit] Summary

Here we report about ADL resources, relevance to QVIZ, and software available that we might exploit. Also, we indicate schemas or ontologies that have exploited ADL that might be of interest to QVIZ (we do not report all)

Background [edit]

...

1.0 Ontologies exploiting ADL (only relevant to QVIZ) [edit]

1.1 Proton Onology [edit]

http://qviz.humlab.umu.se/index.php/Relevant_ADL (1 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ Exploits ADL, but not entirely. No temporal information seems to be used either. Created by the SEKT project, used by OWLIM repository and TREEE engine (reasoner, query engine)

2.0 ADL Projects [edit]

2.1 The Alexandria Digital Library [edit] http://www.alexandria.ucsb.edu/research/index.htm http://www.alexandria.ucsb.edu/research/kos/ index.htm http://www.alexandria.ucsb.edu/ http://www.alexandria.ucsb.edu/gazetteer/

The Alexandria Digital Library

System Architecture http://www.sbg.ac.at/geo/eogeo/authors/frew/frew.htm

New - Gazetteer Server Client 2004-06-03

A new client for the ADL Gazetteer has replaced the former "new client" for the ADL Gazetteer Server. The new client retains the basic look and functionality of the original interface, but underneath it has been completely redesigned. It is now based on version 1.2 of the ADL Gazetteer Protocol, on version 3.2 of the Gazetteer Content Standard, and on a new PostGres database implementation. This new client points not only to the ADL Gazetteer, but also to the ESRI gazetteer. Please try it out and use the Problem Report or the Comment link to send us feedback. Gazetteer Content Standard, version 3.2, and its relational database model - 2004-02-26

This version of the Gazetteer Content Standard (GCS) includes significant changes from the original GCS. The revision process has now been frozen for this release. A logical relational database model has been developed for this version and has been implemented by ADL in PostGreSQL. See the Guide to the ADL Gazetteer Content Standard for more information, including XML schemas, graphics of database tables, and sample full and minimum records.

Specific links to the original version of the Gazetteer Content Standard have been removed from this page but can still be accessed through person contact with ADL.

2.1.1 Gazetteer Service Protocol [edit]

Version 1.2 of the ADL Gazetteer Service Protocol has been published, along with sample code for a Java client. This specification supports remote query and response functions for distributed digital

http://qviz.humlab.umu.se/index.php/Relevant_ADL (2 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ gazetteers and has been developed in collaboration with ESRI. On the referenced page, there are also two links to test forms. The Hands-on Introduction provides various types of queries for demonstration and experimentation; the Test Forms provide tests of the various protocol functions for validation and debugging.

New - Correlation data relating words/phrases in placenames to associated classification terms from three typing schemes - 2004-06-03

Dr. Jun Wang, with the assistance of his students with the Information Management Department of Peking University, recently completed an analysis of the 5.9 million names in the ADL Gazetteer and their association with the feature type classifications from three independent typing schemes: all of the names are associated with one or more terms from the ADL Feature Type Thesaurus and portions of the names are associated with either the gazetteer type terms from the U.S. Geological Survey or from the U.S. National Geospatial-Intellegence Agency (formerly NIMA).

This data can be explored by downloading the client they developed: http://www.alexandria.ucsb.edu/ downloads/gaz/ADLGazetteerCorrelationAnalysis.zip.

Please note that the client was developed in C#, hence it needs Microsoft .NET framework V1.1 and Microsoft Data Access Component, both of them can be downloaded from Microsfot website: http:// msdn.microsoft.com/netframework/technologyinfo/default.aspx and http://www.microsoft.com/ downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en

For a view of what the data looks like, here is a screen shot of the client. On the left is a list of placename "tokens" that are 1 word in length, in order by frequency of occurrence in the ADL Gazetteer. The most frequently occurring word is "School". This word is selected and on the right are the associated feature type terms from the three schemes; the percentage values indicate the strength of relationship between placenames containing the word "School" and the particular feature type term.

We are interested in using this data to explore ways of assisting the process of assigning feature type terms to gazetteer entries and in extending type-based searching across independent, distributed gazetteers. The data also supports a form of term mapping between the classification schemes.

Licensing agreement for ADL gazetteer services and gazetteer data

ADL announces that it is prepared to license the ADL Gazetteer Services and Gazetteer Database and to establish affiliations with commercial and institutional organizations to further the advancement of gazetteers and related services and research. For more information, contact Larry Carver or Linda Hill. Gazetteer discussion list

We have established a listserv for the discussion of gazetteer design, implementation, and research. The name of it is CGGR-L; it is hosted by UCSB's Center for Global Georeferencing Research. To subscribe, address your email to [email protected], leave the subject line blank, enter

http://qviz.humlab.umu.se/index.php/Relevant_ADL (3 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ subscribe cggr-l [your name] in the body of the message (note: the "-l" stands for "-list") and send the message. The archives for the CGGR-L are hosted by the NSF.

List of 5.9 million geographic names available for download

The ADL Project has created a list of all of the names, both primary and alternative names, from its ADL Gazetteer and is making it available for download and local use within the limits of our copyright statement. We anticipate that the list will be useful for geoparsing applications where geographic names need to be identified in natural language text. Each entry in the list, one line per entry, consists of (1) the ADL Gazetteer Identifier for the entry associated with the name; (2) the name; (3) the date of entry into the database.The ADL Gazetteer Identifier for particular entries can be used with the Gazetteer Service Protocol to retrieve standard reports for the entry. The size of the compressed file is 55.1 Mbytes; uncompressed it is approximately 263.7 Mbytes.

This file contains the ADL copyright statement and the compressed file of geographic names. If you are having trouble downloading because the file is large and transmission is interrupted, you might want to get the free HTTP/FTP client that can resume interrupted downloads where they leftoff, instead of having to start over. We would appreciate hearing from those who put the file to use.

2.2.2 ADL Feature Type Thesaurus (ADL FTT) [edit]

ADL Feature Type Thesaurus: A set of terms for categories of geographic places; terms to indicate the nature of a place. It has been designed to be used with the Alexandria Digital Library (ADL) Gazetteer at http://www.alexandria.ucsb.edu/gazetteer/

Thesaurus: A set of terms representing concepts and the relationships among the terms, including hierarchy, equivalence, and associative relationships.

2.2.3 How to cite the ADL Gazetteer [edit]

For a general citation to the ADL Gazetteer, use:

Alexandria Digital Library Gazetteer. 1999- . Santa Barbara CA: Map and Imagery Lab, Davidson Library, University of California, Santa Barbara. Copyright UC Regents. http://www.alexandria.ucsb.edu/gazetteer (ADL Gazetteer Development page with links to various clients and protocols that access the ADL Gazetteer).

To cite gazetteer data from a particular use of the ADL Gazetteer, use:

Alexandria Digital Library Gazetteer. 1999- . Santa Barbara CA: Map and Imagery Lab, Davidson Library, University of California, Santa Barbara. Copyright UC Regents. [URL of the client or server used]. Accessed [the date the data was obtained].

http://qviz.humlab.umu.se/index.php/Relevant_ADL (4 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ

2.2.4 Citation [edit]

To cite a particular piece of data from the ADL Gazetteer, use:

[Primary name (adlgaz-1-.....)]. Alexandria Digital Library Gazetteer. 1999- . Santa Barbara CA: Map and Imagery Lab, Davidson Library, University of California, Santa Barbara. Copyright UC Regents. [URL of the client or server used]. Accessed [the date the data was obtained].

Publications [edit]

Hill, L. L. (2004, May). Georeferencing in digital libraries (guest editorial). D-Lib Magazine, 10 (5). http://www.dlib.org/dlib/may04/hill/05hill.html (All of the articles in this issue refer to the role of gazetteers in georeferencing applications).

Hastings, J., & Hill, L. L. (2002, September 25-28). Treatment of "Duplicates" in the Alexandria Digital Library Gazetteer. Paper presented at the GeoScience 2002, Boulder, Colorado. Powerpoint presentation.

Hill, L. L. (2000). Core elements of digital gazetteers: placenames, categories, and footprints. In J. Borbinha & T. Baker (Eds.), Research and Advanced Technology for Digital Libraries : Proceedings of the 4th European Conference, ECDL 2000 Lisbon, Portugal, September 18-20, 2000 (pp. 280- 290). Berlin: Springer. PDF file.

Hill, L. L., Frew, J., & Zheng, Q. (1999). Geographic names: The implementation of a gazetteer in a georeferenced digital library. D-Lib (January 1999). HTML file.

Hill, L. (1999). Gazetteer and collection-level metadata developments. In R. T. Kaser & V. C. Kaser (Eds.), Metadiversity. The Grand Challenge for Biodiversity Information Management through Metadata. The Call for Community. Proceedings of the Symposium sponsored by the U.S. Geological Survey Biological Resources Div. & the National Federation of Abstracting & Information Services (pp. 141-145): NFAIS. HTML file.

Hill, L. L., & Zheng, Q. (1999). Indirect geospatial referencing through place names in the digital library: Alexandria Digital Library experience with developing and implementing gazetteers. Proceedings of the American Society for Information Science Annual Meeting, Washington, D.C., Oct. 31- Nov. 4, 1999, pp. 57-69. PDF file.

2.3 ADL Software [edit]

Software http://www.alexandria.ucsb.edu/research/kos/index.htm

http://qviz.humlab.umu.se/index.php/Relevant_ADL (5 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ ADEPT Project

Directory of downloadable files for Alexandria Digiral Libary Project. adllibrary -- a standalone version of the adl library software

which uses Apache Tomcat. Requires Java online demo: see webclient webclient -- a developers version of the ADL middleware, plus a

web-based client interface. Requires: Java, Apache Ant, Java App

Server (aka tomcat) online demo: http://webclient.alexandria.ucsb.edu/ middleware -- codebase for ADL middleware

Requires: Java programming online demo: see webclient gazprotocol -- developers version of the ADL

Gazetteer Protocol

server. Requires: Java, Apache Ant, Java App

Server (aka tomcat) online demo: underlies demo running on:

http://testbed.alexandria.ucsb.edu:8080/gazclient/ thesaurus -- Java Application server webapp and associated code

for the thesaurus protocol server. online demo: none at present.

[edit]

http://qviz.humlab.umu.se/index.php/Relevant_ADL (6 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ 2.4 Vision of Britain's Administrative Units Typology and the Alexandria Digital Library's Feature Type Thesaurus.

The Vision of Britain (VoB) system for classifying British administrative units, known as the Administrative Units Typology, is designed as an extension to the Alexandria Digital Library's gazetteer Feature Type Thesaurus (ADL FTT) and was created after discussions with the team in Santa Barbara. The ADL FFT only contains four terms for intra-state political units so the VoB typology had to be adjusted to suit the history of the hierarchy of British Administrative units.

Firstly there is expansion from ADL FFT's four to VoB's seven Geographical Levels. The next expansion is to VoB's Unit Type values, and the final one is to VoB's type-specific Unit Status values ('World', 'State' and 'Nation' are both Geographical Levels and Unit Types). NB a given type of unit may hold more than one status value concurrently.

By selecting an entry from the list of units within the typology various details about the individual unit type within VoB will be displayed. It identifies which ADL feature type the unit is aligned with, gives information about the hierarchic relationships the unit type can have and the status values applicable to the unit type. It also indicates which VoB geographical level the unit type relates to, briefly explains the history of the unit type as well as the standard identifying information. This also applies to all the status values.

See the Vision of Britain Administrative Units Typology: http://www.visionofbritain.org.uk/types/index.jsp

Retrieved from "http://qviz.humlab.umu.se/index.php/Relevant_ADL"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

http://qviz.humlab.umu.se/index.php/Relevant_ADL (7 of 8)2006-09-29 08:51:01 Relevant ADL - QVIZ

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 10:56, 19 September 2006. ● This page has been accessed 9 times.

http://qviz.humlab.umu.se/index.php/Relevant_ADL (8 of 8)2006-09-29 08:51:01 Digital Objects and Library Standards - QVIZ

Digital Objects and Library Standards

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Digital Library Standards

● 3 OAI

● 4 Digital libraries

[edit] Summary

Digital Library Standards [edit]

Library of Congress http://www.loc.gov/standards/

● METS (Metadata Encoding & Transmission Standard) - Structure for encoding descriptive, administrative, and structural metadata (http://www.loc.gov/mets)

❍ Digital Object Metadata

● MIX (NISO Metadata for Images in XML) - XML schema for encoding technical data elements required to manage digital image collections http://www.loc.gov/mix/

OAI [edit]

Dublin Core

Digital libraries [edit]

See DSPACE, FEDORA uses METS, OAC,etc

Retrieved from "http://qviz.humlab.umu.se/index.php/Digital_Objects_and_Library_Standards"

Views

http://qviz.humlab.umu.se/index.php/Digital_Objects_and_Library_Standards (1 of 3)2006-09-29 08:51:02 Digital Objects and Library Standards - QVIZ

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/Digital_Objects_and_Library_Standards (2 of 3)2006-09-29 08:51:02 Digital Objects and Library Standards - QVIZ

● This page was last modified 10:29, 21 September 2006. ● This page has been accessed 7 times.

http://qviz.humlab.umu.se/index.php/Digital_Objects_and_Library_Standards (3 of 3)2006-09-29 08:51:02 Relevant Ontologies and Thesauri - QVIZ

Relevant Ontologies and Thesauri

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 Ontology sites

● 4 IMS Learning

● 5 Thesauri Sites

● 6 Bibliographic

● 7 SKOS - Knowledge Organisation System

● 8 SKOS Overview

● 9 SKOS Thesauri Specific to Archives

● 10 SKOs & Topic Map issues

● 11 DDC Dewey - SKOS

● 12 Software

● 13 GSAFD — Guidelines on Subject Access to Individual Works of Fiction, Drama, etc.

● 14 Terminology services

[edit] Summary

TODO reorganise ontologies in other pages, such as the community, annonation, image pages. We should eventually have one page???

Background [edit]

Semantic Web

● http://en.wikipedia.org/wiki/Semantic_Web

● Semantic web overview and controlled vocabularies including SKOS http://computer.howstuffworks.com/semantic-web.htm/printable

Ontology sites [edit]

● http://www.schemaweb.info/

❍ See also geo related, domain relevant ● http://simile.mit.edu/repository/ontologies/index.html

❍ See also geo related ● http://protege.stanford.edu/plugins/owl/owl-library/

● http://www.ontoware.org

Domains consider publishing and eLearning

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (1 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ

● SWRC, COIN, bibtext ● Industry based publishing ontologies such as http://www.schemaweb.info/schema/SchemaDetails.aspx?id=271 An ontology used by Mondeca ITM for the publishing industry, including concepts used for thesaurus and taxonomy management and automatic index generation. ❍ Conference ontology - can this be considered a "community" ontology or a means to extend/modify SWRC +COIN ■ Considers persons, publications, ■ Example see resources from ESWC conference ontology and resulting FOAF map ■ http://www.eswc2006.org/technologies/index.php

■ http://foafmap.net/user/28/&header=http://www.eswc2006.org/technologies/images/technologiesbanner. gif

Examples

* DC - Dublin Core * DCT - Dublin Core Terms * DC collections (not yet RDF based) * IMSMD - IMS Learning Object Metadata Vocabularies ** lom - learning object metadata ** lom-tech - lom technical metadata ** lom-edu - lom educational metadata ** lom-gen - lom general metadata **lom-life - lom lifecycle metadata ** see http://www.imsproject.org/rdf/ * FOAF - Friend of a Friend * WordNet - WordNet Ontology * CIDOC-CRM - CIDOC Conceptual Reference Model * Doc - Ontology to Describe Documents * VRA - VRA Core3 * artstor - Ontology for Artstor Metadata * ocw - Ontology for MIT OpenCourseWare Metadata * person - Simple Person Ontology * oclc - Ontology for the OCLC Authority Metadata * skosext - Extension to the SKOS Ontology for URI dereferenceable terms * via - Ontology for Harvard VIA Metadata * "display configuration example": http://simile.mit.edu/2004/01/ontologies/ display

IMS Learning [edit]

IMS Resource Description Framework(RDF) Bindings http://www.imsproject.org/rdf/

The following files contain RDF documents that aid in the implementation of the sample RDF binding contained in the IMS Meta-data 1.2 specification. Please note that the RDF binding of IMS meta-data is work in progress and subject to change. You may look at the latest drafts.

The RDF binding of IMS Meta-data 1.2 specification references the following nine RDF schemas, that are used for validation and extensions.

* imsmd_rootv1p2

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (2 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ

* imsmd_generalv1p2 * imsmd_lifecyclev1p2 * imsmd_metametadatav1p2 * imsmd_technicalv1p2 * imsmd_educationalv1p2 * imsmd_rightsv1p2 * imsmd_relationv1p2 * imsmd_annotationv1p2 * imsmd_classificationv1p2

The following files contain an example RDF meta-data instance, including language definitions, a local taxonomy and a local vocabulary.

* lom-rdf1.rdf * lang.rdf * taxon.rdf * vocab.rdf

Thesauri Sites [edit]

1. Controlled Vocabularies 1. Definitions 1. http://en.wikipedia.org/wiki/Controlled_vocabulary 2. Taxonomy 2. Sites 1. Dublin Core 2. NSDL Registry 1. GEM-SKOS -- GEM vocabularies in SKOS version includes Teaching methods, subject, resource, etc 2. GEM-OWL -- GEM vocabularies in OWL version. 3. GEM-Mapping -- Mapping Documents for Resource Type and Level Vocabularies 4. NSDL Resource Type 5. ENCdl Vocubularies 6. Animal Behavior Vocabulary (CoP Archivists in Sweden who like Moose?) 7. KMODDL Vocabulary 3. http://www.oclc.org/research/projects/termservices/ 4. Controlled vocabularies

This page provides links to examples of thesauri and to classification schemes that may be used for controlling database or WWW site subject content. It also provides links to descriptive and critical material about such metainformation.

1. Folsonomies 1. Folksonomy at http://en.wikipedia.org/wiki/Folksonomy 2. "folksonomies + controlled vocabularies":http://many.corante.com/archives/2005/01/07/ folksonomies_controlled_vocabularies.php 3. Ontology 1. http://en.wikipedia.org/wiki/Ontology 2. Ontology 101 1. Ontology 101 Classic

Natalya F. Noy and Deborah L. McGuinness. ``Ontology Development 101: A Guide to Creating Your First Ontology. Stanford Knowledge Systems Laboratory Technical Report KSL-01-05 and Stanford Medical Informatics Technical Report SMI-2001-0880, March 2001.

1. http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (3 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ

html

Bibliographic [edit]

● See Fast and LCSH ... look at SKOS ❍ http://www.oclc.org/research/projects/fast/

● See SWRC and COIN, AKT, Bibtex in owl

SKOS - Knowledge Organisation System [edit]

Focus on SKOS format for thesauri.

Critical to address archivists and "users" of archives, therefore UKAT must be used and setup for multilingual use. Some control should be given to this vocabulary, but we also need to consider how to bring in additional

GEM can be relevant to teaching in cultural heritage (museums,etc).

See GEM SKOs below and http://www.gem.org.uk/

SKOS can also include namespace or scheme of other thesauri

SKOS Overview [edit]

SKOS Core Overview

● Basic description ❍ Concept, ConceptScheme, inScheme, hasTopConcept ● Labelling ❍ prefLabel, altLabel, hiddenLabel, prefSymbol, altSymbol … (audio labels?) ● Documentation ❍ definition, scopeNote, changeNote, historyNote, editorialNote, publicNote, privateNote ● Semantic relations ❍ broader, narrower, related ● Subject indexing ❍ subject, isSubjectOf, primarySubject, isPrimarySubjectOf ● Grouping ❍ Collection, OrderedCollection, CollectableProperty, member, memberList

SKOS Thesauri Specific to Archives [edit]

From http://www.w3.org/TR/swbp-skos-core-guide/

SKOS Core provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies.

Web comments

SKOS and tags (folksonomy) a bridge?

When flickr meets del.icio.us meets SKS.

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (4 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ bridge between http://del.icio.us/tag/, http://flickr.com/tags/, http://blogmarks.net/

● UKAT UK Archival Thesaurus

❍ See LCSH SKOs work http://staff.oclc.org/~vizine/GSAFD/SKOS/2004-07-19/

❍ SMILE project ■ http://simile.mit.edu

■ http://www.dli2.nsf.gov/cgi-bin/wa?A2=ind0602&L=nkos&F=l&P=847

■ http://simile.mit.edu/repository/datasets/loc-tgm/java/LocTGMConverter.java

■ http://staff.oclc.org/~vizine/GSAFD/SKOS/2004-07-19/ gsafd-lcsh-lcshac.2004-07-19.skos.xml 27-Jan-2005 10:02 177K

[TXT] gsafd-lcsh.2004-07-19.skos.xml 27-Jan-2005 10:02 175K [TXT] gsafd-lcshac.2004-07-19.skos.xml 27-Jan-2005 10:02 166K [TXT] gsafd-oclc.2004-07-19.skos.xml 27-Jan-2005 10:02 164K [ ] gsafd.2004-07-19.skos.zip

SKOs & Topic Map issues [edit]

From site:

Simple Knowledge Organization System (SKOS) provides a standard for indicating the subject matter of content. SKOS lets you define the subjects for a particular subject matter area (organizing these subjects as a taxonomy if desired) and then classify each piece of content to indicate its subject. For instance, using SKOS, you could define configuration and security as subjects, and classify the three example topics that relate to those subjects so that users could browse the subjects to find the content regardless of whether the words "configuration" or "security" actually appear in the text.

SKOS is expressed with Resource Description Framework (RDF), the fundamental language of the Semantic Web. However, SKOS provides a higher-level language that's designed for readable content. SKOS has benefited from broad perspectives, including those of experts in OWL/RDF, \TopicMaps, ontology, and library science. In the spectrum of standards, SKOS contributes by bridging the gap between traditional indexing and formal ontologies for the Semantic Web.

● SKOs in Topic Maps ❍ SKOS in Topic Maps

❍ Subject classification with DITA and SKOS

● Ensure that SKOs supports multilinguality ● subjectIndicator in SKOS - check in Topic map ❍ http://esw.w3.org/topic/SubjectIndicator

❍ google query

DDC Dewey - SKOS [edit]

LCSH http://www.oclc.org/news/publications/newsletters/oclc/2004/266/research.html

Software [edit]

OAICat

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (5 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ http://www.oclc.org/research/software/oai/cat.htm Java, OCLC Research Public License.

From site:

The OAICat Open Source Software (OSS) project is a Java Servlet web application providing a repository framework that conforms to the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) v2.0. This framework can be customized to work with arbitrary data repositories by implementing some Java interfaces. Demonstration implementations of these interfaces are included in the webapp distribution.

From site: http://www.oclc.org/news/publications/newsletters/oclc/2004/266/research.html

GSAFD — Guidelines on Subject Access to Individual Works of Fiction, [edit] Drama, etc. http://www.oclc.org/research/projects/termservices/resources/gsafd.htm

Description:

The Guidelines on Subject Access to Individual Works of Fiction, Drama, etc., 2nd edition, was published in 2000. The Guidelines constitute a recommendation for national standard practice in the provision of genre and subject access to individual works of fiction, drama, poetry, humor, and folklore.

Resources:

● SKOS RDF-XML

See above http://staff.oclc.org/~vizine/GSAFD/SKOS/2004-07-20/

Terminology services [edit] http://www.oclc.org/research/projects/termservices/default.htm

Software available

Making knowledge organization schemes more accessible to people and computers

By Diane Vizine-Goetz, Consulting Research Scientist, OCLC Research

Which of the following most closely defines the term ‘vog’?

● a. the latest in Japanese street fashion ● b. not expressing one’s thoughts clearly ● c. volcanic smog ● d. a young fjord horse

According to the 2004 version of the Library of Congress Subject Headings (LCSH), the correct answer is c. Vog is volcanic smog. Concepts like this are constantly being added to knowledge organization schemes, such as thesauri, subject heading systems and classification schemes.

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (6 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ

The goal of OCLC’s terminology services project is to make the concepts in knowledge organization schemes and the relationships within and between schemes more accessible to people and computer applications. For example, if a hypothetical Web service provided access to the equivalent and related terms for concepts in LC Subject Heading records, it would be possible for software developers to create tools to improve Web searching. To test this hypothesis, go to your favorite search engine and search for the word ‘vog.’ Then modify your search to include the words ‘vog volcanic smog volcanic gases.’ The latter search, which includes variant and related terms from LCSH, will likely produce higher quality search results for materials about volcanic smog.

Before a Web service can be developed for a given knowledge organization scheme, it’s often necessary to preprocess the concept data. For some schemes, it’s necessary to convert the data from word processing documents or html pages to structured data formats, such as the MARC 21 formats for authority or classification data, or the SKOS core, an RDF schema for thesauri and related knowledge organization schemes. Once a scheme is in a structured format, it can be enhanced in several ways. Typical enhancements include mappings to other schemes, the addition of persistent identifiers, and the addition of coding to track the origin of records and the sources of changes. The end products of these processes are XML files that can be used as the basis for terminology Web services.

Terminology services are Web services that involve various types of knowledge organization resources, including authority files, subject heading systems, thesauri, Web taxonomies and classification schemes. OCLC researchers have prototyped several experimental terminology services. One Web service that uses the Dewey Decimal Classification (DDC) provides access to the DDC summaries. The service returns captions, in four languages, for DDC numbers at the top three levels of the classification. For example, when DDC class number 798 is submitted to this service, the service returns the following information:

798 Reitsport, Tierrennen Equestrian sports & animal racing Deportes ecuestres y carreras de animales Sports équestres et courses d’animaux

Although this response might not satisfy most human users, it will be quite acceptable to machines. If the results are intended for human eyes, it is up to computer applications to format them appropriately.

Another prototype terminology service, with a human interface component, uses the Microsoft Office 2003 Research services pane to search a database of genre terms for fiction. Without ever leaving the Office application, a user can issue a search and paste results from the search directly into a document. For example, if a college student wishes to categorize a reading list of fiction titles based on genre, he could copy the titles into a Microsoft Excel 2003 workbook, open the Research services pane, send a search to the OCLC Research GSAFD vocabulary service, and then place the results into his document.

For more information on Terminology Services, see: www.oclc.org/research/projects/termservices/.

Retrieved from "http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri"

Views

● Article

● Discussion

● Edit

● History

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (7 of 8)2006-09-29 08:51:04 Relevant Ontologies and Thesauri - QVIZ

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 3 times.

http://qviz.humlab.umu.se/index.php/Relevant_Ontologies_and_Thesauri (8 of 8)2006-09-29 08:51:04 Rights and business process related - QVIZ

Rights and business process related

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Workshops

● 3 1.1 MPEG-21

● 4 1.2 Creative Commons (cc)

● 5 1.3 WOT - Web Of Trust

● 6 Rights Expression Language (REL)

● 7 1.4 Schema for Rights Declaration

[edit] Summary

Workshops [edit]

● W3C Workshop on Languages for Privacy Policy Negotiation and Semantics-Driven Enforcement http://www.w3. org/2006/07/privacy-ws/cfp.html

1.1 MPEG-21 [edit] http://www.chiariglione.org/mpeg/standards/mpeg-21/mpeg-21.htm

1.2 Creative Commons (cc) [edit] http://creativecommons.org/

1.3 WOT - Web Of Trust [edit]

WOT ontology http://xmlns.com/wot/0.1/

Rights Expression Language (REL) [edit]

.... \XrML, ODRL .. others ? Help needed

1.4 Schema for Rights Declaration [edit]

● Schema (METSRights.xsd) http://cosimo.stanford.edu/sdr/metsrights.xsd

● Documentation http://dlib.nyu.edu/METS/textmd.htm

● Announcement http://www.loc.gov/standards/mets/news080503.html

● http://www.loc.gov/standards/

http://qviz.humlab.umu.se/index.php/Rights_and_business_process_related (1 of 3)2006-09-29 08:51:06 Rights and business process related - QVIZ

Used also in METS extended schemas http://www.loc.gov/standards/mets/mets-extenders.html

From the announcement

Simple Rights schema that the METS community could use while the more comprehensive Rights Expression Language (REL) schemas such as \XrML, ODRL, and others are being developed, and debated. The focus of the simple Rights schema is to simply declare or document some basic facts about the digital collections being created and/or included in institutional digital repositories. To that end, this draft Rights Declaration schema is offered to the METS community for review, comment, and discussion. The schema is attached as well as some sample instance documents designed to illustrate how the schema could be used.

As background and in explanation of the rationale for the Board's approach, the following schemas and similar efforts were reviewed closely: the ODRL REL, the \XrML REL, the federated digital rights requirements as crafted by Mairead Martin from U Tenn, Grace Agnew from Rutgers, and others, and the efforts by the Digital Library Federation's Electronic Resource Management Initiative (DLF ERMI) to document terms related to licensed electronic resources. Following the comparison of approaches and metadata elements, this rights declaration schema focuses upon:

● digital resources owned or controlled by the digital repository rather than e-resources accessed remotely, formally licensed and subscribed to by an organization (the area covered by the DLF ERMI group) ● declaring the rights holders and rights associated with the digital resources mentioned above rather than trying to fully express all rights as would a REL designed to be used with a Digital Rights Management system or product ● simplifying the declaration as much as possible given the fact that the whole DRM & REL scene is changing so rapidly

This Rights Declaration schema has 3 main elements:

● A simple declaration of type of rights (copyrighted, licensed, public domain, contractual, other) and the public statement of that Rights Declaration, ● The naming of the Rights Holder(s) with appropriate contact information, ● The Context(s) for the rights declaration based on type of users who have a set of permissions for a digital object or part of a digital object. If there are any constraints to the permissions, those are also expressed within the context by listing the constraints and explaining them in a constraint description element.

The Rights Schema is available at www.loc.gov/standards/rights/METSRights.xsd

Also available are the following example documents:

* "Stanford University Libraries (Example 1)":http://www.loc.gov/standards/rights/ examples/SULRightsEx1.xml * "Stanford University Libraries (Example 2)":http://www.loc.gov/standards/rights/ examples/SULRightsEx2.xml * New York University Library

Retrieved from "http://qviz.humlab.umu.se/index.php/Rights_and_business_process_related"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

http://qviz.humlab.umu.se/index.php/Rights_and_business_process_related (2 of 3)2006-09-29 08:51:06 Rights and business process related - QVIZ

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 2 times.

http://qviz.humlab.umu.se/index.php/Rights_and_business_process_related (3 of 3)2006-09-29 08:51:06 Bookmarking, Social Bookmarking - QVIZ

Bookmarking, Social Bookmarking

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Background

● 3 Review

● 4 Diigo

● 5 XBEL (the XML Bookmark Exchange Language).

● 6 Annotea

● 7 topic resources

● 8 XUL

● 9 Social bookmarking interoperability

● 10 Distributed Social Bookmarking

[edit] Summary

Bookmarking and history standards that we might extend

Background [edit]

● Wiki: http://en.wikipedia.org/wiki/Social_bookmarking

● Social Bookmarking Tools (2005) http://www.dlib.org/dlib/april05/hammond/04hammond.html

Review [edit]

From Social Bookmarking Tools (2005) http://www.dlib.org/dlib/april05/hammond/04hammond.html

!http://www.dlib.org/dlib/april05/hammond/fig-3-rev.gif!

Fig. 3. This diagram charts the benefits of tagging on the vertical axis against the content being tagged on the horizontal axis. (Social bookmarking tools as reviewed in this paper are represented in plain text, while other tools are represented in italics.) As can be seen, use cases range from the lower-left quadrant ('selfish') represented by Flickr, which is mainly concerned with users tagging their own content for their own retrieval purposes (i.e. using their own tags), to the upper-right quadrant ('altruistic') represented by Wikipedia, which is mainly concerned with users categorizing others' content for retrieval by others. (Note, however, that Wikipedia uses a shared taxonomy – albeit one generated by a community – not free-form tags. In the figure, we indicate this difference by adding parentheses to show that Wikipedia is not using user-supplied tags.) The majority of the social bookmarking tools reviewed here fall into the category of others' content tagged for their own retrieval purposes, while Technorati tags (as well as familiar HTML meta tags) are usually about the user's own content being tagged for others to retrieve.

!http://www.dlib.org/dlib/april05/hammond/fig-4.gif!

Despite all the current hype about tags – in the blogging world, especially – for the authors of this paper, tags are just one kind

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (1 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ of metadata and are not a replacement for formal classification systems such as Dublin Core, MODS, etc. [n15]. Rather, they are a supplemental means to organize information and order search results. Figure 4 shows the raw XML for an RSS feed of an item in Connotea describing the paper 'Resource Harvesting within the OAI-PMH Framework' by Herbert Van de Sompel et al. [29] from the December '04 issue of D-Lib Magazine. Clearly present are user-supplied tags describing the content of the paper, along with citation metadata supplied by Connotea from an authoritative source (in this case the structured metadata made available by D-Lib Magazine).

Screen shot showing the raw XML for an RSS feed

Fig. 4. The raw XML for an RSS feed that shows an item describing a page for a bookmarked URL in Connotea (in this case, the paper 'Resource Harvesting within the OAI-PMH Framework' by Herbert Van de Sompel et al. from the December '04 issue of D-Lib Magazine) with user-supplied tags (#1) – expressed as dc:subject elements – and citation metadata (#2) – expressed as dc: and prism: elements – derived from an XML document providing citation metadata that is referenced by the D-Lib paper.

(For a larger view of Fig 4., click here.)

One particularly creative tagging application is, 'Phonetags', a system created by the BBC and presented at the recent O'Reilly Emerging Technology Conference [30]. A listener hears a song on the radio, uses their cell phone to text back to a website with tags and star ratings. Later, returning to the website, the user can type in their phone number and see the songs they have bookmarked. Indeed, few are the things that cannot be tagged, at least in principle. These could include geographical locations, people and (as mentioned earlier) even tags themselves. The Social Axis

The third axis of Matt Biddulph's deconstruction (which was mentioned in the Introduction of this paper) is the user axis and how users can (and do) make use of these tools, which has both a local dimension and a global dimension. As Liz Lawley has blogged on Many 2 Many [31]:

"Flickr and del.icio.us work so well for me not because they aggregate the world's tags, but because they allow me to aggregate my social network's tags, links, and photos. [...] I don't want to see "research" resources from a molecular biologist, but I do want to see them from a sociologist studying online social networks."

This ability to sort out the wheat from the chaff is an important win over a web-based search engine. Search engines, at this point, tend to index and search a global space – not my local space. My space comprises the documents I am interested in and the documents of other users that I want to follow.

Another important aspect on the social axis is user privacy. By publicizing their bookmarks, users are opening up to other users on the Web their own sphere of interests. (Note that some tools already support, or plan to support, the option of keeping certain bookmarks private.) Regardless of the fact that tools usually allow one to set up an account under a self-selected (perhaps obscure) username, this provides little guarantee of anonymity. The short answer to this is that social bookmarking tools, as with the Web at large, usually pay users back many times over in utility for whatever privacy they may have surrendered. But if absolute privacy is important, then it's certainly best to stay away from these tools (and, indeed, possibly the Web as a whole). A further issue to consider is tag spamming. E-mail has been severely impacted by spamming. Blog comments and trackbacks are similarly vulnerable to attack. Adware and spyware are already corrupting users' browsing experiences. There is no question but that spamming of these new social tools can and will occur – it almost goes with the territory that social forums will foster such 'parasites' and some instances have been noted already. So far, however, it does not seem to have been a major problem, largely because spam has been drowned out by legitimate use. But obviously, continuing vigilance must play a part, and robust defences may need to be put in place should this start to become problematic. Glue in the Works

Almost without exception these social bookmarking tools are feature-rich, providing search on both users and tags (with Boolean operators), comments (and comment trails), simple linking syntaxes, and APIs (application programming interfaces) for posting to and from these tools (and to other tools such as blogs). Invariably the 'glue' technology used is RSS.

RSS allows these tools to be hooked up easily. Examples abound. 43 Things [n16] – a service that records (up to) 43 user

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (2 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ goals and allows users to share and tag these goals – can also search the del.icio.us and Flickr tag sets as shown in Fig. 5.

Screen shot of 43 Things

Fig. 5. 43 Things records (up to) 43 user goals and also supports tagging of those goals. Here seven users have chosen the goal 'Make Firefox my default browser', which has been tagged by at least one user with the tag 'firefox'. 43 Things has searched the Flickr and del.icio.us tools for this tag and has returned photos from Flickr and bookmarks from del.icio.us that have the same tag. On the right-hand side are shown related tags to 'firefox' within 43 Things: 'browser', 'ie', 'sux' [sic], 'spyware', 'adware'. Also of note are the search box, the RSS feed, and a Google-esque simplicity in design.

(For a larger view of Fig 5., click here.)

Many of these tools have a very easy-to-use, linking syntax. Below, for example, we show some examples as presented in the del.icio.us 'about' page [32] for linking to HTML pages or to RSS newsfeeds. For RSS newsfeeds an '/rss' path element is simply prefixed to the path. Usernames are presented first, followed directly by any tag or tag combination. If no username is presented then a '/tag' path element is prefixed to the path to avoid name collisions of tags with possible usernames.

Examples of linking syntax from the del.icio.us about page

Other bookmark managers employ similarly straightforward link syntaxes.

Through the use of such linking syntaxes and more fully evolved APIs, along with RSS as a channel for syndicating rich metadata, some of these social bookmarking tools may be well suited to participate in the general service autodiscovery space described by Dan Chudnov and Jeremy Frumpkin in their informal paper 'Service Autodiscovery for Rapid Information Movement' [33]. Building Communities

As a simple demonstration of the way in which social bookmarking tools might benefit academic research, we show here how Connotea can be used by readers of this paper, and of its companion [4], to access the reference lists, to share other relevant links, and to trade comments on them and on the papers themselves.

First, we have selected the simple Connotea tag 'dlib-sb-tools' to refer to this paper and the tag 'dlib-connotea' to its companion paper. (Note that in these cases we have deliberately selected tag names that are unlikely to coincide with those selected arbitrarily by others users. Note also, however, that these tags are not guaranteed to be unique, but in practice they are likely to be so [n17] – this is not an exact science but an empirical one.) New bookmarks of relevance to either of these D-Lib Magazine papers can be added by anyone to these lists simply by bookmarking them in Connotea and using these tags. To begin with, each related links list has been seeded with a link to the paper itself and links to the references from the corresponding paper. Interested readers can follow these growing lists of related links by viewing the following web pages:

http://www.connotea.org/tag/dlib-sb-tools http://www.connotea.org/tag/dlib-connotea or, perhaps more conveniently, by signing up for the corresponding RSS feeds:

http://www.connotea.org/rss/tag/dlib-sb-tools http://www.connotea.org/rss/tag/dlib-connotea

If anyone would just like to focus exclusively on the related links posted by a particular user, e.g., user 'joanna' or 'timo' say (as opposed to all those posted), then they can do so by limiting the set by filtering on the username as follows:

http://www.connotea.org/user/joanna/tag/dlib-sb-tools http://www.connotea.org/user/timo/tag/dlib-connotea

A similar approach can be used to provide communal access to a static list of resources. By way of demonstration, we have selected the tag 'dlib-sb-tools-refs' to refer to references in this paper, and the tag 'dlib-connotea-refs' to references in its companion. Each link to a reference listed in the references section in both papers has been added to Connotea and has been

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (3 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ tagged with the appropriate '-refs' tag to mark it as a reference, in addition to the paper-specific tag. More descriptive tags can also be added, as well as comments on the reference. This means that the published reference lists for these two papers can be retrieved at the following addresses:

http://www.connotea.org/tag/dlib-sb-tools-refs http://www.connotea.org/tag/dlib-connotea-refs

However, to ensure that the reference lists are properly 'closed' (and that no further bookmarks that happen to be tagged by other users with the same '-refs' tag are included), we can further specify the usernames of the lead authors (users 'tony' and 'ben', respectively) who undertake to reserve these '-refs' tags for the exclusive use of tagging the reference lists to their respective papers. This means that truly 'closed' published reference lists for these two papers can be retrieved at the following addresses:

http://www.connotea.org/user/tony/tag/dlib-sb-tools-refs http://www.connotea.org/user/ben/tag/dlib-connotea-refs i.e., return the bookmarks tagged 'dlib-sb-tools-refs' by user 'tony', which correspond to the author's reference list for this paper, and the bookmarks tagged 'dlib-connotea-refs' by user 'ben', which correspond to the author's reference list for its companion. The links given above refer to the properly 'closed' sets of references that appear in the published articles and are made retrievable over the Web as historical resources. Note that this approach not only allows a published reference list to be maintained by a paper's author (e.g., if a link changes, they can update it) but also allows the list to be accessed in machine- readable form from Connotea (currently RSS and RIS are supported, with BibTeX to follow soon) regardless of the functionality of the site publishing the paper itself.

Likewise, we have tagged and made available the lists of related links ('dlib-role-rss') to our earlier RSS paper in D-Lib Magazine [34] and links to the references published therein ('dlib-role-rss-refs'), in both a more-than-likely 'closed' form and in a properly 'closed' form with first author. These can be accessed, respectively, as

http://www.connotea.org/tag/dlib-role-rss http://www.connotea.org/tag/dlib-role-rss-refs http://www.connotea.org/user/tony/tag/dlib-role-rss-refs

Readers are invited to contribute new references to the related link lists for any of these three papers that they deem to be subject compatible by using the appropriate paper-specific tag, i.e., 'dlib-role-rss', 'dlib-sb-tools', or 'dlib-connotea'. Of course, they are free to use any other tags they choose for the purposes of creating their own personal classification schemes, or for linking to other communities of interest. We also urge readers to use Connotea's commenting system to discuss any of these resources or, indeed our papers

http://www.dlib.org/dlib/december04/hammond/12hammond.html http://www.dlib.org/dlib/april05/hammond/04hammond.html http://www.dlib.org/dlib/april05/lund/04lund.html

All bookmarking events for these papers, i.e., the separate bookmarks and tags entered by individual users, are listed on the following pages, respectively:

http://www.connotea.org/uri/8eedc88e80ce8c8350e4236e89569138 http://www.connotea.org/uri/345d20a05f4db6e0d0ceeb940438295a http://www.connotea.org/uri/685b90ae66cfbc3fc8ebeed0a5def571

Comments on the papers themselves can be added on the following pages, respectively:

http://www.connotea.org/comments/uri/8eedc88e80ce8c8350e4236e89569138 http://www.connotea.org/comments/uri/345d20a05f4db6e0d0ceeb940438295a http://www.connotea.org/comments/uri/685b90ae66cfbc3fc8ebeed0a5def571

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (4 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ

These approaches create a series of shared spaces that have the potential to become 'living' resources that maintain and extend the relevance of each paper beyond its initial publication. We are intrigued to see how this experiment might be taken forward by D-Lib Magazine readers. Conclusions

Differently from the simple link manager functionality built into a browser, the new breed of link manager is a server-side web application that enables links to be tagged for easy retrieval and is increasingly being opened up to manage public rather than (or sometimes in addition to) private sets of links. The following elements are usually present in varying degrees:

* Personal user accounts (groups sometimes provided) * Mechanism for entering links, titles and descriptions * Browser bookmarklets to facilitate entry [n18] * Classification by 'open' or 'free' tagging * Search by tag or user (Boolean combinations sometimes allowed) * Querying of links based on popularity, users, tags, etc. * RSS feeds * Extensions such as browser plug-ins

In many ways these new tools resemble blogs stripped down to the bare essentials. Here the essential unit of information is a link, not a story – but a link decorated with a title, a description, tags and perhaps even personal recommendation points. It is still uncertain whether tagging will take off in the way that blogging has. And even if it does, nobody yet knows exactly what it will achieve or where it will go – but the road ahead beckons.

Diigo [edit]

● http://www.diigo.com

Diigo is about "Social Annotation" and is a way to collect, share and interact on online information. It also allows users to apply Folksonomies to links

Note: it works for social annotation of whole pages and currently those where the site has a URL (GET), not POST based. http://www.diigo.com/tools for browser plug-in

● right click context menu and browser menu bar ● search ● view user bookmarks ● blog the bookmark

1. Highlight, Clip and Sticky-Note for any webpage

* just as you would on paper --> write on any webpage! * make them private or public --> interact on any webpage!

1. Share online findings with your friends and colleagues

* complete with highlights and sticky notes * as lists, as blogs, as albums, as feeds, or via email

1. Diigo ideas

* collect and compile your research findings * provide feedback on web design Example * make wishlists Example * plan vacations Example

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (5 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ

* comparison shopping

!http://www.diigo.com/images/socialAnnotate.gif!

XBEL (the XML Bookmark Exchange Language). [edit]

● http://pyxml.sourceforge.net/topics/xbel/

Annotea [edit] http://www.w3.org/2003/07/Annotea/BookmarkSchema-20030707

!http://www.w3.org/2003/07/Annotea/bookmark.png!

This shows the core bookmark properties. An instance of a bookmark is declared by assigning it the rdf:type of b:Bookmark. Each instance of a bookmark is identified with a unique URIref (URI reference; a URI, possibly including a fragment id). When a bookmark URIref is an http: resource it is expected that an HTTP GET using that URI will return RDF content containing properties of the corresponding bookmark.

b:Bookmark The class to which all bookmarks belong. rdf:type Declares the class of the bookmark; the value should be http://www.w3. org/2002/01/bookmark#Bookmark or a subclass of http://www.w3.org/2002/01/ bookmark#Bookmark. dc:title Title of the bookmark. b:recalls Relates the bookmark with the resource that has been bookmarked. The typical user operation of following a bookmark link will use the value of the b:recalls property. This property corresponds to XBEL:href property. b:hasTopic Associates the bookmark with a Topic (see below). A bookmark must have at least one b:hasTopic property. dc:description The description of or notes about the bookmark. dc:creator The name of the creator of the bookmark. a:created The date and time on which the bookmark was created. Format should be YYYY- MM-DDTHH:MM[:SS]TZD (see [DATETIME]) dc:date The date and time on which the bookmark was last modified. Format should be YYYY-MM-DDTHH:MM[:SS]TZD (see [DATETIME])

topic resources [edit]

A topic defines an informal category for the purpose of classifying bookmarks.

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (6 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ

Topics may have subtopics and may refer to categories in more formal ontologies. Each instance of a topic is identified with a unique URIref (URI reference; a URI, possibly including a fragment id). When a topic URIref is an http: resource it is expected that an HTTP GET using that URI will return RDF content containing properties of the corresponding topic.

The basic properties of a topic are listed in Figure 3.3. The dc:title property is used to assign a title to the topic. The dc:description property may be used to give a longer textual description for the topic. A topic hierarchy is defined using b: subTopicOf properties.The a:created and dc:date properties have the same meaning as for bookmarks.

b:Topic The class to which all topics belong. rdf:type Declares the class of the topic; the value should be of rdf:type http://www. w3.org/2002/01/bookmark#Topic or a subclass of http://www.w3.org/2002/01/ bookmark#Topic. dc:title The title of the topic. b:subTopicOf Describes a relationship between topics. When a topic T is a sub-topic of a topic U then all bookmarks that have topic T are also considered to have topic U. A topic may be a sub-topic of one or more topics; trivially, every topic is a sub- topic of itself.

More formally; for all B, T, and U: B b:hasTopic T, T b:subTopicOf U implies B b:hasTopic U. dc:description The description of or notes about the topic. dc:creator The name of the creator of the topic. a:created The date and time on which the topic was created. Format should be YYYY-MM- DDTHH:MM[:SS]TZD (see [DATETIME]) dc:date The date and time on which the topic was last modified. Format should be YYYY-MM-DDTHH:MM[:SS]TZD (see [DATETIME])

XUL [edit]

Bookmarking such as used in Mozilla

Social bookmarking interoperability [edit]

Note: See RSS relationships as well to advertise or present the bookmark

● http://blogs.open.ac.uk/Maths/ajh59/005332.html

● http://blogs.open.ac.uk/Maths/ajh59/006153.html

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (7 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ

● http://blog.simpy.com/blojsom/blog/2005/11/04/Sexy-URIs.html

Distributed Social Bookmarking [edit] http://blogs.open.ac.uk/Maths/ajh59/005336.html

From site:

1. Sharing between different users or different groups defined within a single social bookmarking system; 2. Sharing bookmarks between different installations of the same environment. For example, I could quite easily imagine different academic research groups in the same organisation installing their own version of Connotea, and at some later date wanting to share information across those installations whilst retaining them all as independent installations; 3. Sharing bookmarks between different applications, for example between del.icio. us and Connotea. An example of this scenario may be an academic researcher who maintains their own social bookmarking account to provide continuity as they more from post to post, institution to institution, and yet would like to share this resource with the institutional social bookmarking service at their host instituion. Another example might be ad hoc groups that form across social bookmarking applications, e.g. amongst attendees at a workshop or collaborators on a particular project.

Retrieved from "http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking"

Views

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (8 of 9)2006-09-29 08:51:12 Bookmarking, Social Bookmarking - QVIZ

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

● This page was last modified 07:41, 15 September 2006. ● This page has been accessed 7 times.

http://qviz.humlab.umu.se/index.php/Bookmarking%2C_Social_Bookmarking (9 of 9)2006-09-29 08:51:12 XPointer and applications - QVIZ

XPointer and applications

From QVIZ

Jump to: navigation, search Contents

● 1 Summary

● 2 Libraries

● 3 Relevant Applications using XPointer

● 4 Annozilla

● 5 University of Bologna XPointer implementations, libraries

[edit] Summary

XPointer - it is a means to exploit the XML/html structure of a document to enable annotations of textual content. It was once a goal to create robust XPointer engines. In general a robust solution is not available which can handle all content changes without breaking the links. The most popular application is Annozilla. In a community and QVIZ we could image providing the means for the community to fix broken links, especially if the content is versioned so that users can compare content - and perhaps provide the means to indicate which links are broken and where they occur in versioned content.

Libraries [edit]

Javascript libraries

● http://www.cs.unibo.it/~fabio/XPointer/xpcode.asp

❍ about http://www.cs.unibo.it/~fabio/XPointer/

● Annozilla http://annozilla.mozdev.org/installation/

Relevant Applications using XPointer [edit]

Annozilla [edit]

● http://annozilla.mozdev.org/index.html

● Using annotation server (storing as RDF, users must have login and Mozilla based browser and Annozilla plugin

http://qviz.humlab.umu.se/index.php/XPointer_and_applications (1 of 5)2006-09-29 08:51:13 XPointer and applications - QVIZ

❍ Annotea http://www.w3.org/2001/Annotea/

● http://annozilla.mozdev.org/installation/

The Annozilla software consists of three extensions:

* xpointerlib A library to allow the use of XPointers * the annotations service A service allowing access to annotations * Annozilla The Annozilla client itself

From the site: http://annozilla.mozdev.org/index.html

... designed to view and create annotations associated with a web page, as defined by the W3C Annotea project. The idea is to store annotations as RDF on a server, using XPointer (or at least XPointer-like constructs) to identify the region of the document being annotated.

The intention of Annozilla is to use Mozilla's native facilities to manipulate annotation data - its built- in RDF handling to parse the annotations, and ns\IXmlHttpRequest to submit data when creating annotations.

To use Annozilla, you will need to install the packages, get set up with a user account with an annotation server (e.g., the W3C test server), and then you should be ready to go.

University of Bologna XPointer implementations, libraries [edit] http://www.cs.unibo.it/~fabio/XPointer/

Two types of implementations

❍ XLinkProxy http://www.cs.unibo.it/~fabio/XPointer/MyXpointEN.htm

XPointer is a W3C proposed standard for the addressing of arbitrary fragments of XML documents. XPointer extends XPath, which is used to address nodes, and adds support for single positions within a text node (the so-called points) and ranges within and across element nodes.

Our implementation is a part of a larger project called XLinkproxy, a distributed linking system based on the W3C XLink recommendation. XLink is a sophisticated linking language that uses XPointer to identify the end-points of the links, especially when they are not whole nodes of the XML tree.

Since the XLinkproxy project focuses on the linking system, the current implementation of XPointer is functional to that purpose, and is only partial in terms of the XPointer language itself. Nonetheless, many of the core functions have been implemented and tested for the linking system. Download

http://qviz.humlab.umu.se/index.php/XPointer_and_applications (2 of 5)2006-09-29 08:51:13 XPointer and applications - QVIZ The current version of the XPointer package can be downloaded here Implementation

This XPointer library is designed to run on a web server (specifically Microsoft IIS 5.0) and it is written in Microsoft JScript 5.5. It is aimed at being hosted inside an ASP file on the server. It is based on Microsoft XML4.0 and lies on top of Microsoft's implementation of XPath.

We restrict ourselves to XPointer expressions of this kind:

XPointerExpr := ((XPathExpr)(XPointerKeyword)(XPathExpr)) XPathExpr := any XPath expression XPointerKeyword := 'point()'|'range()'|'range-to'|'range'|

❍ XSLT++ engine http://www.cs.unibo.it/projects/xslt%2B%2B/

XSLT++ is an enhanced version of XSLT. XSLT is a language for transforming XML documents; a typical application of XSLT is to tranform XML documents into HTML documents, which are suitable to be displayed by the majority of web browsers.

XSLT is based on XPath, a specification language for nodes and node sets of the source XML document; using XPath it is possible to select attributes, elements or even entire subtrees of a document. XSLT uses XPath to associate transformation templates to patterns of nodes in the source XML document.

Although XPath is very powerful, it does not allow the selection of arbitrary fragments of documents; for example, with XPath it is not possible to select an arbitrary string, but only the entire text node which it belongs.

XPointer is an extension of XPath that overcomes this limitation. XPointer introduces the concepts of point and range. With XPointer, for example, it is possible to select a range that starts in the middle of a text node and that ends within a different text node, even in a part completely different of the document tree.

XPointer was designed having on mind sophisticated hypertext linking. Yet, XML transformations could greatly benefit from enhanced patterns.

XSLT++ is our XSL engine with support for XPointer instead of XPath for the selection of patterns. With XSLT++ it is possible to apply transformations to portions of text, and not only to elements, attributes or text nodes.

Retrieved from "http://qviz.humlab.umu.se/index.php/XPointer_and_applications"

Views

http://qviz.humlab.umu.se/index.php/XPointer_and_applications (3 of 5)2006-09-29 08:51:13 XPointer and applications - QVIZ

● Article

● Discussion

● Edit

● History

● Move

● Watch

Personal tools

● Nikoletta

● My talk

● Preferences

● My watchlist

● My contributions

● Log out

Navigation

● Main Page

● Community portal

● Current events

● Recent changes

● Random page

● Help

● Donations

Toolbox

● What links here

● Related changes

● Upload file

● Special pages

● Printable version

● Permanent link

http://qviz.humlab.umu.se/index.php/XPointer_and_applications (4 of 5)2006-09-29 08:51:13 XPointer and applications - QVIZ

● This page was last modified 09:17, 5 September 2006. ● This page has been accessed 2 times.

http://qviz.humlab.umu.se/index.php/XPointer_and_applications (5 of 5)2006-09-29 08:51:13 Timeless access to time-spatial information

GIS with overlapping polygons Collapsed non-overlapping for different time period. polygon with relation in table.

parish_01 parish_02 G1 G2 Parish Parish 1870-1890 1892-1920

parish_03 G3 Parish 1730-1865

table: nad_data table: nad_info polygon_id nad_id nad_id G1 parish _01 parish_01 1870 – 1890 G2 parish _01 parish_02 1892 – 1920 G3 parish _01 parish_03 1730 – 1865 G2 parish _01 G2 parish _02 G3 parish _01 G3 parish _03

Query example Q: What other parishes was G3 part of in 1834?