Showing posts with label metadata. Show all posts
Showing posts with label metadata. Show all posts

Friday, January 23, 2015

Data Retention Bill a Threat to Civil Rights

The Internet Society of Australia (ISOC-AU) has released "The Data Retention Bill: A threat to civil rights protections that just won't work!" (Media release, 22 January 2015). ISOC-AU has criticised the draft Telecommunications (Interception and Access) Amendment (Data Retention) Bill, saying it is "deeply flawed", a "serious threat to existing civil rights protections" and too broadly defines the data to be retained for access by agencies.  ISOC-AU has made submissions to parliamentary inquiries on the issue.

ps: I am a member of ISOC-AU and support their position.

Wednesday, October 29, 2014

Half a million warrantless meta data requests

I was interviewed on radio 2SER Sydney this-morning about the release of metadata from Internet Service providers for law enforcement: "Half a million warrantless meta data requests!". For an overview of the issues, see: "Access to and retention of internet 'metadata'" by Jaan Murphy, Australian Parliamentary Library, 18/08/2014.

Thursday, August 07, 2014

Metadata Retention for Law Enforcement

There seems to be some confusion within the Australian Government as to what data retention policy has been decided on by the Cabinet. It might be useful if the Prime Minister and the Attorney General were to ask for a briefing from their departmental staff as to what "metadata" is, or they could ask the Minister for Communications.

The Australian Minster, Mr. Tony Abbot, said on Tuesday:
We also need legislation which I have commissioned the Attorney to prepare, which the National Security Committee of the Cabinet has commissioned the Attorney to prepare to ensure that we are best able to monitor potential terrorist activity in this country. Obviously with the usual range of safeguards and warrants but that will include discussions with the telecommunications providers about the retention of metadata....
From Joint Press Conference - Prime Minister and Attorney General, Canberra,Tuesday, 5 August 2014)
The Attorney General said:
Finally, as the Prime Minister indicated, I have also been asked to develop – in consultation with relevant stakeholders, in particular, in the telecommunications sector – a system of mandatory data retention. That legislation has been approved in principle and is in development from today and will be introduced into Parliament later in the year.  ...
From Joint Press Conference - Prime Minister and Attorney General, Canberra,Tuesday, 5 August 2014)
Unfortunately I have been unable to find a copy of the legislative proposal for retention of metadata. In a later interview the Attorney General, Mr George Brandis, did not appear to know what metadata was, nor what it was proposed to require telecommunications companies to retain:
Brandis: "The web address, um, is part of the metadata."
Journalist: "The website?"
Brandis: "The well, the web address, the electronic address of the website. What the security agencies want to know, to be retained is the, is the electronic address of the website that the web user is ... "
Journalist: "So it does tell you the website?"
Brandis: "Well, it, it tells you the address of the website."

From: Attorney-General George Brandis struggles to explain Government's metadata proposal, ABC Radio, 7 August 2014
The Parliamentary Library produced a good overview of the issues "Surveillance in society—global communications monitoring and data retention" (Nigel Brew, Australian Parliamentary Library, 2013). The Wikipedia's "Telecommunications data retention" entry is also useful.

The UK House of Commons recently passed laws on data retention (Data Retention and Investigatory Powers Act 2014, UK Government). This authorises the UK Secretary of State to require telecommunications operator to retain specified communications data for up to one year. A warrant may not be required to obtain the data, under some circumstances. What data can be collected is not specified in the act, except to say that it does not include "data revealing the content of a communication". In the Australian context this data is being called "metadata". For an explanation of meta-data, see my ANU course lecture notes: "Metadata" (From Metadata and Electronic Data Management, by Tom Worthington, for ANU Course COMP3410, Information Technology in Electronic Commerce, 2009).

Internet metadata which would normally be stored would be the Internet protocol Address (IP Address) of the computer data was being sent from, the IP Address it was being sent to and the date and time. The issue which the Australian Attorney General appeared to be unclear about was if just the IP addresses were to be stored, or if the web address (URI) was also to be stored.

To use an analogy, the IP address would be the street address of a library someone was visiting, whereas the web address would be the number of the book they borrowed (event the chapter they opened it at). My interpretation of the UK law is that the web address would be part of the content of the communication and therefore not permitted.

What the Australian government proposes is unclear. A good first step would be for the Cabinet, and the Attorney General in particular, to be briefed on the basics of how the Internet works.

Wednesday, November 21, 2012

Is the Thomson Reuters Data Citation Index Worth Paying For?

Greetings from the Hancock Learning Commons at the Australian National University in Canberra, where I am attending a presentation on the Thomson Reuters Data Citation Index. This attempts to add data to the traditional papers and books which academics get credit for producing. Thomson Reuters' offering was released a few weeks ago and ANU has been trying it out. Initially there were 2 million records in 69 repositories, including the Australian Data Archive (ADA). About half the current contents are from the USA, 42% from Europe. About half is from the life sciences.

What was not clear to me is what benefit the academic and research community gain by using Thomson Reuters' service. Presumably Thomson Reuters will charge money for use of their service. The information being indexed is almost all free open access material paid for by the public. It is not clear why academics should then pay Thomson Reuters for accessing free information.

The Australian Government funded Australian National Data Service the Australian Research Data Commons and similar free open access repositories are being linked up around the world.

If Thomson Reuters can add value to this, then the benefits they are offering need to be compared with what they propose to charge and a decision made if this investment is in the public interest.  It may not be a good use of public money for each university in Australia individually buy a subscription from Thomson Reuters.

Thomson Reuters collect up the metadata provided by repositories around the world and provide a global search facility to subscribers. The same service could be provided by others by harvesting this metadata.

The other service which is likely to be of more interest to academics, is that they harvest the citations of the datasets. Academics get hired and promoted partly on how many times their work is mentioned (cited) in published work. It is now possible to cite a dataset in the same way as publications, such as using APA. This will then increase the academics' citation ranking. If a Digital Object Identifier (DOI) is used, this makes the collection of the citations relatively easy.

Wednesday, May 18, 2011

BBC on Semantic Web in Canberra

Tom Scott, Executive Product Manager and  Technical Projects Lead at the BBCTom Scott, Executive Product Manager and Technical Projects Lead at the BBC will be speaking on semantic web publishing and metadata at the Meta 2011 conference at University House, the Australian National University, in Canberra, 25 May 2011.
... The BBC is an acknowledged leader in semantic web publishing and the use of metadata to create dynamically linked sites. Tom Scott has executive responsibility for three of the broadcast giant's sites, which are often held up as exemplary projects within the Linked Data community. These are: the BBC Nature site (bbc.co.uk/nature) incorporating a major Linked Data and video publishing element; the BBC Programme Support site (bbc.co.uk/programmes), a website that publishes a page (URI and metadata) for every programme the BBC broadcasts; and the BBC's Music site (bbc.co.uk/music), a website that integrates into the BBC broadcast systems and BBC Programmes.

As an active blogger and expert in semantic web publishing, Tom will paint the picture of both the current and future demands of digital publishing and information management and how metadata can enable that using real live examples. “The idea is to help people think about the Web from a different perspective, one that is ultimately empowering because in doing so you can more easily deliver real benefits to your organisation and users” said Scott....

From: BBC Tom Scott to present at Meta2011, Press Release, IMM, 12 May 2011

Monday, May 02, 2011

Meta 2011 Conference Program

The Meta 2011 Conference is at ANU University House in Canberra, 25 to 27 May 2011. Notable speakers include: Tom Scott, BBC; Professor John McMillan, Australian Information Commissioner; Tim Dale, Director, Gov 2.0 Strategy & Services, Department of Finance and Deregulation; and Greg Stone, Chief Technology Officer, Microsoft Australia. I am speaking on "Designing for Democratic Dialogue: More than Mating iPads" 11.00 am on Thursday 26th May, 2011. Here is the full program for the conference:

Day 1 - Wednesday 25th May, 2011

Hall Sessions

Hall

Session Speaker

Session Title

Registration

Welcome and Introduction

Opening Address Mel Taylor, Inaugural IMM PresidentConference overview and context
Day One Theme The Market Today and Where it is Going - Current Challenges & Issues
Current Challenges & Issues
KEYNOTE 1 Tom Scott, BBCPublishing BBC metadata
Sub Keynote 1 Business Intelligence & AnalyticsGreg Stone, Chief Technology Officer, Microsoft AustraliaTBC
Sub Keynote 2 Management, Governance and StewardshipProfessor John McMillan, Australian Information CommissionerThe Open Government Reform Agenda
Energy & Contact Break

Business Intelligence & Analytics

Speakers:

Session OnePaul Madden, CIO and CKO, Department of Health & Ageing
Session TwoPeter Harper, Deputy Australian Statisician
Session ThreeCraig Mudge, University of Adelaide
Lunch

Case Study Sessions

Case Study OneBettina Konti, ATO
Case Study TwoBarbara Reed, Recordkeeping Innovation
Case Study ThreeTBC
Energy & Contact Break

Speaker Debate with Q & A Voted around the Market and its Challenges and potential solutions
Close

Drinks - Fellows Bar, University House, ANU




Common Room Sessions

Time

Foyer

Common Room

Session Title

10:30 AMEnergy & Contact Break
11:00 AM
Management, Governance and Stewardship - including Professional & Capability Development


Speakers: Session OneCraig Thomler


Session Two
Tim Dale, Director, Gov 2.0 Strategy & Services, Department of Finance and Deregulation


Session ThreeProfessor Andy Koronios, University of South Australia
12:30 AMLunch

1:30 PM
Case Study Sessions


Case Study OneTim Hart, CIO, Museum of Victoria


Case Study TwoMichael Beahan, Australian Bureau of Statistics


Case Study ThreeSally Goodenough, ANDS


Case Study FourMatt Moore, Innotecture
3:00 PMEnergy & Contact Break

Day 2 - Thursday 26th May, 2011

Hall Sessions

Time

Foyer

Hall

Session Speakers

9:00 AM
RECAP FROM DAY ONE Overview of Day Two
9:00 AM
DAY TWO THEME Emerging solutions and applications in market and in development
9:10 AM
Sub Keynote 3 What's out there now (the market)Peter Williams, Deloitte
9:30 AM
Chair:


Case Study One
Warwick Graco, ATO


Case Study TwoCassandra Findlay, State Records NSW


Case Study ThreeAnne Stevenson, CSIRO
10:30 AMEnergy & Contact Break
11:00 AM
Overcoming obstacles in the Execution process - challenges and solutions




Case Study OneProfessor Tom Worthington, ANU


Case Study TwoTim Drury, Department of Immigration


Case Study ThreeAustralian Broadcasting Corporation
12:30 AMLunch





1:30 PM
Sub Keynote 4 Research Overview (emerging technologies) Dr Renato Ianella, Semantic Identity


Case Study
Dr Tudor Groza (UQ) and Dr Armin Haller (W3C, CSIRO)


Case StudyLeanne Fry, Fair Work Ombudsman
2:30 PMEnergy & Contact Break
3:00 PM
Linked Data Mashup Challenge




Facilitators
Dr Tudor Groza (UQ) and Dr Armin Haller (W3C, CSIRO)
4:30 PMClose

7:00 PMSpeakers' and Sponsors' Dinner

Common Room Sessions

Time

Foyer

Common Room

Session Speakers

10:30 AMEnergy & Contact Break
11:00 AM
Overcoming obstacles in the Execution process - challenges and solutions




Case Study OneDennis Doolette, ASG


Case Study TwoJohn Weaver, Office of Spatial Data Management Margie Smith, Office of Spatial Data Management


Case Study ThreeTBC
12:30 AMLunch

Day 3 - Friday 27th May, 2011

Hall Sessions

Time

Foyer

Hall

Session Speakers

9:00 AM
RECAP FROM DAY ONE AND TWO Overview of Day Three
9:10 AM
Sub Keynote 5 Bringing Diversity TogetherTim Turner, ADFA


Case Study OneStephen Machin, Data Consultant


Case Study TwoLes Kneebone, Schools Online Thesaurus


Case Study ThreeMohsen Kalantari, University of Melbourne
10:30 AMEnergy & Contact Break
11:00 AM
PROFESSIONAL DEVELOPMENT


Professional Development 1 - Hands On WorkshopGov 2.0 and data.gov.au - Lisa Cornish, Department of Finance & Deregulation


Professional Development 1 - Hands On WorkshopData Visualisation - Mitchell Whitelaw, University of Canberra
12:30 AMLunch

1:30 PM
SPEAKER DEBATE


Speakers Speakers from throughout the programme


CASE STUDY AWARDS


CLOSING SESSION
3:00 PMOnsite Drinks
3:30 PM
BIRDS OF A FEATHER SESSIONS

4:30 PM
Close

Common Room Sessions

Time

Foyer

Common Room

Session Speakers

10:30 AMEnergy & Contact Break
11:00 AM
PROFESSIONAL DEVELOPMENT


Professional Development 1 - Hands on WorkshopRon Dunn, Microsoft Australia


Professional Development 2TBC
12:30 AMLunch

Thursday, April 14, 2011

Designing for Democratic Dialogue

I will be speaking on "Designing for Democratic Dialogue: More then Mating iPads" at Meta 2011, Australian National University, 25 to 27 May, 2011 .

Name: Tom Worthington
Title: Adjunct Senior Lecturer
Organisation: Research School of Computer Science, The Australian National University

Stream: Overcoming obstacles in the Execution process - challenges and solutions
Your session title: Designing for Democratic Dialogue: More then Mating iPads
Session Time: 11.00 am on Thursday 26th May, 2010
Duration: 30 minutes

Abstract

Tom Worthington discusses how to integrate on-line systems and buildings using metadata, to allow people to talk, learn and make decisions together, using a new $327M centre to be built in Canberra as an example. Tom outlines the work he has been doing at the Australian National University preparing online open source teaching materials on metadata, e-document and records management for public servants in Australia and developing nations. He argues that we need to go beyond the latest fads, such as iPads, and consider the fundamentals of how people have a discussion and make decisions in a globally connected democratic society.

See also:

Biography
Tom Worthington is a CSIRO Visiting Scientist, independent ICT consultant and an Adjunct Senior Lecturer in the Department of Computer Science at the ANU. In 2010 Tom received the ACS Canberra ICT Award for the design of the ANU Green ICT Course. He was elected a Fellow of the ACS in 1999 for his contribution to the development of public Internet
policy in Australia. Tom is a past president, Fellow and Honorary Life Member of the ACS, a voting member of the Association for Computing Machinery and a member of the Institute of Electrical and Electronics Engineers.

Tuesday, October 19, 2010

Web Standards for the Australian Government

Greetings from the Australian Defence Force Academy (ADFA) in Canberra, where the October Web Standards Group meeting was held.

This meeting is sponsored by the Defence Department and so the location is appropriate. However, the ADFA Adams Hall is not the best location for a meeting. This is a multi-purpose hall with a polished wooden floor and steeply ranked seating at the back. It looks like a US college gym and at any moment I expected a cheer leading squad to march in.

Today's speakers were:

1: Neil Philips - FOI Legislative Requirements to Publish Information On the Web
2: Raven Calais - WCAG 2.0 and the Website Accessibility National Transition Strategy
3: Gordon Grace - Making Better Use of On-line Data
4: Eileen Tannachion - Changes to the Australian Government Locator Service Metadata Standard

These are all interesting topics, but this seems like twice as many speakers as it is reasonable to fit into such a format.

The MC for the day was Tony Corcoran, Assistant Secretary, Freedom of Information and Information Management Branch, Department of Defence. He admitted that the Defence Department was not well prepared for new Government FOI legislative requirements (but it sounded like they were making rapid progress to be ready in time). Defence is doubling the capacity of their records management system from 30,000 to 60,000 users. An imaging system is being installed. Also many routine manuals which are currently on the internal intranet will be moved to the Internet to avoid the need for FOI requests.

Tony modestly said that his area of Defence was not "technical" being staffed by policy people. I have no doubt that there are suitably qualified people from information disciplines in Defence to write policy (I used to be one of them).

1: Neil Philips "FOI Legislative Requirements to Publish Information On the Web".

The new FOI procedures from 1 May 2011 are for more proactive disclosure. Public servants have protection under the legislation if they accidentally release something they should not. The legislation provides for agencies to sell documents, but hopefully most material will be provided freely online.

The main requirement is that the agency publish on its web site a list of information about the information they have (metadata) an organisation chart and other details about what the agency does. What was not clear to me was if there are standards for the format used for lists of information. It would make sense if all agencies used the same format and there was a government wide search facility provided. The Information Commissioner is expected to produce guidelines in November.

2: Raven Calais - WCAG 2.0 and the Website Accessibility National Transition Strategy

Raven started by saying the presentation would be provided afterwards, so I shouted out "in an accessible format?". She replied that there were some accessibility problems with Powerpoint and so the presentations would be offered in other formats.

Raven pointed out that accessibility is not just for a small group identified as "disabled", such as just the blind. Accessibility is an issue for much of the community at different times in their lives. Currently 20% of the Australian population identify themselves as having a disability. People with a disability have a higher unemployment rate. Accessibility is about social inclusiveness.

The Online and Communications Council of Australia agreed that all federal, state and local government web sites would be WCAG 2 complaint by November 2012.

Federal FMA agencies are required to be Level A compliant by 31 December 2012 and Level double A by 31 December 2014.

AGIMO has a National Transitional Strategy. This involves agencies first taking a stock take of what web sites they have, then checking current compliance, then assessing the publishing process and what barriers there might be. Barriers might be a lack of training in accessibility for web staff in a decentralised web publishing process.

AGIMO is developing a Community of Expertise (COE) under the AGIMO blog. This will then be updated to be a forum and have a document repository.

Raven stated that PDF, RTF and MS Word files are not accessible and so accessible HTML alternatives are required for these. I found this a refreshingly frank and practical approach. In theory it is possible to create accessible PDF, RTF and MS Word files, but as Raven says, there are not sufficient tools and techniques to support these in practice. In my view a sensible approach for agencies would be to implement accessible HTML which also displays and prints well. Agencies could then dispense with the complexity and expense of creating versions of documents in PDF, RTF and MS Word. The one HTML version would be suitable for all uses.

Raven nominated Canada as leading the way with accessibility.

Expected skill sets for roles are to be released soon. This would help me in teaching web accessibility to public servants at ANU.

I was very impressed with Raven's practical approach to accessibility.

Funnelback then provided afternoon tea.

3: Gordon Grace then talked on "Making Better Use of On-line Data".

Gordon pointed out that data web sites are not that exciting and data.gov.au (which is not online yet) will be no exception. The idea is to provide access to "raw data" which can then be combined and processed. To me this is conceptually very similar (and uses many of the same technical standards) as data repositories for research. The USA's data.gov was launched May 2009, Australia's beta data.Australia.gov.au ina October 2009, UK's data.gov.uk relaunched May 2009. AGLS, AGIFT, DCAT, Dublin Core, hCard, vCard and X500 were some standards used for gov.au.

Gordon pointed out that budget papers are now being published under a creative commons licence, but the data tables are currently GIF images and so not usable as data.

Gordon mentioned that he would not be able to in in GOVDEX online discussions of data in the future as he had left the public service and so would not have a gov.au email address. I found this curious as I have previously taken part in GOVDEX discussions as an industry expert.

Gordon showed an interesting example of XHTML with RDFa embedded. This allows data fields (such as phone numbers) to be identified in web pages. This allows both human and machine readable web pages. He pointed out these could be particularly useful for smart phones, if standards were supported. One difficulty this will cause is that "hits" on web sites may be reduced as data can be extracted from the web site once and provided via an intermediary. Gordon suggested that academics working on citation statistics might have a solution for this, but judging by the session I attended at ANU yesterday on assessing research.

Gordon suggested that providing data would be one way for agencies to easily able to meet FOI requests.

4: Eileen Tannachion - Changes to the Australian Government Locator Service Metadata Standard

Eileen started by pointing out that AGLIS is now a Australian Standard AS 5044-2010 and so is not just for government use. The updated standard supports new Dublin Core features. Thesauri are AGIFT and TAGS.

AGRkMS is a subset of SPIRIT. AGLS has considerable compatibility with AGRkMS but is not a strict subset of it.

Recent changes to AGLS include: linked data, semantic web and 2008 DC abstract model. AGLS qualifiers are "aglsterms". Some XML examples and encodings were removed. Five additional DC terms were added and included in AGLS. Two new AGLS terms were added: dateLicenced and protectiveMarking. The document type vocabulary is now common with AGRkMS. AGLS.audience has been replaced ith DC.audience. DC.Coverage.postcode will be replaced with a geo-spatial term still being worked on. Some other vocabularies have been updated. Some properties are now "recommended".

Challenges with AGLS include implementing in HTML 4.01 (I wonder about HTML 5?). Also the issue Google is starting to collect some of the metadata (will Funnleback?).

Social media advice was issued September 2010. Web Archiving Policy was will be issued the end of October 2010. The new AGLS manual will be issued as an exposure draft in November 2010. This will be useful for my new "Electronic Document Management" course at the ANU.

Ruth Ellison ended by asking for help with future WSG events: organising, speakers, venues and sponsors.

Wednesday, August 26, 2009

Australian National Data Service

Greetings from the Australian National University in Canberra where Ian Barnes is giving a presentation on the Australian National Data Service to my e-commerce students. ANDS aims to make the data behind research in Australia accessible online. The services provided are both for human readers to search for data and then machine to machine web services to access the data.

One interesting question is why scientists would share their data. One reason would be that this will tend to result in the scientist's work being more widely cited and thus promoting their career. A less obvious reason is that by making the data available will help ensure the data is preserved for long term use, including by the original creator. Another reason is that this may be required by funding bodies to prevent academic fraud.

Interestingly some of the initial data in the ANDS system is research data about humpback whales near the location for the proposed north west multi-billion dollar gas platform.

The service provides a google map interface using the geotagging information in the metadata. The service uses a different metadata standard to the ISO19115/19139 standard which is used for some repositories, but there is provision for conversion of the data. The service uses the same OAI interface as used for electronic document repositories. The service also provides persistent identifiers.

The service has a harvesting process to search registered data sources to find new collections of data to index. The service uses RIF-CS based on ISO2146 to represent data in XML format.

Sunday, July 12, 2009

Designing a course module in Metadata and Electronic Data Management - Part 3

Having the general direction for the course module on Metadata and Electronic Data Management, what should the students be able to do at the end of the IT in e-Commerce course? The numerous seminars on how to design courses I have attended over the last year have emphasised the importance of learning objectives and of assessment as part of the learning process. This is not just about setting a test at the end to see the students can remember things.

In order to prepare some Learning Outcomes, I did a web search for other courses on metadata and document management to see what they had. The first found was the University of Manchester's "COMP30352: Information Retrieval, Hypermedia and the Web", however this seems more of a web course. The second found was "IT in E Commerce COMP6341" at the ANU. It took me some moments to realise this was the course I was teaching. Someone had already written the learning outcomes:
Learning Outcomes:

The focus of this course is on document representation, knowledge discovery, storage and retrieval, and electronic trading. The areas covered include XML, XSL, DTD, metadata, data management and different forms of trading such as deliberative, spontaneous and auctions. Other topics will be included to match recent developments and maturation of the area, such as web application frameworks, web services and the semantic web Rationale Electronic Commerce is an area that is growing in leaps and bounds. The use of information technology is at the heart of electronic commerce. It is important that students doing a degree in Information Systems have a sound understanding of the role that information technology plays in electronic commerce. This course, along with the course on Internet, Intranet and Document Systems, is meant to do just that. It looks at some of the current and potential uses of information technology in electronic commerce. The topics covered include document representation in the form of XML, XSL, DTD's; knowledge discovery using metadata and data mining; data management as in the case of Digital Libraries and Electronic Document Management; trading, including deliberative, spontaneous and auctions; and security (public keys, PKI, digital signatures, etc). Other topics would be included as the area matures. It is anticipated that this course will be of interest to people in the industry as well.

This course is responsible for:

  • current trends in representation of data and documents on the web
  • knowledge discovery in the form of metadata and data mining
  • database management in electronic commerce
  • electronic trading
  • security in electronic commerce.

The following topics will be addressed:

  • knowledge representation - XML, XSL, DTD, CSS
  • knowledge discovery - metadata and data mining.
  • data management - digital libraries and electronic document management
  • trading - deliberative, spontaneous and auctions
  • security - public keys, symmetric keys, PKI, authentication, digital signatures, etc.

Upon completion of this course, the student will be able to do the following:

  1. Describe the XML language, write simple DTD's, write CSS style sheets for documents, and explain where XML can be applied to advantage and why.
  2. Describe the use of metadata, and describe the current trends in data mining.
  3. Describe how digital libraries and electronic document management work.
  4. Describe the different kinds of trading that an individual, or an organisation, can do electronically. Explain the advantages and limitations of electronic trading, and the risks involved.
  5. Explain why security is such a big issue in electronic commerce and how it is being addressed. Describe key concepts like public keys, symmetric keys, PKI, authentication and digital signatures. Given a system specification, come up with a design that allows secure transmission of information.
From: "IT in E Commerce COMP6341", Course Details, ANU, 2009

The last part which is of interest, saying what the student should be able to do on completion of the course:
  1. Describe the XML language, write simple DTD's, write CSS style sheets for documents, and explain where XML can be applied to advantage and why.
  2. Describe the use of metadata, and describe the current trends in data mining.
  3. Describe how digital libraries and electronic document management work.
  4. Describe the different kinds of trading that an individual, or an organisation, can do electronically. Explain the advantages and limitations of electronic trading, and the risks involved.
  5. Explain why security is such a big issue in electronic commerce and how it is being addressed. Describe key concepts like public keys, symmetric keys, PKI, authentication and digital signatures. Given a system specification, come up with a design that allows secure transmission of information.

The wording of this is curiously loose, for example "...why security is such a big issue ...". Also use of the term "describe" seems too passive for a IT course, which should be about being able to do things, not just describe them.
  • Describe the XML language, write simple DTD's, write CSS style sheets for documents, and explain where XML can be applied to advantage and why.
  • Describe the use of metadata, and describe the current trends in data mining.
  • Describe how digital libraries and electronic document management work.
  • Describe the different kinds of trading that an individual, or an organisation, can do electronically. Explain the advantages and limitations of electronic trading, and the risks involved.
  • Explain why security is such a big issue in electronic commerce and how it is being addressed. Describe key concepts like public keys, symmetric keys, PKI, authentication and digital signatures. Given a system specification, come up with a design that allows secure transmission of information.
  • Extracting the items relating to metadata and electronic document management:
  • Describe the use of metadata ...
  • Describe how digital libraries and electronic document management work.
  • A better way to put this may be:
    1. Use the XML language to define document strutures
    2. Use XSLT to transform documents and CSS to present them
    3. Use metadata to describe documents for use in digital libraries and electronic document management
    In the course I previously spent a lot of time describing how e-publishing systems worked in general, and the history of publishing, to provide a context for XML based publishing. This is of little interest to current day students of IT, to whom paper publishing and library card catalogues are not part of their experience, having been born after e-publishing and computer catalogues had become the norm.

    Also I spent a lot of time saying what was wrong with PDF. While there is still much wrong with PDF, there seems little point in spending time on that, when instead alternatives could be presented. Otherwise this is much like presenting what is wrong with private cars and roads to transport engineers.

    Some other parts of the course can be emphasised. As an example the IFIP Digital Library which was speculated about last year has now become a reality, with the ANU providing the system for users around the globe. It is unlikely that students will have much interest or understanding of the idea that the material in the digital library was once available primarily on paper. They may also have difficulty making the connection between the digital library and the buildings on campus which are still called a library. The lower floors of these buildings have been cleared of most paper, to provide space for computer access, with perhaps a few serials and new books on display as historical curiosities.

    Designing a course module in Metadata and Electronic Data Management - Part 2

    Having worked out how much material is needed for a course module on Metadata and Electronic Data Management, what exactly is it for? The description of the IT in e-Commerce course refers to: "... document representation (XML, XSL, DTD, CSS), knowledge discovery (meta-data, information retrieval), data management (digital library, electronic document management), trading (spontaneous, deliberative, auctions) and security (encryption, public key, symmetric key, PKI, authentication, etc). ..."). So the course is about how to design e-documents, protect and manage them, so that they can be found and used for transactions in business.

    The ANU is in Canberra, the seat of Australian Government and many students work for the government and so many of the examples in the course are drawn from government business. Also because some of the students go on the be academics and researchers, the example of academic publishing has been used as an example.

    There are some common problems for people in business, government and academia: how do I create an e-document which will be flexible for use by different people at different times? How can it be kept? How can it be found? How can it be authenticated?

    The problem with e-documents is coping with the volume of material. Workers are being overwhelmed with the volume of email and attachments. Just as they get used to e-mail, along comes blogs, wikis, twits and other technologies to cope with.

    The course teaches the use of XML based technology. The idea is that you create the documents in a format which reflects the information content, separate from how the document will look to the reader. This goes beyond the separation of structure from presentation for web pages. With a HTML document, if you strip off the presentation layer, the document still looks like a text document. However, with XML data, with the data definitions removed, you have just a jumble of letters and numbers.

    The key point in terms of knowledge discovery is metadata. The metadata can be used to find the data and also substitute for it in many processes. In the case of XML documents metadata is also used to define the data structure.

    Students have considerable difficulty understanding what metadata is. The popularisation of metadata trough Tags on web resources, such as images, blog postings and instant messages, provides a useful example.

    Previously I introduced metadata from the technical point of view and then illustrated it with popular examples such as Tags. Perhaps it might be to reverse this and introduce tags first.

    In introducing electronic document management I went into considerable detail about the procedures used by the Australian Government. While this was popular with professional records managers and archivists, it was of little interest to IT students. It also seems a loosing battle in the government with such records management systems falling into disuse. While I can't solve the problems of the government by myself, perhaps I can suggest some different techniques to the students.

    Deleting most of the material about records management procedures will make room for some new material on new electronic formats for use by business.

    Saturday, July 11, 2009

    Designing a course module in Metadata and Electronic Data Management

    How do I create a course module on "Metadata and Electronic Data Management"? This year I have again been asked to help teach students in the course Information Technology in Electronic Commerce (COMP3410) at ANU.

    The content will be much the same as last year, but I would like to package the material up more neatly. This is partly prompted by my resolution last year that I had given my last lecture. Also the material currently lacks a coherent theme as is much longer than it should be. In addition I would like to revise some of the material which is based on old EDI standards and old Australian government records management guidelines.

    How much?

    But where to start? The first step is to get some idea of how much material is required. Previously I gave about five or six lectures and a lab covering the material. This equates to about two weeks of a course.

    Last years notes for the course are the equivalent of 36 A4 pages, or about 18 pages per week. At one end of the spectrum my notes for Green ICT Strategies (COMP&310) are about 3 A4 pages per week, whereas the web technology lectures for COMP2410/6340 - Networked Information Systems are 24 pages per week. This range can be accounted for by the Green ICT course being at the masters level and assuming the student does more independent reading. Also the Green ICT notes are mostly English text, whereas the web technologies notes contact examples of code, which take up more space. So at 18 pages per week, the metadata and data management notes seem about right, but perhaps could be trimmed a little.

    Where does it fit in the skill set?

    The Metadata and Electronic Data Management materials was just whatever I thought might be relviant, when first presented in 2000. It was designed to fit with what else was included in the course and related courses, but no thought to how it fitted in the career of the people who were being trained.

    To position the Green ICT Strategies course, the Skills Framework for the Information Age (SFIA) was used. A search of SFIA found only one Skill definition which mentioned metadata, which was Information management (IRMG) :
    The overall management of information, as a fundamental business resource, to ensure that the information needs of the business are met. Encompasses development and promotion of the strategy and policies covering the design of information structures and taxonomies, the setting of policies for the sourcing and maintenance of the data content, the management and storage of electronic content and the analysis of information structure (including logical analysis of data and metadata). Includes overall responsibility for compliance with regulations, standards and codes of good practice relating to information and documentation records management, information assurance and data protection. ...

    From: Information management (IRMG) , Strategy & planning, Information strategy, SFIA, Version 3, 2005
    For the undergraduate version of the course this would be at SFIA level 4 and Level 5 for the postgraduate version. The higher SFIA level has more management and less technical responsibility.

    A search of SFIA for "data management" turned up reference in Business analysis (ANAL), System software SYSP and Enterprise architecture STPL. None of these seem to fit with the intended content, the closes is business analysis, but that has too much business and not enough technology.

    A search of SFIA for "records management" turned up the
    Information management (IRMG) skill again.

    A search for "publishing" found Information content publishing ICPM, but this seems to relate more to web design.

    So of all these
    Information management (IRMG) seems most relevant.

    Metadata and data management for governance

    Looking at the higher level, IM is in the SFIA Subcategory of Information strategy. This also includes the Corporate governance of IT (GOVN). At first glance governance does not seem relevant to metadata and data management, being more for a course on IT project management.

    However, many of the examples I use to explain the uses of metadata and data management from government and involve the keeping of records for demonstrating that an organisation is being properly run. It occurred to me that it might be useful to turn around the emphasis on record keeping in case you are taken to court, to instead start by looking at what is needed in terms of electron communications and documents for running an organisation well at the highest level, that is governance. With this I could start off with the principles of governance and then show how to make effective use of tools like instant messaging and blogs in a corporate environment.




    Friday, July 10, 2009

    The Obama effect: how to win a political campaign with the web

    This year I have again been asked to help teach students about Metadata and Electronic Data Management in the course Information Technology in Electronic Commerce (COMP3410) at ANU. The content will be much the same as last year, but I would like to introduce some central themes to what otherwise looks like a random collection of technologies and techniques.

    Recently a policy adviser for an MP pointed out that there is an election coming up in Australia relatively soon and that political parties are interested in how President Obama used the web to help win. They suggested if I was to offer a course in how to do web based campaigning that would be very popular. How to do political campaigning is not something I have experience, nor much interest, in. What I find more interesting is how to use the technology to run the country, after you win the election.

    What I have found disappointing in the Australian case is that while a political party might use the Internet to help win the election, once in office, this is forgotten and the political process reverts to a manual one, which disenfranchises most of the citizens. Similarly the public service might use the Internet to put out public information campaigns, but seems unable to use the technology to communicate effectively with the public.

    Perhaps the solution to this is to bring the political and administrative processes to together and use a uniform set of technologies and techniques for both. That way the politicians could run the campaign and then be ready to work the same way to run the country. At the same time the public service would not see this way of working as alien.

    To put all that in a more concrete way, I thought I might give one of my seminars for COMP3410, to which the political advisers would be invited, on:
    The Obama effect: how to win a political campaign with the web

    Using blogs, twitter, Google Wave, email, podcasts, the web and the Internet to run a campaign and a country.

    Abstract: Much has been written about how President Obama used the web to campaign. The next Australian federal election must be held by April 2011. By then there will be a new generation of Internet and mobile phone technology. How will it be used for campaigning? Can the technology extend beyond the election campaign to give Australian citizens more of a voice in policy development and running the country? Are there some general principles which can be applied to existing and emergence technologies? Tom Worthington explains how the Metadata and Electronic Data Management techniques underlying web technologies can provide a road map to the future.

    See:

    Saturday, July 04, 2009

    Video Archiving System for the Australian Parliament

    The Department of Parliamentary Services has issued a Request for Tender for "Provision of Equipment and Services for Media Asset Management and Archiving Solution". This is a digital system for the capture, delivery, and archiving of audio and video from the House of Representative, Senate, hearings and the like. There is also 55,000 hours of broadcast quality video to be digitised and catalogued. There is a detailed tender document available online, with Metadata Exchange, Data Storage Backup and Recovery Principles, Style Manual, User Permissions, ICT Architecture and Standards. Also there will be a briefing at Parliament House, 21 May 2009.
    DPS is seeking:

    1. hardware, software and services to construct a digital system for the capture, segmentation, delivery, archiving and management of audiovisual and audio-only content; and
    2. additional services to digitise the estimated 55,000 hours of recorded broadcast quality video of Parliamentary proceedings and special events (back-capture project). ...

    From: Provision of Equipment and Services for Media Asset Management and Archiving Solution, DPS09001, Department of Parliamentary Services, 5-May-2009

    Wednesday, May 06, 2009

    Parliament Media Archive Specification

    The Federal Department of Parliamentary Services has issued a Request for Tender for "Provision of Equipment and Services for Media Asset Management and Archiving Solution" (ATM ID DPS09001, 5-May-2009). They are seeking hardware, software and services for digital capture, segmentation, delivery, archiving and management of audiovisual content from the Parliament. They also have an existing 55,000 hours of broadcast quality video of Parliamentary proceedings to digitise. What makes this interesting is that the tender documents (available to registered companies) include a detailed specification of the system including free TV metadata:

    6 STATEMENT OF REQUIREMENT (SOR) ... 33
    6.1 Overview ... 33
    6.2 Content Capture ... 35
    6.3 Content Enrichment ... 39
    6.4 Non Linear Editing ... 41
    6.5 Content Storage ... 42
    6.6 Content Distribution—Platforms ... 43
    6.7 Content Distribution—Client Access ... 44
    6.8 System Management—Administration .... 48
    6.9 System Management—Health/Status Monitoring .... 49
    6.10 System Management—Information Reporting ... 50
    6.11 System Management—Account Access and Content Security ... 51
    6.12 Data Migration of File Based Content ... 52
    6.13 System Integration ... 52
    6.14 System Architecture and Technology ... 54
    6.15 Project Implementation Plan .... 55
    6.16 Acceptance Testing ... 56
    6.17 Documentation .... 58
    6.18 Training .... 60
    6.19 Support and Maintenance ... 60
    6.20 Additional Services—Back-Capture of Archive Content ... 61
    ...
    9 STAGE 3—TECHNICAL REQUIREMENTS ... 79
    9.1 Solution Overview ... 79
    9.2 Content Capture ... 79
    9.3 Content Enrichment ... 85
    9.4 Non-Linear Editing .... 89
    9.5 Content Storage ... 90
    9.6 Content Distribution—Platforms ... 93
    9.7 Content Distribution—Client Access ... 94
    9.8 System Management—Administration ... 100
    9.9 System Management—Health/Status Monitoring ... 103
    9.10 System Management—Information Reporting .... 104
    9.11 System Management—Account Access and Content Security .... 106
    9.12 Data Migration of File Based Content ... 107
    9.13 System Integration .... 108
    9.14 System Architecture and Technology ... 110
    9.15 Project Implementation .... 113
    9.16 Acceptance Testing .... 113
    9.17 Documentation ... 116
    9.18 Training ... 118
    9.19 Support and Maintenance ... 119
    9.20 Additional Services—Back-Capture of Archive Content ... 121

    Appendix A—Metadata Exchange
    Appendix B—EMMS Metadata
    Appendix C—Data Storage Backup and Recovery Principles
    Appendix D—APH Style Manual
    Appendix E—User Permissions
    Appendix F—APH ICT Architecture and Standards
    Appendix G—Chamber Microphone Interface
    Appendix H—ScheduAll Data Schema
    Appendix I—ParlInfo Schema
    Appendix J—Broadcast Standards Manual ...

    From Table of Contents, "Provision of Equipment and Services for Media Asset Management and Archiving Solution", Department of Parliamentary Services (ATM ID DPS09001, 5-May-2009).

    Friday, August 22, 2008

    Sunday, August 17, 2008

    What is wrong with the OJS Schema?

    Since I was testing the IFIP Digital Library OAI interface, I thought I might as well test the one for the ACS Digital Library and register it with the Open Archives Initiative - Repository Explorer, so researchers could use it as an example of a working system. But it failed the XML Schema validation test. This was the only test failed, but is an important one and is a bit odd, as the archive seems to be working okay. Any one any thoughts?

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 2.0 : December 2006
    Open Archives Initiative :: Protocol for Metadata Harvesting v2.0
    RE Protocol Tester 1.46c :: UCT AIM :: December 2006

    (1) Testing : Identify
    URL : http://dl.acs.org.au/index.php/index/oai?verb=Identify
    Test Result : OK
    ---- [ Repository Name = ACS Digital Library ]
    ---- [ Protocol Version = 2.0 ]
    ---- [ Base URL = http://dl.acs.org.au/index.php/index/oai ]
    ---- [ Admin Email = dl@tomw.net.au ]
    ---- [ Granularity = YYYY-MM-DDThh:mm:ssZ ]
    ---- [ Earliest Datestamp = 2006-12-05T00:40:05Z ]

    (2) Testing : Identify (illegal_parameter)
    URL : http://dl.acs.org.au/index.php/index/oai?verb=Identify&test=test
    Test Result : OK

    (3) Testing : ListMetadataFormats
    URL : http://dl.acs.org.au/index.php/index/oai?verb=ListMetadataFormats
    Test Result : OK
    ---- [ Only oai_dc supported ]

    (4) Testing : ListSets
    URL : http://dl.acs.org.au/index.php/index/oai?verb=ListSets
    ------ Response from Xerces Schema Validation ------
    [Error] re.51bDjv:164:37: cvc-pattern-valid: Value 'crpit:Volume 1' is not facet-valid with respect to pattern '([A-Za-z0-9\-_\.!~\*'\(\)])+(:[A-Za-z0-9\-_\.!~\*'\(\)]+)*' for type 'setSpecType'.
    [Error] re.51bDjv:164:37: cvc-type.3.1.3: The value 'crpit:Volume 1' of element 'setSpec' is not valid.
    /tmp/re.51bDjv: 1632;20;0 ms (76 elems, 52 attrs, 0 spaces, 897 chars)
    ------- End of Xerces Schema Validation Report -------
    ------ Start of XML Response ------

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
    http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
    2008-08-17T01:32:59Z
    http://dl.acs.org.au/index.php/index/oai


    ajis
    Australasian Journal of Information Systems

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:ED
    Editorial

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:FT
    AJIS Featured Theme

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:ART
    Articles

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:FTA
    AJIS Featured Theme

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:FTB
    AJIS Featured Theme

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    ajis:FTC
    AJIS Featured Theme

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    jrpit
    Journal of Research and Practice in Information Technology

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    jrpit:ART
    Articles

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    crpit
    Conferences in Research and Practice in Information Technology

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    crpit:ART
    Articles

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">





    crpit:Volume 1
    Volume 1

    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
    http://www.openarchives.org/OAI/2.0/oai_dc.xsd">







    ------- End of XML Response -------
    Test Result : FAIL!
    **** [ERROR] XML Schema validation failed ...

    From: "Open Archives Initiative - Repository Explorer" test of
    ACS DL, explorer version - 1.46c : protocol version - 2.0 : December
    2006 (run 17 August 2008)
    
    

    Testing IFIP Digital Library OAI Interface

    For those wondering what the OAI interface I was asking librarians to test for the IFIP Digital Library: The Open Archives Initiative (OAI) defines a standard computer to computer interface (OAI-PMH) which can be used to query a digital library to see what information it has and in what formats. The IFIP Digital Library uses the Open Journal Systems (OJS) open source publishing system which has OAI built in.

    Normally you would point your own OAI software at the address of the IFIP DL and it would send transactions and extract data into your system. But you can also use some test tools to see what is happening. One of these is the Open Archives Initiative - Repository Explorer. With this you supply the address on an OAI system and then can pass queries and see the data. There is also an automatic test which sends a series of queries and checks the answers. These are used in the Conformance Testing for Basic Functionality, Error and Exception Handling by the OAI Registry. Here are the results of the test on the IFIP DL:

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 2.0 : December 2006
    Open Archives Initiative :: Protocol for Metadata Harvesting v2.0
    RE Protocol Tester 1.46c :: UCT AIM :: December 2006

    (1) Testing : Identify
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=Identify
    Test Result : OK
    ---- [ Repository Name = International Federation for Information Processing Digital Library ]
    ---- [ Protocol Version = 2.0 ]
    ---- [ Base URL = http://dl.ifip.org/iojs/index.php/ifip/oai ]
    ---- [ Admin Email = tom.gedeon@anu.edu.au ]
    ---- [ Granularity = YYYY-MM-DDThh:mm:ssZ ]
    ---- [ Earliest Datestamp = 2008-04-01T10:07:00Z ]

    (2) Testing : Identify (illegal_parameter)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=Identify&test=test
    Test Result : OK

    (3) Testing : ListMetadataFormats
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListMetadataFormats
    Test Result : OK
    ---- [ Only oai_dc supported ]

    (4) Testing : ListSets
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListSets
    Test Result : OK
    ---- [ Sample Set Spec = ifip ]

    (5) Skipping : ListSets (resumptionToken)
    This test is being skipped because it cannot or should not be performed.

    (6) Testing : ListIdentifiers (oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc
    Test Result : OK
    ---- [ Sample Identifier = oai:ifip.cs.anu.edu.au:article/711 ]

    (7) Skipping : ListIdentifiers (resumptionToken)
    This test is being skipped because it cannot or should not be performed.

    (8) Skipping : ListIdentifiers (resumptionToken, oai_dc)
    This test is being skipped because it cannot or should not be performed.

    (9) Testing : ListIdentifiers (oai_dc, from/until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2000-01-01&until=2000-01-01
    Test Result : OK

    (10) Testing : ListIdentifiers (oai_dc, set, from/until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=ifip&from=2000-01-01&until=2000-01-01
    Test Result : OK

    (11) Testing : ListIdentifiers (oai_dc, illegal_set, illegal_from/until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=really_wrong_set&from=some_random_date&until=some_random_date
    Test Result : OK

    (12) Testing : ListIdentifiers (oai_dc, from granularity != until granularity)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01&until=2002-01-01T00:00:00Z
    Test Result : OK

    (13) Testing : ListIdentifiers (oai_dc, from > until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2000-01-01&until=1999-01-01
    Test Result : OK

    (14) Testing : ListIdentifiers ()
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers
    Test Result : OK

    (15) Skipping : ListIdentifiers (metadataPrefix)
    This test is being skipped because it cannot or should not be performed.

    (16) Testing : ListIdentifiers (illegal_mdp)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=illegal_mdp
    Test Result : OK

    (17) Testing : ListIdentifiers (mdp, mdp)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&metadataPrefix=oai_dc
    Test Result : OK

    (18) Testing : ListIdentifiers (illegal_resumptiontoken)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&resumptionToken=junktoken
    Test Result : OK

    (19) Testing : ListIdentifiers (oai_dc, from YYYY-MM-DD)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01
    Test Result : OK

    (20) Testing : ListIdentifiers (oai_dc, from YYYY-MM-DDThh:mm:ssZ)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01T00:00:00Z
    Test Result : OK

    (21) Testing : ListIdentifiers (oai_dc, from YYYY)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001
    Test Result : OK

    (22) Testing : ListMetadataFormats (identifier)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListMetadataFormats&identifier=oai:ifip.cs.anu.edu.au:article/711
    Test Result : OK
    ---- [ Only oai_dc supported ]

    (23) Testing : ListMetadataFormats (illegal_id)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListMetadataFormats&identifier=really_wrong_id
    Test Result : OK

    (24) Skipping : GetRecord (identifier, metadataPrefix)
    This test is being skipped because it cannot or should not be performed.

    (25) Testing : GetRecord (identifier, oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=oai:ifip.cs.anu.edu.au:article/711&metadataPrefix=oai_dc
    Test Result : OK

    (26) Testing : GetRecord (identifier)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=oai:ifip.cs.anu.edu.au:article/711
    Test Result : OK

    (27) Testing : GetRecord (identifier, illegal_mdp)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=oai:ifip.cs.anu.edu.au:article/711&metadataPrefix=really_wrong_mdp
    Test Result : OK

    (28) Testing : GetRecord (oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&metadataPrefix=oai_dc
    Test Result : OK

    (29) Testing : GetRecord (illegal_id, oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=really_wrong_id&metadataPrefix=oai_dc
    Test Result : OK

    (30) Testing : GetRecord (invalid_id, oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=invalid\"id&metadataPrefix=oai_dc
    Test Result : OK

    (31) Testing : ListRecords (oai_dc, from/until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2000-01-01&until=2000-01-01
    Test Result : OK

    (32) Skipping : ListRecords (resumptionToken)
    This test is being skipped because it cannot or should not be performed.

    (33) Skipping : ListRecords (metadataPrefix, from/until)
    This test is being skipped because it cannot or should not be performed.

    (34) Testing : ListRecords (oai_dc, illegal_set, illegal_from/until)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&metadataPrefix=oai_dc&set=really_wrong_set&from=some_random_date&until=some_random_date
    Test Result : OK

    (35) Testing : ListRecords
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords
    Test Result : OK

    (36) Testing : ListRecords (oai_dc, from granularity != until granularity)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2001-01-01&until=2002-01-01T00:00:00Z
    Test Result : OK

    (37) Testing : ListRecords (oai_dc, until before earliestDatestamp)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&metadataPrefix=oai_dc&until=2007-04-01T10:07:00Z
    Test Result : OK

    (38) Testing : ListRecords (oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&metadataPrefix=oai_dc
    Test Result : OK

    (39) Testing : ListRecords (illegal_resumptiontoken)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListRecords&resumptionToken=junktoken
    Test Result : OK

    (40) Testing : ListIdentifiers (oai_dc, set)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=ifip
    Test Result : OK

    (41) Testing : GetRecord (identifier, oai_dc)
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&identifier=oai:ifip.cs.anu.edu.au:article/711&metadataPrefix=oai_dc
    Test Result : OK
    ---- [ Found setSpec in header ]

    (42) Testing : IllegalVerb
    URL : http://dl.ifip.org/iojs/index.php/ifip/oai?verb=IllegalVerb
    Test Result : OK

    ---- Total Errors : 0


    From: "Open Archives Initiative - Repository Explorer" test of IFIP DL, explorer version - 1.46c : protocol version - 2.0 : December 2006 (run 17 August 2008)

    The Self description for the archive:

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 2.0 : December 2006

    http://dl.ifip.org/iojs/index.php/ifip/oai?verb=Identify

    Archive details : http://dl.ifip.org/

    Archive Self-Description

    Repository NameInternational Federation for Information Processing Digital Library
    Base URLhttp://dl.ifip.org/iojs/index.php/ifip/oai
    Protocol Version2.0
    Admin Emailtom.gedeon@anu.edu.au
    Earliest Datestamp2008-04-01T10:07:00Z
    Deleted Record Handlingno
    GranularityYYYY-MM-DDThh:mm:ssZ
    Compressiongzip
    Compressiondeflate
    Other Information
    description:
    oai-identifier:
    scheme: oai
    repositoryIdentifier: ifip.cs.anu.edu.au
    delimiter: :
    sampleIdentifier: oai:ifip.cs.anu.edu.au:article/1

    Request : http://dl.ifip.org/iojs/index.php/ifip/oai, verb=Identify
    Response Date : 2008-08-17T04:35:13Z

    Requesting a list of metadata formats returns:

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 1.0/1.1/2.0 : December 2006

    http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListMetadataFormats

    Archive details : http://dl.ifip.org/

    List of Metadata Formats

    Click on the link to view schema

    Prefix=[oai_dc]
    NameSpace=[http://www.openarchives.org/OAI/2.0/oai_dc/]
    Schema=[http://www.openarchives.org/OAI/2.0/oai_dc.xsd]

    Prefix=[oai_marc]
    NameSpace=[http://www.openarchives.org/OAI/1.1/oai_marc]
    Schema=[http://www.openarchives.org/OAI/1.1/oai_marc.xsd]

    Prefix=[marcxml]
    NameSpace=[http://www.loc.gov/MARC21/slim]
    Schema=[http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd]

    Prefix=[rfc1807]
    NameSpace=[http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1807.txt]
    Schema=[http://www.openarchives.org/OAI/1.1/rfc1807.xsd]


    Request : http://dl.ifip.org/iojs/index.php/ifip/oai, verb=ListMetadataFormats
    Response Date : 2008-08-17T00:56:06Z

    All the records in the archive can then be displayed:

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 2.0 : December 2006

    http://dl.ifip.org/iojs/index.php/ifip/oai?verb=ListIdentifiers&metadataPrefix=oai_dc

    Archive details : http://dl.ifip.org/

    List of Record Identifiers

    Select a link to view more information ...

    header: identifier : oai:ifip.cs.anu.edu.au:article/711 datestamp : 2008-04-01T10:07:00Z setSpec : ifip:SS [display record in Dublin Core] [display metadata formats]

    ...

    header:
    identifier : oai:ifip.cs.anu.edu.au:article/1273
    datestamp : 2008-07-16T10:07:00Z
    setSpec : ifip:SS

    [display record in Dublin Core] [display metadata formats]


    Request : http://dl.ifip.org/iojs/index.php/ifip/oai, verb=ListIdentifiers, metadataPrefix=oai_dc
    Response Date : 2008-08-17T03:31:36Z

    The metadata for a record can be selected:

    Open Archives Initiative - Repository Explorer

    explorer version - 1.46c : protocol version - 2.0 : December 2006

    http://dl.ifip.org/iojs/index.php/ifip/oai?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai%3Aifip.cs.anu.edu.au%3Aarticle%2F1273

    Archive details : http://dl.ifip.org/

    List of Fields

    header:
    identifier : oai:ifip.cs.anu.edu.au:article/1273
    datestamp : 2008-07-16T10:07:00Z
    setSpec : ifip:SS

    metadata:
    dc:
    title: Differentiated Survivability in a Distributed GMPLS-Based IP-over-Optical Network
    creator: David Harle
    creator: Saud Albarrak
    subject:
    subject:
    subject:
    description: A key element of the survivability cost is the amount of the additional capacity embedded in the network for recovery purposes. Generally, Internet Service Providers (ISPs) have the obvious aim of achieving the required level of survivability with minimum resource consumption and network cost. Therefore, in order to achieve such a challenge, it is necessary to move towards the multilayer differentiated survivability concept. In this paper, the focus is given to the investigation of the application of differentiated survivability concept with pre-allocated restoration technique considering a distributed GMPLS-based IP-over-optical mesh network under single and dual-link failure scenarios.
    publisher: International Federation for Information Processing
    contributor:
    date: 1970-01-01
    type: Peer-reviewed Article
    type:
    format: application/pdf
    identifier: http://dl.ifip.org/iojs/index.php/ifip/article/view/1273
    source: International Federation for Information Processing Digital Library; Optical Network Design and Modelling (ONDM 2008);
    language:
    coverage:
    coverage:
    coverage:
    rights: Copyright© International Federation for Information Processing. Most IFIP papers are Under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.


    Request : http://dl.ifip.org/iojs/index.php/ifip/oai, verb=GetRecord, metadataPrefix=oai_dc, identifier=oai:ifip.cs.anu.edu.au:article/1273
    Response Date : 2008-08-17T04:31:28Z