KR20070120965A - Determining fields for presentable files and extensible markup language schemas for bibliographies and citations - Google Patents

Abstract

Fields for presentable files can be determined by an application (i) based on a field type and at least one parameter of the fields and (ii) responsive to raw data and a separate transformation engine, even when the application is unaware of the mechanics of the separate transformation engine. In a described implementation for a given field, the field type indicates that the given field is to be evaluated based on raw data that is referenced by the at least one parameter of the given field. The transformation engine is applied to the referenced raw data to produce a result for the given field that is suitable for presentation. Schemas for bibliographies and citations facilitate utilization of bibliographic information. A schema for bibliographic information defines a framework for bibliographic information. The bibliographic information may be embedded in a document, embodied as a master list, and so forth.

Description

DETERMINING FIELDS FOR PRESENTABLE FILES AND EXTENSIBLE MARKUP LANGUAGE SCHEMAS FOR BIBLIOGRAPHIES AND CITATIONS}

<Copyright Notice>

Portions of this patent document contain copyrighted material. The copyright owner does not object to anyone's facsimile reproduction of this patent document or patent specification as indicated in the Patent and Trademark Office patent file or record, but otherwise all copyrights are reserved.

Field of invention

The present invention relates to the determination of extensible markup language schema for fields in displayable files and references and citations.

For example, a word processing document can include embedded fields. The field represents a portion of the document that is visually represented by the display data based on the field type and the at least one field parameter. Thus, the display data can be changed in response to the change in the value (s) of the at least one field parameter. There may be different types of fields for different purposes. Examples include the number of pages of the document, the file name of the document, the current date and time, numbers for numbering features (e.g., paragraphs, borders, pages, etc.), and the like.

When the display of the word processing document is updated, the display data is also updated based on at least one parameter. For example, if there is a field for the number of pages of the document, each time the document is updated for printing, the current page number of the document is inserted as display data at the position of the embedded field.

In existing fields, at least one field parameter is essentially associated with known or determinable information. For example, dates and / or times are essentially known by the computing system. In addition, the file name and internal numbering operations are essentially determinable from the document itself. As a result, existing embedded field technology is relatively limited and inflexible.

The ability to work efficiently on bibliographic information in the context of text-based applications such as word processors is becoming increasingly important, especially with respect to embedded fields. This is especially true when the number of sources cited in a given document increases and the number of different available source types increases. Examples of text-based applications that can be used to generate documents with quotes include word processors, hypertext markup language (html) editors, and the like.

Summary of the Invention

The fields for the displayable file are based on (i) the field type and at least one parameter of each of the fields, and (ii) the raw data, and in response to a conversion engine that is separable and external to the application. This can be determined by the application even when the application does not know the internal mechanics of the conversion engine. In the described implementation for a given field, the field type indicates that the given field is evaluated based on the raw data referenced by at least one parameter of the given field. The transformation engine is applied to the referenced raw data to produce a result for a given field suitable for presentation. In an example implementation, the transformation engine includes a plurality of presentation rule sets that can be optionally set up to apply to the field. In one embodiment, each subset of display rules targets each raw data type. In an example implementation, the field includes bibliography and citations for bibliographic sources, the raw data includes bibliographic data for cited sources, and different sets of presentation rules include different bibliographic formatting standards. Each raw data type includes a respective source type.

Extensible markup language schemas for references and citations facilitate the use of bibliographic information. For example, the schema usage module may enable the creation, modification, interpretation, etc. of schemas for bibliographic information. The schema usage module may be a standalone program, part of an application program, or the like. The schema for bibliographic information defines a framework for bibliographic information. Bibliographic information can be embedded in a document, implemented as a master list, and the like. In the described implementation, the schema for bibliographic information is implemented using open standards such as Extensible Markup Language (XML). The schema lists a number of source types and their associated data types. In another described implementation, using the schema utilization module in connection with the schema for bibliographic information allows bibliographic source information to be generated, inserted into the document as a citation, added to the master list, reused later, and the like.

This summary is provided to briefly introduce a selection of concepts that are further described in the detailed description below. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. Moreover, implementations of other methods, systems, approaches, apparatus, devices, media, procedures, schemas, application program interfaces (APIs), arrays, and the like are also described herein.

Like numbers are used to refer to the same and / or corresponding aspects, features and components throughout the drawings.

1 is an exemplary block diagram of a displayed file containing display data resulting from a field.

2 is an exemplary block diagram of an application capable of displaying displayable files and displayable files using raw data and a transformation engine.

3 is a flow diagram illustrating an example of a method for displaying a displayable file having embedded fields.

4 is a block diagram of an exemplary interpretation of a built-in field.

5 is a block diagram of exemplary extraction of raw data for embedded fields.

6 is a block diagram of an exemplary transformation of extracted raw data.

7 is a block diagram of an example conversion engine.

FIG. 8 is a block diagram that provides examples of surge related to the more general concepts and terms shown in FIGS. 1-7.

FIG. 9 is a computing application that may implement (in whole or in part) at least one aspect of determining a field for a displayable file and / or an extensible markup language schema for references and citations as described herein. Or a general purpose device) operating environment.

FIG. 10 is a diagram that illustrates an exemplary schema for defining a framework for bibliographic information and / or enabling the use of bibliographic information.

Introduction

For example, a word processing document can include embedded fields. The field represents a portion of the document that is visually represented by the display data based on the field type and the at least one field parameter. Thus, the display data can be changed in response to the change in the value (s) of the at least one field parameter. There may be different types of fields for different purposes. Examples include the number of pages of the document, the file name of the document, the current date and time, numbers for numbering features (e.g., paragraphs, borders, pages, etc.), and the like.

When the display of the word processing document is updated, the display data is also updated based on at least one parameter. For example, if there is a field for the number of pages of the document, each time the document is updated for printing, the current page number of the document is inserted as display data at the position of the embedded field.

In existing fields, at least one field parameter is essentially associated with known or determinable information. For example, dates and / or times are essentially known by the computing system. In addition, the file name and internal numbering operations are essentially determinable from the document itself. As a result, existing embedded field technology is relatively limited and inflexible.

Therefore, as described above, the conventional embedded field description is limited to the field parameter that can be determined based on predetermined unique information. On the other hand, the schemas, mechanisms, techniques, etc. described below relate to determining fields for displayable files in a flexible and / or extensible manner.

In the example implementation described, the field may be a transform reference field type. The transform reference field type indicates that the referenced raw data is to be transformed, and the transformed raw data is then displayed as the display data result of the field. A set of display rules can be selected from the transformation engine so that the referenced raw data is displayed in the desired manner.

The transformation engine is independent of the application displaying the field, and the application is unaware of the nature of the transformation engine's internal mechanics (eg, display rules). Moreover, the user understands the details of how the application applies the transformation engine, without relying on the application, or even relying on the application as long as the generated transformation engine generally supports or conforms to the published schema for the transformation engine. You can create or modify the transformation engine independently without having to do so. For example, users can create, edit, etc. raw data and transformation engines using non-proprietary open standards such as XML and XSLT, respectively, without having to associate applications.

Fields of the transform reference field type may be used in various situations. In one example situation, the bibliographic feature uses the schema, mechanism, description, etc. of the transform reference field type. The raw data includes one or more surge sources and the transformation engine includes at least one set of presentation rules. Each marking rule can implement a written approach to cite bibliographic sources. In addition, references and citations can be quickly retargeted by changing the selected presentation rule set. This may cause the indication of each cited surge source to change accordingly.

In certain implementations described below, bibliographic information may be entered once, edited at will, and retrieved for reuse in different documents, for example using open standard techniques. Moreover, generating bibliographic information in accordance with a schema may enable the use of bibliographic information in different environments. In certain implementations, extensible markup language schemas for references and citations are described herein.

Extensible Markup Language (XML) is a universal language that provides a way to identify, exchange, and process various kinds of data. For example, XML can be used to generate documents that can be used by many different application programs. Elements of an XML file generally have an associated namespace and schema.

The namespace is a unique identifier for a set of names used in XML documents to define element / attribute names and types. The name of the namespace is generally used to uniquely identify each class of XML document. XML Schema (schema) provides a way to describe and validate data in an XML context. The schema may indicate, for example, what elements and attributes are used to describe content in an XML document, where each element is allowed, what type of content is allowed in it, and / or which elements appear within any other element. Indicate if it can. The use of a schema can ensure that documents are structured in a consistent and predictable manner, which facilitates standard document organization and enables subsequent interpretation of individual documents.

This description is divided into seven additional sections. The third, fifth, sixth and seventh sections are particularly suitable for this partial continuation patent application. The first section relates to FIGS. 1-3, entitled "General Implementation of Field Determination". The second section relates to FIGS. 4-7 and is entitled "Specific Implementation of Field Determination." The third section relates to FIG. 8 and is entitled "Surge Related Implementation of Field Determination". The fourth section is entitled "Conclusion on Field Decision". The fifth section refers to FIG. 9 and is entitled "Exemplary Operating Environment for a Computer or Other Device." The sixth section relates to FIG. 10 and is entitled "Extended Markup Language Schema for References and Citations." The description of the seventh section entitled "Extended Markup Language Based Techniques of Source Types for References and Citations" is associated with the description of the sixth section.

General implementation of field determination

1 is an exemplary block diagram of a display file 102 with display data 106 resulting from field 108. In the implementation described, the presentation file 102 includes a data stream representation 104 that includes the presentation data 106. The display file 102 can come from any type of displayable file. Examples of displayable file types include word processing files, spreadsheet files, slideshow files, email files, browser files, multimedia files, certain combinations thereof, and the like. Thus, data stream representation 104 and presentation data 106 may include any number of symbols of any kind.

Data stream configuration 110 for field 108 is shown. Data stream configuration 110 may be represented as {(field type) (field parameter (s)) | [result]}. "Field type" indicates one of the many possible field types to which a given field 108 belongs. "Field parameter (s)" represents at least one field parameter that functions as an independent variable for the field type. “Result” refers to the result of a function characterized by a pair of field type and field parameter (s).

By way of example only, the field type is a paragraph reference number and the field parameter may be a pointer to a numbered reference paragraph. Thus, the result is the current paragraph number of the reference paragraph. For a given field type, the field parameter may be blank or omitted when the field type alone provides enough information to determine the result.

The logical configuration 112 for the field 108 is shown in a block diagram. Field 108 includes function information 114 and result 120. The function information 114 includes a field type 116 and one or more pairs of parameters 118. When the function characterized by the field type 116 and the parameter 118 is evaluated or determined, a result 120 is generated. When display file 102 is updated, result 120 is displayed as display data 106 that is part of data stream display 104.

2 is an exemplary block diagram of an displayable file 202 and an application 208 that can display the displayable file 202 using the raw data 204 and the transformation engine 206. In the implementation described, the application 208 generally results in the field 108 based on the field type 116 and the at least one parameter 118 and in response to the raw data 204 and the transformation engine 206. Determine 120.

The displayable file 202 is the source or basic information for the display file 102 (FIG. 1). That is, the information in displayable file 202 enables an application to generate data stream representation 104 (FIG. 1) when displayable file 202 is being displayed. The displayable file 202 may be displayed on a visual screen, printed, or the like.

As shown, displayable file 202 includes data stream information 210 and additional information 212. The data stream representation 104 is mainly generated from the data stream information 210. If present, additional information 212 includes additional information that can be used to manipulate, display, or use data stream information 210 and / or the entire displayable file 202. For example, the additional information 212 may include attribute information about the displayable file 202, a change history, and the like. Moreover, the additional information 212 includes all or part of the raw data 204 and / or the conversion engine 206 to improve portability of the displayable file 202 as described below in detail with reference to FIG. 8. can do.

The raw data 204 and the transformation engine 206 are also shown in FIG. 2. Raw data 204 includes data that is at least partially represented as display data 106 (FIG. 1) for field 108. The transformation engine 206 includes display rules (not explicitly shown in FIG. 2) that transform the raw data 204 into the result 120. In one embodiment, the translation engine 206 follows an open standard, so that individual users modify or augment the translation engine provided by another user, or the application 208 (which is word processing such as Microsoft Word from Microsoft). May be chosen to create a new transformation engine without using any general purpose application type that includes the program). Examples of raw data 204 are described below with reference to FIGS. 5 and 6 in detail, and examples of conversion engine 206 are described below with reference to FIGS. 6 and 7 in detail. In addition, the transformation is described below with reference to FIGS. 6 and 7 in detail.

In the implementation described, the application 208 includes a field interpreter 214, a raw data extractor 216, and a raw data converter 218. The field interpreter 214 can interpret the field 108, in particular the function information 114. The raw data extractor 216 may extract the raw data from the raw data 204 according to the parameter 118 including a reference to the raw data 204. The raw data converter 218 may convert the extracted raw data according to one or more display rules of the conversion engine 206 without directly controlling the conversion.

The raw data converter 218 can apply the conversion engine 206 to the extracted data of the raw data 204 without knowing the internal mechanics of the conversion engine 206 (including the characteristics of any included display rules). . Thus, the result 120 of field 108 may be independent of application 208. Schema 220 is known to application 208, which is adapted to work with transformation engines 206 that support or follow schema 220. Schema 220 specifies one or more formats for transformation engine 206. As a result, as long as the transformation engine 206 supports or follows the schema 220, the raw data converter 218 can apply the transformation engine 206 to the raw data 204 without knowing the internal mechanics of the transformation engine. . It should be understood that the application 208 may interpret other (eg, conventional) fields 108 independently without relying on the raw data 204 or the transformation engine 206.

As shown in the example block diagram of FIG. 2, the raw data 204 and the transformation engine 206 are separate from the displayable file 202 and the application 208. For example, raw data 204 can be a separate file, such as a separate master raw data file. Also, the translation engine 206 may be a standalone file, an individual program, a plug-in module, an operating system (OS) feature, or the like. However, as noted above, all or some of the raw data 204 and / or the transformation engine 206 may alternatively be included as part of the additional information 212.

Indeed, in the described implementation, at least some of the raw data 204 are stored as part of the additional information 212, and at least some of the transformation engine 206 converts the referenced raw data 204 to result 120. It may be used by the application 208 when generating the. In this implementation, at least the relevant (eg, referenced) raw data of the raw data 204 is convertible as part of the displayable file 202. As a result, with the relevant raw data included as part of the displayable file 202, the displayable file 202 can be emailed to the recipient, for example. Similarly, if the recipient has an application 208 that is expected to access and display the displayable file 202 properly, including at least a portion of the transformation engine 206 as part of the additional information 212 is displayable. It ensures that the file 202 can be displayed in the way intended by its creator.

3 is a flow diagram 300 illustrating an example of a method for displaying a displayable file having embedded fields. Flowchart 300 includes five "main" blocks 302-310 and six "minor" blocks. Although the operations of the flowchart 300 may be performed in other environments and using various hardware and software combinations, FIGS. 1 and 2 are specifically used to illustrate certain aspects and examples of the present invention. By way of example only, the operations of flowchart 300 may be performed by an application on displayable file 202 using raw data 204 and transformation engine 206.

In block 302, data stream information of the displayable file is processed until it encounters an embedded file. For example, data stream information 210 of displayable file 202 may be treated as data stream representation 104 of display file 102 until it encounters field 108.

At block 304, the field is interpreted. For example, the field interpreter 214 of the application 208 can interpret the field 108. Specifically, in block 304 (1), the field type is identified. For example, the field interpreter 214 can identify the field type 116 of the function information 114. At block 304 (2), one or more parameters are obtained. For example, the field interpreter 214 can obtain the parameter (s) 118 of the function information 114.

In the described implementation, the field type 116 includes a transform reference field type 116. This instructs field interpreter 214 that the reference indicates the raw data to be converted before display. Thus, at least one parameter 118 includes a reference to the raw data 204. The other parameter 118 can identify all or part of the transformation engine 206. Alternatively, the conversion engine 206 to be used for the displayable file 202 may be identified (and optionally included) in the additional information 212. As another example, transformation engine 206 may be identified by global settings set by or through an application.

At block 306, raw data for the field is extracted. For example, raw data extractor 216 of application 208 may extract raw data for field 108 from raw data 205. Specifically, in block 306 (1), raw data is found in response to the acquired parameter (s). For example, raw data extractor 216 may find raw data 204 and / or portions thereof in response to at least one parameter 118 that includes a reference to the raw data. In block 306 (2), the found raw data is retrieved. For example, raw data extractor 216 may retrieve raw data found from raw data 204.

At block 308, the extracted raw data is transformed. For example, the raw data converter 218 of the application 208 can cause the extracted raw data of the raw data 204 to be converted in response to a separate conversion engine 206. Specifically, at block 308 (1), the relevant information engine 206 is identified. For example, the raw data converter 218 may use the at least one parameter 118, additional identifiers in the additional information 212 (eg, transformation engine identifier), global settings of the application 208, etc. The engine 206 and / or its associated presentation rules may be identified. In block 308 (2), the identified transformation engine is applied to the retrieved raw data. For example, the raw data converter 218 may apply the identified transformation engine 206 that includes a set of display rules to the retrieved raw data of the raw data 204 to produce a result 120. The raw data converter 218 can cause the conversion engine 206 to perform this conversion without knowing any characteristics of the content of the conversion engine 206.

At block 310, the transformed raw data or field results are displayed as part of the data stream representation of the presentation file. For example, the application 208 can display the result 120 including the raw data converted as display data 106 for the field 108 that is part of the display file 102. The operations of the flowchart 300 may be performed in a different order than shown. For example, the transformation of block 308 may be performed prior to or at least partially overlapping with the extraction of block 306. Thus, in the example implementation, only portions of the raw data that remain after any filtering need to be extracted completely.

Specific implementation of field determination

4 is a block diagram of an analysis example of the built-in field 108. In the implementation described, field 108 includes field type 116 and at least one parameter 118. As shown, field type 116 includes a transform reference 402 field type and parameter (s) 118 includes at least raw data reference 404.

Field interpreter 214 confirms that field type 116 is a transform reference field type 402 as indicated by arrow 408. Thus, the field 108 is based on the raw data reference 404 and (i) the raw data 204 (FIG. 2) and (ii) the transformation engine 206 referenced by the raw data reference 404. Is determined in response.

Field interpreter 214 provides raw data reference 404 to raw data extractor 216 as indicated by arrow 410. Field interpreter 214 also provides a translation identifier 406 to raw data converter 218 as indicated by arrow 412. Three example locations are shown where the translation identifier 406 can be found. These examples include parameter (s) 118, additional information 212, and application 208. However, the translation identifier 406 may alternatively be placed within or in relation to other component (s). In addition, the raw data converter 218 may alternatively obtain the translation identifier 406 independently from any location.

5 is a block diagram of an example of extraction of raw data 204 for a built-in field. In the described implementation, the raw data 204 includes one or more data items 502. As shown, the raw data 204 includes " k " data items 502 (1 ... k), i.e. item # 1 502 (1), item # 2 502 (2). .Item #k (502 (k)). Each data item 502 corresponds to a data item type. As shown, data item # 1 502 (1) corresponds to data item type "Θ", data item # 2 502 (2) corresponds to data item type "∑", and data item # k 502 (k) corresponds to the data item type Θ ". The data item types are further described below with reference to FIGS.

Data items 502 include one or more respective tag fields 504 and associated respective data 506, referred to herein as tag-data pairs. As shown, data item #k 502 (k) includes "n" respective tag fields 504 associated with "n" each data entry 506. That is, tag field # 1 is associated with data entry # 1, tag field # 2 is associated with data entry # 2, tag field # 3 is associated with data entry # 3, and tag field #n is data entry #n. Associated with The manner in which the tag fields 504 are used by the raw data converter 218 is further described below with reference to FIG.

As shown, the raw data reference 404 refers to data item #k 502 (k). Raw data references 404 may include links, pointers, addresses, universal resource locators, uniform resource locators, some combination thereof, and the like. Raw data extractor 216 uses raw data reference 404 to locate and retrieve data item #k 502 (k), as indicated by arrow portion 508. Data item #k 502 (k) or at least a portion thereof is then provided to raw data converter 218 as indicated by arrow portion 510.

6 is a block diagram of an example of conversion of extracted raw data 240. In the implementation described, raw data converter 218 applies data item #k 502 (k) to transformation engine 206 as indicated by arrow 604. As shown, transformation engine 206 includes filter, sorting, and / or formatting capabilities 602. The nature of the filter, sort and / or format capabilities 602 is not known to the raw data converter 218.

The filter, sorting and / or formatting capability 602 is based on the selected display rule set and in response to the data item type of data item #k 502 (k) with respect to the tag fields 504 with data item #k ( 502 (k)) is adapted to filter, sort, and / or format. In this illustrative case, the display rule set selected for data item type Θ "is applied to data item #k 502 (k), where data item #k 502 (k) is data item type Θ". Because.

In general, the presentation rules may specify which tag fields 504 will be filtered, how the remaining tag fields 504 will be sorted, and how the remaining data entries 506 will be formatted. Specifically, tag-data pairs (eg, each tag field 504 associated with each data entry 506) may be filtered, sorted, and / or formatted. More specifically, one or more individual tag-data pairs may be filtered (eg, removed and / or excluded from the indication). In addition, tag-data pairs may be rearranged in a prescribed order. Furthermore, tag-data pairs may be arranged such that display text is centered, bolded, italicized, underlined, properly spaced, capitalized, highlighted, some combination thereof, etc. Can be formatted.

Thus, the filter, sort and / or format capabilities 602 of the transformation engine 206 yield a result 120 that is displayed as the display data 206. As shown in FIG. 6, the tag-data pairs of # 1 through #n were filtered and controlled tag-data pairs # 1, # 3, and #m as shown in result 120. These pairs were also rearranged in the order of tag-data pair # 3, tag-data pair # 1, and tag data pair #m.

The data entries 506 may also be formatted individually or as a group to generate the final appearance for the presentation data 206. Although result 120 is shown to include tag fields 504 in addition to data entries 506, result 120 is alternatively streamlined by omitting tag fields 504 to result 120. Can be effectively equivalent to the display data 106. As a result, result 120 may be displayed as display data 106 without first removing tag fields 504.

7 is a block diagram of an example conversion engine 206. In the described implementation, the transformation engine 206 includes at least one set of presentation rules 702. As shown, the conversion engine 206 has four sets of display rules 702: display rule A 702 (A), display rule B 702 (B), and display rule C 702 (C). And display rule D 702 (D). However, alternatively, transformation engine 206 may include fewer or more than four sets of presentation rules 702.

Regarding presentation rule set A 702 (A), there is a different subset 704 of presentation rules for each data item type of multiple data item types. As shown, the display rules A 702 (A) include rule subsets 704 targeting data items of type Δ, type Σ, type Θ ... type Ω. Display rule subsets 704 for each data item type may include their own set of filter, sorting and / or formatting capabilities 602. As a result, data entries 506 associated with the same kind of tag field 504 may be filtered, sorted, and / or differently formatted if they are part of data items 504 corresponding to different data item types. Can be. This is further illustrated by way of example using the bibliographic example in the next section.

The transformation identifier 406 (FIG. 4) can identify a separate set of presentation rules 702 of the transformation engine 206. If the set of presentation rules 702 is set globally (eg, by the application 208 or additional information 212), the fields 108 of the transform reference 402 field type are set globally. Each is displayed according to a set of presentation rules 702. Alternatively, the set of presentation rules 702 to be used is for each field (eg, with parameter 118, for each section or area of the file (eg, perhaps additional information 212). May also be set), or in any other manner.

Although both sets of display rules A and B 702 (A) and 702 (B) as shown in the conversion engine 206 of FIG. 7 clearly represent the same display rule subsets 704, the display Rule sets 704 may be different. For example, display rules C 702 (C) do not include a display rule subset 704 for data item 502 of type Δ, but display rule sub for data item 502 of type Φ. Has a set 704. In addition, display rules D 702 (D) include only a display rule subset 704 for data items 502 of types Δ, Σ, Θ, and Γ. Moreover, the presentation rule subset 704 for a given data item type may be exclusive to a single set of presentation rules 702. Other combinations and exchanges of the display rule sets 702 and the display rule subsets 704 are possible.

Bibliographic implementation example of field determination

An example application for determining a field in accordance with certain implementations as described above is associated with a reference document. Bibliographic data for a cited source may be entered once, and then bibliographic data may be used as a footnote, endnote, or the like. A user may search bibliographic data to find a citation or bibliography entry for a given source whenever a given source is entered.

Moreover, citation sources in displayable file 202 are included in data stream information 210 as fields 108 with field type 116 of translation reference 402. Thus, surge data can be extracted from the raw data 204. In addition, the raw surge data 204 may be converted in accordance with the set display rule 702. The display file 102 may then be repurposed by simply selecting a different display rule 702. That is, the user can insert a citation or bibliographic entry, extract the raw data (source data), and convert it according to a document style such as MLA or APA. After a citation or bibliographic entry is inserted, it can be retargeted by selecting a different document style (translation).

FIG. 8 is a block diagram that provides examples of surge related to the more general concepts and terms shown in FIGS. 1-7. Bibliographic related examples and implementations have been annotated using italic text in the example of FIG. 8. 8 includes raw data 204 and transformation engine 206. Although raw data 204 can be implemented in a variety of ways, in the implementation described, raw data 204 includes an Extensible Markup Language (XML) file or a portion of a file constructed in accordance with XML. Similarly, transformation engine 206 includes an Extensible Stylesheet Language (XSLT) file or a portion of a file configured according to XSLT in the described implementation. However, either can be implemented using other mechanism (s). By using non-proprietary open standards such as XML and XSLT, a user can create, edit, etc. raw data 204 and / or transformation engine 206 without using an application 208.

Translation engine 206 (eg, XSLT or other non-proprietary file) is installed and / or invoked by application 208. However, the application 208 need not be used to create or modify the transformation engine 206. Instead, the user can use any program that can generate a file that supports or follows the schema 220 specifying the available format (s) for the conversion engine 206. Thus, conversion engine 206 generated by an unknown file may be installed and / or invoked by application 208 to determine the fields in the displayable file. For example, the word processing program implementation of the application 208 may install or call any translation engine 206 that follows the specified schema 220, regardless of how the translation engine 206 was generated.

In the described implementation, the raw data 204 can include some of the additional information 212 of the master bibliographic data file and / or the displayable file 202. For example, a user may enter bibliographic data directly into a master file and have its citations copied into additional information 212. Alternatively, a user may enter bibliographic data directly into additional information 212 (eg, via application 208) and allow bibliographic data of the newly entered quote to be copied into the master file for subsequent use. Can be. As mentioned above, including bibliographic data in the additional information 212 is an optional implementation.

Raw data 204 includes at least one data item 502. As shown in FIG. 8, raw data 204 includes data item #k 502 (k) of type Θ. In a bibliographic related implementation, data item #k 502 (k) includes the individual bibliographic source #k being cited, and type Θ includes a source type such as a book. Examples of other bibliographic source types include periodicals, journals, broadcast programs, meeting minutes, speeches, journal articles, magazine or news articles, sound recordings, performances, themes / papers / reports, works of art, musical works, Internet sites, and Internet sites. Documents, such as, but not limited to.

Data item #k 502 (k) generally includes a number of entries. Specifically, there are respective data entries 506 associated with each tag field 504. Tag fields #n 504 are shown in this example as the title of the book that is the source for this data item 502. As a result, associated data entry #n 506 contains the actual title of source #k. Although only one tag-data pair is shown in FIG. 8, there are generally many such pairs. Additional examples of bibliographic related implementations for tag fields 504 include author, publication date, page, publisher, chapter title, article title, volume, number of copies, edition, URL, performer, writer, artist, version, director, etc. But it is not limited thereto. The specific tag fields 504 supported may optionally be changed by the data item type.

In a surge related implementation, the conversion engine 206 includes one or more surge formatting standards. Thus, each presentation rule 702 may be implemented as a separate surge formatting standard. As shown, presentation rule A 702 (A) is implemented as a set of rules for converting raw bibliographic data into bibliographic data that conforms to document-style American Psychological Union (APA) rules. Other exemplary bibliographic related implementations of the presentation rules 702 include, but are not limited to, the Modern Language Association (MLA), the Chicago Manual of Style, Turabian, author-date, etc. no.

Thus, in this surge related implementation, the translation engine 206 may be an XSLT for MLA, APA, etc. installed or called by a word processing application. Other XSLTs for other bibliographic document styles may also be created by the user and then installed or called by a word processing application. These other transformation engine 206 implementations cooperate with a word processing application as long as they are created to support the specified schema 220. The word processing application does not need to understand the internal mechanics of the conversion engine, and the user does not need to create or modify the conversion engine using the word processing application.

Since the presentation rules 702 tend to vary depending on the source type, each source type has a corresponding item type presentation rule subset 704. As a result, book citations may be formatted differently than periodical citations. As shown, item type Δ 704 is implemented as a display rule subset 704 of APA that aims to convert raw data for books into book citations that conform to the APA, and item type Σ is a periodical. It is implemented as a presentation rule subset 704 of APA that aims to convert the raw data for into a periodical citation following the APA.

In operation, the parameters of the presentation rule subset 704 define not only which tag fields 504 will be displayed in the result 120, but also their order. They can also define proper formatting, including capitalization and punctuation. Specifically, the parameters specify which of the data entries 506 will be displayed as the display data 106 of the display file 102.

Conclusion on field determination

In the implementations described, the transformation engine is generated according to an open standard (eg, XSTL) selected to support a given schema. The given schema is associated with the given application. The given schema specifies the format for the transformation engines that a given application can work with.

Thus, a given application is adapted to apply the transformation engine to the fields of the displayable file (eg by installing and / or invoking the transformation engine). The fields may be determined by a given application in response to the raw data and the transformation engine, as well as based on the field type and at least one parameter of the field. This determination can be made by the application even if the application does not know the internal mechanics of the conversion engine.

The conversion engine can be created, modified, and the like by the user without using a given application. Creation and / or modification is performed such that the resulting transformation engine follows a given schema. The user can use any program that can manipulate the file for the conversion engine.

By way of example only, the fields determined may be bibliographic related entries for a word processing document. Raw data that may be formatted according to open standards such as XML may include bibliographic related data. The transformation engine may include one or more bibliographic citation styles such as APA and MAL. The user can create his own bibliographic citation style or modify the documented style without using a word processing application. In any case, the word processing application can determine the surge related fields of the word processing document by applying a translation engine that includes at least one bibliographic citation style without having to understand the details of the internal mechanics of the translation engine.

Operating environment example for a computer or other device

9 is at least one system, device, device, component, arrangement, protocol, approach for determining an extensible markup language schema for fields and / or references and citations for a displayable file as described herein. , An example computing (or general purpose device) operating environment 900 that can implement methods, procedures, media, application programming interfaces (APIs), certain combinations thereof, and the like. Operating environment 900 may be used in computer and network architectures described below.

The example operating environment 900 is just one example of an environment, and it is desirable to propose any limitation as to the scope or functionality of the applicable device (computer, network node, entertainment device, mobile device, general purpose electronic device, etc.) architecture. no. The operating environment 900 (or devices thereof) should not be construed as having any dependencies or requirements with respect to any one component or any combination of components as shown in FIG. 9.

In addition, implementations for determining fields for displayable files and / or extensible markup language schemas for references and citations may be implemented using a variety of other general purpose or specialized devices (including computing systems) environments or configurations. . Examples of known devices, systems, environments and / or configurations that may be suitable for use include personal computers, server computers, thin clients, thick clients, PDAs or mobile phones, watches, hand-held or Laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, video game machines, game consoles, portable or hand-held game units, network PCs, video conferencing equipment, minicomputers, mainframe computers, networks A distributed or multiprocessing computing environment including nodes, any such system or apparatus, any combination thereof, and the like, is not limited thereto.

Implementations for determining fields for displayable files and / or extensible markup language schema for references and citations may be described in general with respect to processor executable instructions. In general, processor executable instructions include routines, programs, protocols, objects, functions, interfaces, components, schemas, data structures, etc. that perform and / or enable particular tasks and / or implement particular abstract data types. do. As described in certain implementations herein, implementations that determine fields for displayable files and / or extensible markup language schema for references and citations may be remote links that are connected through a communication link and / or a network. It can also be practiced in distributed processing environments where tasks are performed by specialized processing devices. In particular, but not exclusively, in a distributed computing environment, processor executable instructions may be located in separate storage media, executed by different processors, and / or propagated through transmission media.

Exemplary computing environment 900 includes a general purpose computing device in the form of a computer 902 that may include any (eg, electronic) device with computing / processing capabilities. Components of the computer 902 include a system bus 908 that couples one or more processors or processing units 904, system memory 906, and various system components including the processor 904 to the system memory 906. It may be, but is not limited thereto.

Processors 904 are not limited by the materials from which they are formed or the processing mechanisms used therein. For example, processor 904 may include semiconductor (s) and / or transistors (eg, electronic integrated circuits (ICs)). In this situation, the processor executable instructions may be electronically executable instructions. In the alternative, the mechanisms of or for the processor 904 and, thus, or for the computer 902 may include, but are not limited to, quantum computing, optical computing, mechanical computing (eg, using nanotechnology), and the like. It doesn't happen.

System bus 908 is one of many types of wired or wireless bus structures including memory buses or memory controllers, point-to-point connections, switching fabrics, peripheral buses, accelerated graphics ports, and processor or local buses using any of a variety of bus architectures. Any one or more. As an example, these architectures include PCI (also known as an industrial standard architecture (ISA) bus, micro channel architectrue (MCA) bus, Enhanced ISA (EISA) bus, video electronics standard association (VESA) local bus, and mezzanine bus). peripheral component interconnect) buses, any combination thereof, and the like.

Computer 902 typically includes a variety of processor accessible media. Such media may be any available media that can be accessed by the computer 902 or other (eg, electronic) device, and may be volatile and nonvolatile media, removable and non-removable media, and storage and transmission media. It includes.

System memory 906 includes processor accessible storage media in the form of volatile memory such as RAM 910 and / or nonvolatile memory such as ROM 912. Basic input / output system (BIOS) 914, which includes basic routines that assist in transferring information between elements in computer 902, for example at startup, is generally stored in ROM 912. RAM 910 generally includes data and / or program modules and / or instructions that may be readily accessed by processing unit 904 and / or currently operating on processing unit 904.

Computer 902 may also include other removable / removable and / or volatile / nonvolatile storage media. For example, FIG. 9 illustrates a (normally) hard disk drive or disk drive array 916 for reading from and writing to non-removable, nonvolatile magnetic media (not shown separately); A magnetic disk drive 918 for reading from and writing to a (generally) removable, nonvolatile magnetic disk 920 (eg, “floppy disk”); And optical disk drive 922 for reading from and / or writing to a (generally) removable, nonvolatile optical disk 924, such as a CD, DVD or other optical medium. Hard disk drive 916, magnetic disk drive 918, and optical disk drive 922 are each connected to system bus 908 by one or more storage media interfaces 926. Alternatively, hard disk drive 916, magnetic disk drive 918, and optical disk drive 922 may be connected to system bus 908 by one or more other discrete or combined interfaces (not shown).

Disk drives and processor accessible media associated with them provide nonvolatile storage of processor executable instructions, such as data structures, program modules, and other data for the computer 902. Although the example computer 902 shows a hard disk 916, a removable magnetic disk 920 and a removable optical disk 924, other types of processor accessible media include magnetic cassettes or other magnetic storage devices, flash memory, It should be appreciated that the instructions may be stored by a device such as a CD, DVD or other optical storage device, RAM, ROM, EEPROM or the like. Such media may also include so-called special or hard wired IC chips. That is, any processor accessible media may be used to implement the storage media of the example operating environment 900.

As a general example, any number of program modules (or other units or sets of processor executable instructions), including an operating system 928, one or more application programs 930, other program modules 932, and program data 934, may be used. Hard disk 916, magnetic disk 920, optical disk 924, ROM 912, and / or RAM 910. These processor executable instructions may include, for example, displayable file 202 with embedded fields 108, raw data 204, transformation engine 206, applications 208 capable of processing built-in fields 108, It may include one or more of any combination thereof. These processor executable instructions may also include, for example, a schema, accessing a schema, modifying a schema, use of a schema to interpret and / or create a data structure, and the like.

A user may enter commands and / or information into the computer 902 through input devices such as a keyboard 936 and pointing device 938 (eg, a “mouse”). Other input devices 940 (not specifically shown) may include a microphone, joystick, game pad, satellite dish, serial port, video camera, scanner, and the like. These and other input devices are connected to the processing unit 904 via an input / output interface 942 coupled to the system bus 908. However, the input device and / or output device may instead be connected to other devices such as parallel ports, game ports, universal serial bus (USB) ports, infrared ports, IEEE 1394 ("firewire") interfaces, IEEE 802.11 wireless interfaces, Bluetooth wireless interfaces, and the like. It may be connected by an interface and a bus structure.

Monitor / view screen 944 or other type of display device may also be connected to system bus 908 via an interface such as video adapter 946. The video adapter 946 (or other component) may be or include a graphics card for handling graphics intensive calculations and handling difficult display requests. Generally, graphics cards include a graphics processing unit (GPU), video RAM (VRAM), and the like, to facilitate the rapid display of graphics and the performance of graphics operations. In addition to the monitor 944, other output peripherals may include components such as a speaker (not shown) and a printer 948 that may be connected to the computer 902 via an input / output interface 942.

Computer 902 may operate in a networked environment using logical connections to one or more remote computers, such as remote computing device 950. For example, the remote computing device 950 may be a peripheral device, personal computer, portable computer (eg, laptop computer, tablet computer, PDA, mobile station, etc.), palm or pocket size computer, clock, game device, server, Routers, network computers, peer devices, other network nodes, or other device types described above. However, the remote computing device 950 is shown as a portable computer that can include most or all of the elements and features described herein in connection with the computer 902.

The logical connection between computer 902 and remote computer 950 is shown as LAN 952 and general purpose WAN 954. Such networking environments are commonplace in offices, enterprise broadband computer networks, intranets, the Internet, fixed and mobile telephone networks, ad hoc and infrastructure wireless networks, mesh networks, other wireless networks, gaming networks, some combination thereof, and the like. Such network and logical and physical communication connections are further examples of transmission media.

When implemented in a LAN networking environment, the computer 902 is typically connected to the LAN 952 through a network interface or adapter 956. When implemented in a WAN networking environment, the computer 902 typically includes a modem 958 or other component for establishing communications over the WAN 954. The modem 958, which may be internal or external to the computer 902, may be connected to the system bus 908 via an input / output interface 942 or any other suitable mechanism (s). It is to be appreciated that the network connections shown are examples and that other ways to establish communication link (s) between the computers 902, 950 may be used.

In a networked environment as shown in conjunction with operating environment 900, program modules or other instructions described with respect to computer 902 or portions thereof may be stored in whole or in part in remote media storage. As an example, remote application program 960 is located on a memory component of remote computer 950, but can be used or accessed by computer 902. Also, by way of example, other processor executable instructions, such as the application 930 and the operating system 928, are shown in separate blocks herein, but such programs, components, and other instructions may be modified in the computing device 902 at various times. (And / or located in different storage components of the remote computing device 950) and executed by the processor (s) 904 of the computer 902 (and / or the processors of the remote computing device 950). I understand that.

Extensible Markup Language Schema for References and Citations

Implementations described herein generally relate to extensible markup language (XML) schemas for references and / or citations. For example, certain implementations may be implemented as data structure (s) that include part (s) of the entire schema, including the schema for bibliographic information. Other example implementations may be implemented as at least one module that may utilize a schema for bibliographic information. Data structures, modules, and the like may be implemented on or as part of a processor accessible medium.

10 illustrates an example schema 1004 that defines a framework for bibliographic information 1002 and / or enables the use of bibliographic information by schema usage module 1006. As shown, FIG. 10 is a block diagram that includes an application 208, raw data 204, a schema 1004 for bibliographic information, and a schema usage module 1006. In addition, bib info 1002 is shown in two exemplary locations.

Application 208 provides access to document 202 *. Access can include the creation, display, modification, interpretation, etc. of document 202 *. Application 208 may be, for example, a text based application such as a word processor, html editor, or the like. Document 202 * is a specific example of displayable file 202 (FIG. 2). Bibliographic information 1002 of document 202 * is part of built-in field 108 (FIG. 1), as part of additional information 212 (FIG. 2), and part of some other portion of document 202 *. As a predetermined combination thereof, or the like. Document 202 * may be stored according to a variety of different file formats, and optionally according to the native programming language of application 208 that originally created document 202 *.

Raw data 204 is described above generally. Raw data 204 may be inserted into a document, part of a master list, or the like. The document specific raw data 204 may be inserted as part of the document 202 *. A bibliographic information file serving as a master list is described above in particular in connection with FIG. 8 in the section entitled "Surge Related Implementations for Field Determination".

Raw data 204 includes bibliographic information 1002. Raw data 204, and thus bibliographic information 1002, is part of a master list of bibliographic information, as bibliographic information embedded in a document (eg, as shown with respect to document 202 *), and the like. It can be implemented as. Although not specifically shown in FIG. 10, bibliographic information 1002 may also be present in other locations, in other environments and / or situations, and in other formats.

In general, the raw data 204 master list is a file that contains many bibliographic entries for a user, for an application, for a computing device, for some combination thereof, and the like. Typically, the raw data 204 master list includes bibliographic entries that may be used and / or used in multiple documents 202 *. Bibliographic entries may be first entered into the raw data 204 master list and then copied into the document 202 *. Alternatively, bibliographic entries may first be entered into document 202 * and then copied into the raw data 204 master list.

In the implementation described, schema 1004 provides a framework for bibliographic information 1002. For example, the schema 1004 may define, describe, display, describe, etc. the layout, organization, interrelationships, and permissible content of the bibliographic information 1002. Schema 1004 may be included as part of schema 220 (FIG. 2), or as part of another schema, or schema 1004 may exist individually. Schema 1004 enables understanding of raw data 204 with bibliographic information 1002 present in accordance with schema 1004.

By way of example only, schema 1004 may follow extensible markup language (XML) formatting. Schemas that define different source types of the example XML-based schema 1004 for bibliographic information 1002 are described below. The example schema below defines which bibliographic source type can contain which data. In addition, the exemplary schema defines acceptable format (s) (eg, strings, integers, specially defined types, etc.) for each of the data.

Schema usage module 1006 is adapted to enable the use of bibliographic information 1002. Examples of schema usage include the creation, modification, interpretation, application, etc. of a schema and / or information that conforms to the schema. Schema usage module 1006 may be part of an application 208 or other software program (including an OS) (including a plug-in), or schema usage module 1006 may be an independent program. In any case, the schema utilization module 1006 may be configured to interact with other programs. Such interaction may include, for example, being callable by another program, being a plug-in of another program, calling another program, and the like. As a specific example, a web service can create an add-on for the "Research and Reference" window introduced in Microsoft Word 2003 (available from Microsoft Corporation, Redmond, Washington). The web service accepts the search criteria and returns a match with bibliographic metadata that conforms to schema 1004. The bibliographic information 1002 may then be inserted into the document 202 *.

For example, an application 208 displaying a document 202 * previously generated by a given program may interpret the bibliographic information 1002 according to the schema 1004 using the schema usage module 1006. . As another example, the application 208 can call the schema usage module 1006 so that the schema 1004 can be used to generate a data structure of bibliographic information 1002 that is formatted according to the schema 1004. The data structure of the generated bibliographic information 1002 may be a master list such as the raw data 204, the document embedded raw data 204, and the like. In addition, the application 208 can call the schema usage module 1006 so that the schema 2004 can be used to modify the data structure of the bibliographic information 1002 formatted according to the schema 1004.

In one example, a user can enter source data for bibliographic information 1002 into document 202 * using application 208 (eg, in cooperation with schema usage module 1006). The user can select a window (e.g., each field) identified as corresponding to each tagged portion (e.g. title, author, publication date, etc.) of a given source type (e.g., book, periodical article, etc.) For example, source data can be input using a dialog box. Exemplary XML-based source types that can be used to generate such an input window are described below in the section entitled "Extensible Markup Language-Based Description of Source Types for References and Citations" along with their tagged portions. The input source data may be automatically included in the bibliographic information 1002 configured according to the schema 1004 for bibliographic information. The bibliographic information 1002 may then be stored by the application 208 as part of the document 202 *.

In some implementations, programmatically via schema utilization module 1006, which enables manipulation of other software application programs (eg, bibliographic information 1002), written directly via one or more APIs, or in accordance with various programming languages, An object-oriented programming model is provided for authorizing manipulation of bibliographic information 1002, either individually or in conjunction with a document 202 *, through a set of API or object-oriented message calls. C ++, C #, Visual Basic, etc. In one example, an object oriented program model is disclosed in US Patent Application No. 11 / 280,101 entitled "Programmable Object Models for Bibliographies and Citations" filed on the same page as this application. It is composed.

Example XML-Based Schema for References and Citations

As described above, schema 1004 may be created, interpreted, modified, or used by schema usage module 1006. Schema 1004 may be used by schema usage module 1006 in accordance with the exemplary bibliographic source schema provided below.

 Thus, the following is a description of an example schema associated with XML notation for references and citations. Although specific examples of schemas are described below, alternatively more, fewer and / or different source types may be included in a given XML schema for references and citations. Moreover, alternative correlations and data types may alternatively be defined by such a schema.

Examples of the schema below include 17 different bibliographic source types, which include books, book sections, journal articles, periodical articles, meeting minutes, reports, sound recordings, performances, art, documents on Internet sites, Internet sites, Movies, interviews, patents, electronic sources, cases and crap. An example schema is as follows.

Extensible markup language-based description of source types for references and citations

An example of an implementation of a source type is described below. 17 exemplary source types are shown below in XML format, although other formats may alternatively be used. By way of example only, XML data tags may be used to populate a dialog or similar user input mechanism used in word processing or other text editing program. The dialog box enables acquisition of raw source information or bibliographic source information for document embedded bibliographic information and the like. Each surge source may have a number of data associated with it as specifically indicated below by the data tag for each source type.

Thus, the following is a description of example XML that can be used to activate a dialog box in an application 208. The user can enter a notation for references and citations that follow the schema 1004. The exemplary notation is divided into 17 parts, each corresponding to each surge source type. However, alternatively more, fewer and / or different source types may be included in a given XML notation set for references and citations.

The description below for example source types relates primarily to each set of tagged portions that may correspond or be associated with each source type. Each example tagged portion is for an attribute of each source type and generally includes two subtags, a label and a data tag. Source types can be combined into a set of types.

The 17 example source types include books, book sections, journal articles, periodical articles, minutes, reports, sound recordings, performances, arts, documents on Internet sites, Internet sites, movies, interviews, patents, electronic sources, precedents and miscellaneous articles. to be.

Source Type # 1: Books

Books may be cited as bibliographic sources. Exemplary attributes for a book bibliographic source are author, title, year, city, state / country, publisher, editor, subtitle, volume, volume number, translator, standard number, and comment.

An example XML portion of a book bibliography source follows.

Source Type # 2: Book Section

Book sections may be cited as bibliographic sources. Exemplary attributes for the book section bibliographic source are author, title, book author, book title, year, page, city, state / country, publisher, editor, translator, subtitle, volume, volume number, standard number, and comment.

An example XML portion of a book section bibliographic source follows.

Source Type # 3: Journal Article

Journal articles may be cited as bibliographic sources. Exemplary attributes for the journal article bibliographic source are author, title, journal name, city, month, day, year, page, editor, publisher, volume, number of copies, subtitle, standard number, and comment.

An example XML portion of a journal article bibliographic source follows.

Source Type # 4: Periodical Article

Periodic articles may be cited as bibliographic sources. Exemplary attributes for the periodical article bibliographic source are author, title, periodical title, city, month, day, year, page, subtitle, editor, publisher, edition, volume, publication number, standard number, and comment.

An example XML portion of a periodical article bibliographic source follows.

Source Type # 5: Minutes

Minutes may be cited as a bibliographic source. Exemplary attributes for the minutes bibliographic source are author, title, editor, page, year, meeting name, city, publisher, subtitle, volume, standard number, and comment.

An example XML portion of the minutes bibliographic source is as follows:

Source Type # 6: Reports

The report may be cited as a bibliographic source. Exemplary attributes for the report bibliographic source are author, title, year, sector, society, publisher, city, subtitle, page, report type, standard number, and comment.

An example XML portion of a report bibliographic source is as follows:

Source Type # 7: Sound Recording

Sound recording may be cited as the surge source. Exemplary attributes for the sound recording bibliographic source are composer, conductor, performer, artist, title, album title, producer name, production company, year, medium, city, state / country, recording number, subtitle, standard number, and comment.

An example XML portion of a sound recording surge source is as follows.

Source Type # 8: Performances

The performance may be cited as a bibliographic source. Exemplary attributes for a performance bibliographic source are title, author, performer, producer name, production company, director, theater, city, state / country, month, day, year, subtitle, and comment.

An example XML portion of a show bibliographic source is as follows.

Source Type # 9: Art

Art can be cited as a bibliographic source. Exemplary attributes for the art bibliographic source are artist, title, association, publication title, city, state / country, publisher, year, page, subtitle, and comment.

An example XML portion of an art bibliographic source is as follows:

Source Type # 10: Documents on the Internet

Documents on Internet sites can be cited as bibliographic sources. Exemplary attributes for Internet site document bibliographic sources include author, title, editor, internet site name, publisher name, publisher, month, day, year, month accessed, day accessed, year accessed, URL, medium, version, It is a subtitle, standard number and comment.

An example XML portion of an Internet site document bibliographic source is as follows.

Source Type # 11: Internet Sites

Internet sites can be cited as bibliographic sources. Exemplary attributes for Internet site bibliographic sources are Author, Title, Internet Site Title, Editor, Producer Name, Publisher, Month, Day, Year, Month Accessed, Day Accessed, Year Accessed, URL, Medium, Version, Subtitle And comments.

An example XML portion of an internet site bibliographic source is as follows.

Source Type # 12: Movie

The movie may be cited as a bibliographic source. Exemplary attributes for a film bibliographic source are title, performer, producer name, producer, director, country, distributor, author, media, subtitle, year, standard number, and comment.

An example XML portion of a film bibliographic source is as follows.

Source Type # 13: Interview

The interview may be cited as a bibliographic source. Example attributes for interview bibliographic sources include interviewer, interview title, program title, interviewer, month, day, year, publisher, broadcaster, station, city, state / country, editor, translator, collector, page, It is a subtitle, standard number and comment.

An example XML portion of the interview bibliographic source follows.

Source Type # 14: Patent

Patents can be cited as bibliographic sources. Exemplary attributes for the patent bibliographic source are inventor, title, month, day, year, country, type, patent number, subtitle, editor, translator, and comment.

An example XML portion of a patent bibliographic source is as follows.

Source Type # 15: Electronic Source

The electron source can be referred to as a surge source. Exemplary attributes for an electronic source bibliographic source include author, title, publication title, city, state / country, editor, producer name, publisher, translator, publisher, edition, medium, volume, month, day, year, subtitle, standard number. And comments.

An example XML portion of an electronic source bibliographic source is as follows.

Source Type # 16: Case Study

Cases can be cited as bibliographic sources. Exemplary attributes for a case bibliographic source are author, title, year, case number, reporter, place of publication, court, month, day, year, attorney, subtitle, simplified case number, and comment.

An example XML fragment for a case bibliographic source follows.

Source Type # 17: Sundries

A "junk" source may be cited as a bibliographic source. Exemplary attributes for a bibliographic source include author, title, publication title, month, day, year, city, state / country, publisher, editor, page, subtitle, volume, edition, publication number, translator, collector, standard number. And comments.

An example XML fragment for a junk bibliographic source follows.

The apparatus, operations, aspects, features, functions, procedures, modules, data structures, objects, components, etc. of FIGS. 1-10 are illustrated in a diagram divided into a number of blocks. However, the order, interconnections, interrelationships, layouts, etc. that are described and / or illustrated in FIGS. Any number of blocks can be modified, combined, rearranged, augmented in any manner to implement one or more systems, methods, devices, procedures, media, devices, schemas, APIs, arrays, etc. to determine the markup language schema. , May be omitted. Moreover, while the description herein includes references to specific implementations (including the general purpose device of FIG. 9), the implementations shown and / or described may be implemented in any suitable hardware, software, firmware, or combination thereof. have.

Thus, systems, media, devices, methods, procedures, apparatus, techniques, approaches, procedures, schemas, arrays, and other implementations are described in language specific to structural, logical, algorithmic, functional features, and / or drawings, It is to be understood that the invention as defined in the appended claims does not need to be limited to the specific features and drawings described. Rather, the specific features and figures are disclosed as example forms of implementing the claimed invention.

Claims (27)

Raw data 204 including a number of data items 502 including a particular data item of a particular data item type; A displayable file 202 having a field type 116 and a field 108 including at least one parameter 118 referencing the particular data item; And Transformation engine 206 comprising a plurality of sets of display rules 702 including at least one set of display rules with a specific display rule subset 704 targeting the particular data item type. Including, The transformation engine is separate from an application (208) capable of applying the transformation engine to at least the particular data item. 2. The apparatus of claim 1, wherein the raw data is constructed in accordance with extensible markup language (XML) and the transformation engine is configured in extensible stylesheet language (XSLT). The apparatus of claim 1, wherein the field includes a result suitable for display, the result indicating the particular data item after application of the particular display rule subset targeting the particular data item of the particular data item type. . The method of claim 1, A field interpreter capable of interpreting the field with respect to the field type and the at least one parameter; A raw data extractor adapted to extract at least a portion of the specific data item from the raw data in response to the at least one parameter referring to the specific data item; And A raw data converter adapted to apply the at least one set of presentation rules to the particular data item Further comprising an application comprising a, And the particular presentation rule subset targeting the particular data item of the particular data item type is applied to the particular data item without direct control by the application. 5. The apparatus of claim 4, wherein the filtering capability of the particular presentation rule subset is applied to the particular data item prior to extraction of the particular data item such that filtered tag-data pairs are not extracted by the raw data extractor. The apparatus of claim 1, wherein the conversion engine can be modified without using the application. As a method for an application 208, Interpreting the field 304; Extracting 306 raw data for the field from a first file portion 204 in response to the interpretation; And Converting the raw data before display of the field using a second file portion 206 (308) Including, The first file portion (204) and the second file portion (206) are separate from the application (208). The method of claim 7, wherein Displaying the converted raw data as part of a data stream representation of the displayable file More, The conversion is performed without direct control by the application, Each of the first file portion and the second file portion comprises a portion of the displayable file. The method of claim 7, wherein The interpretation step is Identifying the field type of the field being interpreted and Obtaining at least one parameter of the field to be interpreted How to include. The method of claim 9, The extraction step Finding the raw data in response to the obtained at least one parameter comprising a reference to the first file portion having the raw data; And Retrieving at least a portion of the raw data from the first file portion as indicated by a reference to the raw data How to include. The method of claim 7, wherein The conversion step is Identifying a translation engine of the second file portion; And Applying the identified transformation engine to the raw data to generate transformed raw data as display data for the field How to include. The method of claim 11, wherein the step of identifying comprises: (i) at least one parameter of the field, (ii) additional information in a file embedded with the field, (iii) setting of an application that performs the method or (iv) the Obtaining an identifier of the conversion engine from at least one of the operating systems on which the application runs. 8. The method of claim 7, wherein the field represents a bibliographic citation for a source, the raw data includes bibliographic data for the source, and the transformed raw data generated by the transform is filtered, sorted, and And / or at least a portion of the bibliographic data after formatting. The method of claim 7, wherein The interpretation step is Determining that the field type of the field indicates that the referenced raw data should be converted prior to display of the field; And Obtaining, from the field, at least one parameter containing a reference to a data item of the raw data Including, The extraction step Retrieving at least a portion of a data item of the raw data from a location referenced by the at least one parameter Including, The conversion step is Applying a transformation engine including a plurality of sets of presentation rules to the referenced data item of the raw data Including; The application is unaware of the internal mechanics of the plurality of sets of presentation rules. 15. The method of claim 14, wherein the applying step includes applying a subset of display rules targeting a type of raw data corresponding to the referenced data item. A system having one or more processor accessible media containing processor executable instructions, the system comprising: The processor executable instructions include an application 208 that can process built-in fields 108, the application responsive to at least one parameter 118 of the field, field 108 of file 202. Is adapted to retrieve 216 raw data 204, wherein the at least one parameter refers to the raw data 404, and the application is also internal to display rules 702 of the selected set of transformation engines. The system is adapted to cause the referenced raw data to be converted in accordance with the selected set of display rules (702) of the transformation engine without knowledge of the mechanics. 17. The system of claim 16, wherein the application is further adapted to enable a user to set display rules of the selected set of the conversion engine at a global level for at least one of the file or the application. 18. The system of claim 17, wherein the application is able to reprocess a plurality of embedded fields of the file in response to a user selection of the selected set of presentation rules. 17. The application of claim 16, wherein the referenced raw data includes a data item of a particular data item type, and wherein the selected set of display rules includes a specific display rule subset targeting the specific data item type. And / or the transformation engine is adapted to apply the specific presentation rule subset targeting the specific data item type to the referenced data item. The method of claim 16, wherein the application may enable a user to create a built-in field for the file, wherein the built-in field is based on one or more parameters of the built-in field and wherein And an indication that the device is intended to be displayed in response to the selected set of presentation rules, wherein the application enables the user to cause one or more parameters of the embedded field to reference a data item of the raw data. One or more processor accessible media containing processor executable instructions that include a schema 1004 for bibliographic information 1002, the method comprising: The schema (1004) comprises one or more processor source types to provide a framework for the bibliographic information (1002). The one or more processor-accessible media as recited in claim 21, wherein the schema conforms to an Extensible Markup Language (XML) format. The one or more processor-accessible media as recited in claim 21, wherein the framework defines at least one of layout, organization, interrelationship, or permissible content for the bibliographic information. 23. The one or more processor accessible media of claim 21, wherein each surge source type of the plurality of surge source types is limited to a string 255 data type. 22. The one or more processor-accessible media as recited in claim 21, wherein the schema can be used to create, modify, or interpret bibliographic raw data organized according to the framework by a schema usage module. The method of claim 21, wherein the plurality of bibliographic source types include books, book sections, journal articles, periodical articles, minutes, reports, sound recordings, performances, artworks, movies, interviews, internet sites, documents on internet sites, patents, One or more processor-accessible media comprising a surge source type selected from the group of surge source types including an electronic source, a case and a random source type. 22. The method of claim 21, wherein the processor executable instructions further comprise bibliographic information raw data comprising a plurality of surge sources of different surge source types of the plurality of surge source types, wherein each surge source of the plurality of surge sources One or more processor accessible media containing attribute data in accordance with the schema.

Images