Вы находитесь на странице: 1из 19

OpenDocument 1.

2 Metadata Examples, Oct 22, 2009


Document identifier: 09-10-22-ODF-MetaData-Examples.odt Editors: Patrick Durusau <Patrick@durusau.net>, Svante Schubert <Svante.Schubert@sun.com>, Michael Stahl <Michael.Stahl@Sun.com>

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 1 of 19

October 22, 2009

Table of Contents
1 Overview......................................................................................................................................3 2 RDF/XML: a Brief Overview..........................................................................................................5 3 Storing Extensible Metadata........................................................................................................6 3.1 Content Files.........................................................................................................................6 3.2 RDF/XML Metadata Files .....................................................................................................6 3.3 The Metadata Manifest..........................................................................................................7 4 Describing Document Content.....................................................................................................8 4.1 Metadata describing the OpenDocument Document............................................................8 4.2 Metadata describing an OpenDocument Element.................................................................9 4.3 Metadata describing a Part of the Document......................................................................10 5 Metadata Scenarios...................................................................................................................13 5.1 Content described by Metadata...........................................................................................13 5.2 Content equivalent to Metadata..........................................................................................16 6 Metadata Proposal's FAQ ..........................................................................................................18 AppendixA. References.................................................................................................................19

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 2 of 19

October 22, 2009

1 Overview
Metadata lies at the heart of making documents more useful for their authors and subsequent users. This document provides an overview of the new metadata features in OpenDocument (1.2), which enable users and organizations to enhance their documents with the metadata of their choice. The Metadata SC of the OpenDocument TC at OASIS developed nineteen use cases that shaped the current metadata proposal.1 Those use cases were:

Accessibility Information Asymmetric Metadata Automatically Generated Metadata Bibliographies and Citations Content Tagging Conversion Metadata Document as Web Service Enhanced Search Extrinsic Metadata Intellectual Property Metadata Templates Ontology Validation Realtime Collaborative Editing Revision Metadata Rich Semantic Metadata Security Metadata Semantic Web Ready Documents Workflow Management

The use cases read like a wish list of metadata capabilities and the question facing the SC was how to make that possible. The resolution of that question requires extensible metadata as no committee proposal could anticipate all the contours of any one use case, much less all of them. Rather than re-inventing the metadata wheel, the metadata proposal adopted the W3C Resource Description Framework (RDF). RDF provides a flexible and extensible data standard that allows users and organizations to describe their documents in ways that fit their own needs. The contribution of the SC was to develop mechanisms in OpenDocument that enable the robust linking of RDF/XML metadata to OpenDocument content.

1 OpenDocument_Metadata_UseCases8Oct2006
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 3 of 19 October 22, 2009

A complete explanation of RDF is beyond the scope of this document but a short overview is provided to orient the reader to the mechanisms added to support the use of RDF in OpenDocument documents.2 The overview of RDF is followed by Storing Extensible Metadata, Describing Document Content and we conclude with Metadata Scenarios to provide a glimpse of the future that is made practical by the new metadata mechanisms. The scenario examples do not represent limitations of the metadata mechanisms but are evidence of the limited imaginations of the authors. This document is maintained by the OpenDocument Metadata SC so please contribute examples for inclusion at the SC's webpage at: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=officemetadata. A more detailed reference document with longer examples and accompanied by example files is in preparation by the Metadata SC. The current version of that document is available at the SC website.

2The examples in this document expose the underlying ODF and RDF mechanisms in a way that would not be seen by the average author/user of a document. That is to say that implementations will hide many of the details of how the metadata mechanisms work while providing users with the benefits of using RDF based metadata.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 4 of 19 October 22, 2009

2 RDF/XML: a Brief Overview


This overview does not cover RDF/XML in detail. Only the RDF concepts that are necessary for basic use of the new metadata features are covered below. RDF is a complex specification and can be used in full with OpenDocument files. For more detailed information on RDF readers should consult the RDF page at the W3C.3 An RDF statement has three parts, a subject, a verb and an object. It is like the simple grammar taught in grade school but has power that those grammar lessons did not. Assume that we want to make the following statement into an RDF statement: Patrick (subject) has (verb) big feet (object) In that case we would have the following (in one RDF syntax)4:

<(some IRI)/#Patrick> <(some IRI)/#has> <(some IRI)/#Bigfeet> . Note that we still have the same subject-verb-triple but it is expressed differently.
There are advantages to expressing the statement in RDF. First, we can gather up other information about Patrick that uses the same identifier. Second, in an OpenDocument format, we can enter that information only once for each subject and every time that subject appears, it has the same metadata. The subject and verb of an RDF statement are always written using an IRI (Internationalized Resource Identifier) [RFC3987]. The object can also be written using an IRI, but often in an OpenDocument document the object will be some text in the document. This enables the user to make statements about the content in an OpenDocument document. All of the RDF statements in the following examples use the simple model set forth above. (There are more complex mechanisms in RDF but they all follow that simple model.)5 The new metadata mechanisms bring the full power of RDF to OpenDocument documents. The only limitation is the users' skill in determining what metadata they want to use to enhance their documents.

3 RDF specifications, see http://www.w3.org/RDF 4 N3 notation tutorial, see http://www.w3.org/2000/10/swap/Primer.html 5 The examples are given in both RDF/XML and equivalent N3 syntax.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 5 of 19 October 22, 2009

3 Storing Extensible Metadata


To introduce the mechanisms developed to store extensible metadata in OpenDocument files, the following facts are presumed: A medical document has been prepared concerning a fictitious patient and his treating physician. In the introductory example, the name of the treating physician occurs in the footer of the document (visible to the user), and additional metadata about the physician is stored in the document (invisible to the user). The editing of the metadata that is invisible to the user is application specific. The storage of RDF metadata in an OpenDocument package uses three types of files:

Content Files, see 3.1 RDF/XML Metadata, see 3.2 Metadata Manifest, see 3.3

3.1 Content Files


The content files are the files that contain the content to which metadata refers. In the case of OpenDocument, the content file is either the content.xml file, or the styles.xml file (in case of referring to the content of a footer or header, being part of a page style). The content file contains what the user sees as the content of a document that they are viewing or editing. The content file is controlled by the OpenDocument application. The following fragment of a styles.xml file shows a footer, where a <text:p> element surrounds the treating physician's name (Dr. J. Franklin). This paragraph has an identifier called xml:id. The xml:id enables the linking of metadata to a particular portion of text.
<style:master-page style:name="Standard" style:page-layout-name="pm1"> <style:footer> <text:p text:style-name="fs">Hospital Encounter Note</text:p> <text:p text:style-name="fs" xml:id="ID_A">Dr.J.Franklin</text:p> </style:footer> </style:master-page>

3.2 RDF/XML Metadata Files


RDF/XML metadata files record additional information describing or augmenting content; in this case, for the treating physician Dr. J. Franklin, stating his medical specialty.6 Metadata files are stored as part of the OpenDocument package.7 6 It should be noted that recording the information in metadata allows this information to be reused without re-entering the information the next time Dr. J. Franklin is encountered in the text. 7 There are more advanced ways to store metadata for OpenDocument files. See the Advanced Examples document at the Metadata SC website for details.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 6 of 19 October 22, 2009

Here is a fragment of an RDF/XML file (e.g. /meta/hospital/doctor.rdf) for Dr. James Franklin:
<odf:Element rdf:about="../../content.xml#ID_A"> <med:doctorOnDuty> <med:Doctor rdf:about="http://hospital-DB/doctors/ID116"> <med:fieldName xml:lang="en">Neurologist</med:fieldName> </med:Doctor> </med:doctorOnDuty> </odf:Element>

3.3 The Metadata Manifest


The metadata manifest file enumerates the files in the OpenDocument document that may contain metadata; this includes the content.xml and styles.xml, which may contain inline RDFa annotations, and any number of user-defined RDF/XML files. The metadata manifest is itself a metadata file and stored as RDF/XML. For every user-defined metadata file, the storage location is given by a URI relative to the metadata manifest itself. Furthermore, annotations that specify what is contained in the userdefined metadata file should be given, so that a metadata consuming application can identify which metadata files in the document contain metadata the application is interested in. It is recommended that application-specific metadata annotations for individual content elements not be inserted directly in the metadata manifest, but into a user-defined metadata file. In this way, different applications may add different annotations to the same content element without creating conflicts.8 Here an example of a basic metadata manifest file (/manifest.rdf):
<?xml version="1.0"?> <rdf:RDF xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:odf="http://docs.oasis-open.org/ns/office/1.2/meta/odf#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <pkg:Document rdf:about=""> <pkg:hasPart> <odf:ContentFile rdf:about="content.xml"> </odf:ContentFile> </pkg:hasPart> <pkg:hasPart> <pkg:MetadataFile rdf:about="meta/hospital/doctor.rdf"> <rdf:type rdf:resource="http://medical-employee/data"/> <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#"/> </pkg:MetadataFile> </pkg:hasPart> </pkg:Document> </rdf:RDF>

8 Different applications may even create annotations that contradict each other. As long as the applications do not look at each other's annotations, this will work.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 7 of 19 October 22, 2009

4 Describing Document Content


The metadata mechanisms of OpenDocument (1.2) can be conveniently described in XML terms as operating on three different categories of content as follows:

Metadata can be used to describe the complete document Metadata can be used to describe a single OpenDocument element (e.g. a table) Metadata can be used to describe a set of OpenDocument elements (e.g. a part of the viewed content)

4.1 Metadata describing the OpenDocument Document


In order to attach metadata to the OpenDocument document as a whole, the document has to be identified by an IRI. That IRI identifying the document itself is in general the URL of the OpenDocument package concatenated with the relative path of the document within the package.. For example, an embedded document stored in the directory someobject of an ODF package at http://example.org/foo.odt will have the IRI http://example.org/foo.odt/someobject/9. The metadata files contained in the ODF package will of course refer to the contents of the package by relative IRIs.

Metadata Manifest Example


In a metadata manifest a resource with the type <pkg:Document> represents the document.
<?xml version="1.0"?> <rdf:RDF xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <pkg:Document rdf:about=""> <!-- further information about the document --> </pkg:Document> </rdf:RDF>

Alternative RDF view in N3:


@prefix pkg: <http://docs.oasis-open.org/ns/office/1.2/meta/pkg#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . <> a pkg:Document .

RDF/XML Metadata Example


Metadata describing the document is added to a RDF/XML file in form of RDF statements referring to the IRI identifying the document. For example, an RDF statement can be added to say that the document is an encounter note (i.e. http://hospital/documents/encouter-note). 9 Note that this is not a URI which can be dereferenced. This is most unfortunate, but there is currently no standard URI scheme for ZIP-based packages.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 8 of 19 October 22, 2009

<?xml version="1.0"?> <rdf:RDF xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <pkg:Document rdf:about=""> <rdf:type rdf:resource="http://hospital/documents/encouter-note"/> </pkg:Document> </rdf:RDF>

Alternative RDF view in N3:


@prefix pkg: <http://docs.oasis-open.org/ns/office/1.2/meta/pkg#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . <> <> a pkg:Document . a <http://hospital/documents/encouter-note> .

4.2 Metadata describing an OpenDocument Element


Metadata has traditionally been applied at the entire document level. But, to have the granularity necessary to meet many of the use cases, metadata must be applied at the level of individual OpenDocument elements. For example, attaching metadata to any given OpenDocument paragraph element.10 For purposes of illustration, the initial example is extended to include a fictitious patient John Smith. Now the document contains both personal data about the patient and medical notes from his treating physician. Assume that a text section includes the results of a physical examination of a patient. The visible content might appear as:
PHYSICAL EXAMINATION VITALS: Temperature: 36.2, Pulse: 1.05Hz, Respiration: 0.2Hz

Content Example
The content.xml for the above document view consists of a text section, a heading and two paragraphs. The surrounding section is identified by an xml:id attribute:
<text:section xml:id="Sect1" text:style-name="Sect1" text:name="PhysicalExamData"> <text:h text:style-name="Heading_20_3" text:outline-level="3">PHYSICAL EXAMINATION</text:h> <text:p text:style-name="Standard"> VITALS: Temperature: 36.2, Pulse: 1.05Hz, Respiration: 0.2Hz </text:p> </text:section>

To attach metadata to this section, the xml:id value Sect1 will be referenced directly from the RDF/XML files using a relative in package URL, such as content.xml#Sect1.

10 Although the metadata is attached to the OpenDocument element, the metadata is usually about the content of the element.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 9 of 19 October 22, 2009

Relative URLs are made absolute by using the URL of the document as base URI on loading. As a consequence, changing the location of the document (e.g., by moving it to some other place in the file system) will lead to different absolute URIs being generated for the contained content elements. This has the advantage that it is possible to tell apart the metadata for different versions of the same document. Because references within the document are stored as relative URIs, they are unaffected by changes in the storage location. But references from outside the document may break. If it is necessary to reference a content element independent of the document location, the RDF predicate owl:sameAs may be used to create a stable URI alias. But please note that creating URI aliases also has drawbacks (see [WEBARCH]).

RDF/XML Metadata Example


The IRI identifying the element is used in the user defined RDF/XML metadata files to add RDF statements about the text section. In this example the metadata consists of medical details about the physical examination of the patient. For example the metadata RDF/XML file medical/physicalExam.rdf might contain the following:
<rdf:Description rdf:about="http://ex-hospital-DB/patients/ID98765"> <rdf:type rdf:resource="http://ex-hospital#patient"/> <ex:hasID rdf:resource="ID98765"/> <ex:hasVitals> <med:vitalData rdf:about="../content.xml#Sect1"> <rdf:type rdf:resource="http://docs.oasisopen.org/ns/office/1.2/meta/odf#Element"/> </med:vitalData> </ex:hasVitals> </rdf:Description>

Just as with <text:section> elements, metadata can be added to any of the more than forty OpenDocument elements that have an xml:id attribute.

4.3 Metadata describing a Part of the Document


When content that spans more than one OpenDocument element requires metadata there are two possible techniques available: 1. Identifying the selected part by the contained OpenDocument elements, each identified via xml:id 2. Inserting a <text:bookmark-start> and <text:bookmark-end> element to embrace the content of various OpenDocument elements (in case of a sequential part of content)

Content Example (xml:id)


To attach metadata to a set of OpenDocument elements the binding mechanism earlier introduced for one element is applied on each element of the set. Every element of this set will have a different xml:id. The set of IRIs representing ODF elements may be bundled in RDF Containers and RDF Collections in the metadata RDF/XML files.

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 10 of 19

October 22, 2009

<text:h text:outline-level="3">Notes from Monday</text:h> <text:p> The patient John Smith came in the morning and <text:meta xml:id="c1"> complained about pain in neck and left foot. </text:meta> </text:p> <text:p xml:id="c2"> In the afternoon he reported additional pain in head and stomach. </text:p>

Metadata Manifest Example (xml:id)


<?xml version="1.0"?> <rdf:RDF xmlns:odf="http://docs.oasis-open.org/ns/office/1.2/meta/odf#" xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <pkg:Document rdf:about=""> <pkg:hasPart> <odf:ContentFile rdf:about="content.xml"> </odf:ContentFile> </pkg:hasPart> <pkg:hasPart> <pkg:MetadataFile rdf:about="meta/hospital/doctor.rdf"> <rdf:type rdf:resource="http://medical-employee/data"/> <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#"/> </pkg:MetadataFile> </pkg:hasPart> </pkg:Document> </rdf:RDF>

Note: Using xml:id and bundling in RDF/XML is the only approach to describe a set of nonsequential elements. To be clarifed: Why has Dublin Core deprecated RDF Containers? http://dublincore.org/documents/2006/05/29/dc-rdf-notes/

Content Example (Bookmarks)


In order to attach metadata to sequential content, such as a text selection by the user of various paragraphs, OpenDocument bookmark elements may be used. The XML content would be embraced by two standalone elements <text:bookmark-start> and <text:bookmark-end> marking the region.11 The <text:bookmark-start> starts within the first paragraph and the <text:bookmarkend> ends within the last paragraph, therefore not the paragraph elements are included, but the content is included.
<text:h>Notes from Monday</text:h> <text:p> The patient John Smith came in the morning and

11 Bookmark elements are paragraph content. Therefore even when a user selects all paragraphs from a document, their content is the subject of the metadata.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 11 of 19 October 22, 2009

<text:bookmark-start text:name="Mark 1" xml:id="c1"/> complained about pain in neck and left foot. </text:p> <text:p> In the afternoon he reported additional pain in head and stomach. <text:bookmark-end text:name="Mark 1"/> </text:p>

Bookmarks are milestone XML elements. They occur only within paragraph elements but exist outside the XML hierarchy. This enables them to mark content that exists outside of a paragraph, such as a table between two paragraphs.

Metadata Manifest Example (Bookmarks)


<pkg:Document rdf:about="" xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:odf="http://docs.oasis-open.org/ns/office/1.2/meta/odf#"> <pkg:hasPart> <odf:ContentFile rdf:about="content.xml"> </odf:ContentFile> </pkg:hasPart> <pkg:hasPart> <pkg:MetadataFile rdf:about="medical/physicalExam.rdf"> </pkg:MetadataFile> </pkg:hasPart> </pkg:Document>

RDF/XML Metadata Example (Bookmarks)


For example the metadata RDF/XML file medical/physicalExam.rdf might contain the following:
<med:patient rdf:about="http://ex-hospital-DB/patients/ID98765"> <ex:hasID rdf:resource="ID98765"/> <ex:hasSymptoms rdf:resource="../content.xml#c1"/> </med:patient>

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 12 of 19

October 22, 2009

5 Metadata Scenarios
There are three different kinds of scenarios between metadata and the parts of the viewed content of the OpenDocument file: 1. Content is being described by Metadata 2. Content is being created based on Metadata 3. Content is tagged as Metadata Each of them is used for different scenarios and identified in the content of the OpenDocument format by a different binding technique.

5.1 Content described by Metadata


Classic metadata is attached to particular content of a document. In this scenario the document editor associates part of the document with metadata. In general this is done by hiding the RDF statements from the user, who is only interfacing with a metadata aware component which performs the binding of the metadata to the content target. This binding is expressed in the OpenDocument format by using the xml:id attribute on one of the xml:id capable OpenDocument elements to identify the element containing the content to be described.12

Content Example
<text:section xml:id="Sect1" text:style-name="Sect1" text:name="PhysicalExamData"> <text:h text:style-name="Heading_20_3" text:outline-level="3">PHYSICAL EXAMINATION</text:h> <text:p text:style-name="Standard"> <text:meta xml:id="p2"> VITALS: <text:meta xml:id="p3">Temperature: 36.2 </text:meta>, <text:meta xml:id="p4">Pulse: 1.05Hz</text:meta> <text:meta xml:id="p5">Respiration: 0.2Hz </text:meta> </text:meta> </text:p> </text:section>

Content created from Metadata


This scenario involves the usage of a metadata aware application (i.e. a plug-in for an OpenDocument application) to insert a field within any paragraph. The content of the field is generated by the metadata application based on metadata. In our scenario Dr. J. Franklin takes advantage of a citation plug-in based on metadata, that uses his own GUI to let him choose to quote from a list of medical article and the citation is saved in the medical document. 12When the subpart of a paragraph should be described, there are two OpenDocument elements available. The <text:meta> element should be preferred in this case as the <text:metafield> has a different function.
09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 13 of 19 October 22, 2009

Content Example
The citation field in the OpenDocument format is saved as a <text:meta-field> element, which is always part of a paragraph. The <text:meta-field> is not a simple text field, as it is not restricted to text, but may contain arbitrary paragraph content. The anchor to the metadata is established by the xml:id attribute.
<text:p text:style-name="Standard"> It can be assumed the patient was infected from pigs. <text:meta-field xml:id="citation-1"> (<text:meta-field xml:id="citation-1-r1"> Doe, 1999 </text:meta-field>; <text:meta-field xml:id="citation-1-r2"> Smith, 2000 </text:meta-field>) </text:meta-field> </text:p>

Metadata Manifest Example


<?xml version="1.0"?> <rdf:RDF xmlns:pkg="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#" xmlns:odf="http://docs.oasis-open.org/ns/office/1.2/meta/odf#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <pkg:Document rdf:about=""> <pkg:hasPart> <odf:ContentFile rdf:about="content.xml"/> </pkg:hasPart> <pkg:hasPart> <pkg:MetadataFile rdf:about="citation.rdf"> </pkg:MetadataFile> </pkg:hasPart> <pkg:hasPart> <pkg:MetadataFile rdf:about="bibliography.rdf"/> </pkg:hasPart> </pkg:Document> </rdf:RDF>

RDF/XML Metadata Example


Citation.rdf
<?xml version="1.0"?> <rdf:RDF xmlns:cite="http://docs.oasisopen.org/prototype/opendocument/citation#" xmlns:dcterms="http://dublincore.org/documents/dcmi-terms/#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <cite:Reference rdf:about="content.xml#citation-1-r1"> <!-- to specify the ID/URI for the source --> <dcterms:source rdf:resource="info:pmid/17445913"/> <!-- to track position within the list of references --> <cite:position>1</cite:position> </cite:Reference>

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 14 of 19

October 22, 2009

<cite:Reference rdf:about="content.xml#citation-1-r2"> <dcterms:source rdf:resource="urn:isbn:12902189"/> <cite:position>2</cite:position> <cite:pages>23</cite:pages> </cite:Reference> </rdf:RDF>

Bibliography.rdf13
<?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:bibtex="http://purl.oclc.org/NET/nknouf/ns/bibtex#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/" xmlns:foaf="http://xmlns.com/foaf/0.1/" > <bibtex:Article rdf:about="info:pmid/17445913"> <dc:title>Neuraminidase inhibitor susceptibility of porcine H3N2 influenza A viruses isolated in Germany between 1982 and 1999.</dc:title> <dcterms:abstract>As an intermediate host of avian and human influenza A viruses (FLUAV) pigs may play a potential role in interspecies virus transmission and reassortment of viral genes including those conferring antiviral drug resistance. Porcine FLUAV isolated in Germany between 1989 and 2001 contains mutations in the M2 gene inducing amantadine resistance. No data exist on neuraminidase inhibitor (NAI) susceptibility of these porcine FLUAV. We studied the antiviral activity of NAI against seven selected H3N2 FLUAV isolated from pigs in Germany between 1982 and 1999. All isolates were susceptible towards oseltamivir and zanamivir in neuraminidase enzymeinhibition assays. Both compounds inhibited virus spreading and reduced the virus yields and plaque size at low concentrations. Higher concentrations were necessary to reduce the plaque number. Two isolates that differed in glycosylation pattern of viral hemagglutinin (HA) showed markedly reduced drug susceptibility in cell culture-based assays.</dcterms:abstract> <dc:creator>K Bauer</dc:creator> <dc:creator>C Schrader</dc:creator> <dc:creator>J Suess</dc:creator> <dc:creator>P Wutzler</dc:creator> <dc:creator>M Schmidtke</dc:creator> <foaf:maker> <foaf:Person rdf:about="http://purl.org/net/hubmed/ns/pmids/17445913/authors/Bauer,K" > <foaf:name>K Bauer</foaf:name> <rdf:value>K Bauer</rdf:value> <foaf:givenname></foaf:givenname> <foaf:surname>Bauer</foaf:surname> </foaf:Person> </foaf:maker> <foaf:maker> <foaf:Person rdf:about="http://purl.org/net/hubmed/ns/pmids/17445913/authors/Schrader ,C">

13 Taken from http://www.hubmed.org/


09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 15 of 19 October 22, 2009

<foaf:name>C Schrader</foaf:name> <rdf:value>C Schrader</rdf:value> <foaf:givenname></foaf:givenname> <foaf:surname>Schrader</foaf:surname> </foaf:Person> </foaf:maker> <foaf:maker> <foaf:Person rdf:about="http://purl.org/net/hubmed/ns/pmids/17445913/authors/Suess,J" > <foaf:name>J Suess</foaf:name> <rdf:value>J Suess</rdf:value> <foaf:givenname></foaf:givenname> <foaf:surname>Suess</foaf:surname> </foaf:Person> </foaf:maker> <foaf:maker> <foaf:Person rdf:about="http://purl.org/net/hubmed/ns/pmids/17445913/authors/Wutzler, P"> <foaf:name>P Wutzler</foaf:name> <rdf:value>P Wutzler</rdf:value> <foaf:givenname></foaf:givenname> <foaf:surname>Wutzler</foaf:surname> </foaf:Person> </foaf:maker> <foaf:maker> <foaf:Person rdf:about="http://purl.org/net/hubmed/ns/pmids/17445913/authors/Schmidtk e,M"> <foaf:name>M Schmidtke</foaf:name> <rdf:value>M Schmidtke</rdf:value> <foaf:givenname></foaf:givenname> <foaf:surname>Schmidtke</foaf:surname> </foaf:Person> </foaf:maker> <dc:identifier>10.1016/j.antiviral.2007.03.007</dc:identifier> <prism:publicationName>Antiviral Res</prism:publicationName> <prism:publicationDate>2007-09</prism:publicationDate> <prism:volume>75</prism:volume> <prism:number>3</prism:number> <prism:startingPage>219</prism:startingPage> <prism:endingPage>226</prism:endingPage> <prism:isPartOf rdf:resource="urn:issn:0166-3542"/> </bibtex:Article> </rdf:RDF>

5.2 Content equivalent to Metadata


Whenever a text portion of the document is also used as metadata at the same time (RDF literal), the text portion should not exist both in the metadata and content files. Duplicating data risks inconsistency between the RDF/XML file (readable for RDF applications) and the OpenDocument content (readable for humans). As the text portion should be viewable by ODF applications that are not able to process metadata, the literal should solely exist in the content. There are five OpenDocument elements that support in content metadata.

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 16 of 19

October 22, 2009

Content Example
<text:p text:style-name="Standard"> The patient name is: <text:meta xhtml:about="http://ex-hospital-DB/patients/ID98765" xmlns:vcard="http://www.w3.org/2006/vcard/ns#" xhtml:property="vcard:fn"> John Smith </text:meta> </text:p>

RDF/XML Metadata Example


<med:patient rdf:about="http://ex-hospital-DB/patients/ID98765"> <ex:hasID rdf:resource="ID98765"/> <ex:hasVitals> <med:vitalData rdf:about="http://hospital-DB/medical-notecc1593"/> </ex:hasVitals> </med:patient>

Note: It is not part of this specification how metadata information will be added to the document. For instance, what kind of metadata tools are being used together with the ODF application to enable an efficient handling in the daily routine of a hospital.

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 17 of 19

October 22, 2009

6 Metadata Proposal's FAQ


1. section 1.1 says: Applications that read and write documents should preserve all metadata files. Why is it not a must? Because when the document is being edited by an OpenDocument application that is not capable of using metadata, the application should get the chance to drop the metadata to prevent inconsistencies between the metadata and the viewed content. 2. Why do we need Named Graphs? Named graphs are a mechanism used to refer to a particular RDF graph in a set of graphs using its name, that is an IRI. In an OpenDocument package. a named graph is always represented as an RDF/XML File There may be an arbitrary number of named graphs in a single document, which allows for separating the metadata for different consumers, even if those consumers want to annotate the same ODF document content element. 3. Why are in-content metadata attributes (i.e. xhtml:about, xhtml:property, xhtml:content and xhtml:datatype) not allowed on <text:meta-field>? The content of <text:meta-field> is meant to be created from metadata. Describing it again by metadata seems redundant.

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 18 of 19

October 22, 2009

AppendixA.References
[RFC3987] M. Duerst, M. Suignard, Internationalized Resource Identifiers (IRIs), http://www.ietf.org/rfc/rfc3987.txt, , 2005. WEBARCH: Ian Jacobs, Norman Walsh, Architecture of the World Wide Web, Volume One, 2004

09-10-22-ODF-MetaData-Examples.odt Copyright OASIS Open 2002 - 2009. All Rights Reserved.Page 19 of 19

October 22, 2009

Вам также может понравиться