https://www.bibsonomy.org/user/pitman/formatBibSonomy RSS Feed for /user/pitman/formatThe eXtensible Text Framework (XTF) is an architecture that supports searching across collections of heterogeneous textual data (XML, PDF, HTML, text, and more), and the presentation of results and documents in a highly configurable manner. http://sourceforge.net/projects/xtf/pitman2009-03-20T20:40:27+01:00text format architecture <span itemprop="description">The eXtensible Text Framework (XTF) is an architecture that supports searching across collections of heterogeneous textual data (XML, PDF, HTML, text, and more), and the presentation of results and documents in a highly configurable manner. </span>Template for use in RePEc Here are some template for use by archive maintainers. Cut and paste them, or save them, and then fill out. Delete unnecessary lines, repeat clusters (like author, file) as a whole. Addition attributes are available, please see the ReDIF documentation for complete details. Attributes that go over one line should start with an empty space in all subsequent lines. Series templates need all to be in the same file (xxxseri.rdf). It does not matter whether individual templates are in separate files or not, as long as they are all in the same directory (one for each series, directory name with 6 characters). http://ideas.repec.org/templates.htmlpitman2009-01-27T03:23:12+01:00RePEc data format templates <span itemprop="description">Template for use in RePEc Here are some template for use by archive maintainers. Cut and paste them, or save them, and then fill out. Delete unnecessary lines, repeat clusters (like author, file) as a whole. Addition attributes are available, please see the ReDIF documentation for complete details. Attributes that go over one line should start with an empty space in all subsequent lines. Series templates need all to be in the same file (xxxseri.rdf). It does not matter whether individual templates are in separate files or not, as long as they are all in the same directory (one for each series, directory name with 6 characters). </span>The bibliography conversion service lets you convert your BibTeX or EndNote bibliography to BibTeX, EndNote, HTML, or Silva XML. For an example of an HTML bibliography, please visit dret's online bibliography, which has been generated from BibTeX. Note the OpenURLs, which enable users to simply look up the ETHZ library catalog for this particular resource. When generating HTML, this OpenURL resolver (and many other options) can be configured to generate customized HTML.http://dret.net/bibconvert/pitman2009-01-26T00:59:41+01:00bibliography bibtex conversion format xml <span itemprop="description">The bibliography conversion service lets you convert your BibTeX or EndNote bibliography to BibTeX, EndNote, HTML, or Silva XML. For an example of an HTML bibliography, please visit dret&#039;s online bibliography, which has been generated from BibTeX. Note the OpenURLs, which enable users to simply look up the ETHZ library catalog for this particular resource. When generating HTML, this OpenURL resolver (and many other options) can be configured to generate customized HTML.</span>Internet Message Format Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract This standard specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This standard supersedes the one specified in Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. http://www.ietf.org/rfc/rfc2822.txtpitman2009-01-26T00:41:59+01:00format internet message spec <span itemprop="description">Internet Message Format Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the &#034;Internet Official Protocol Standards&#034; (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract This standard specifies a syntax for text messages that are sent between computer users, within the framework of &#034;electronic mail&#034; messages. This standard supersedes the one specified in Request For Comments (RFC) 822, &#034;Standard for the Format of ARPA Internet Text Messages&#034;, updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. </span>The growing public perception is that PDF is too bulky and increasingly too opaque for the networked world. This is because PDF’s have not kept up with the prevailing trends of transparency, findability, and collaboration. PDF is important as a container with certain rights & privileges (DigSig, Security, Markup, Forms), but the data inside a PDF is far more important. Currently, PDF’s are way too opaque, too bloated, and do not clearly convey value to most users. This is especially true on mobile (why would I chose to view PDF on mobile if not required by an enterprise I need to engage with?). For most enterprises and customers, PDF is a cloud of data more than a display standard. It’s value is no longer in consistent display of fonts and formatting. It’s in the data within the millions of PDF’s that the IRS has, for example. Even as a Forms front-end it’s difficult to see why Reader/Acrobat is a better solution than a robust customizable Flash interface. The Flash-based Portfolios feature is a step in this direction.http://www.urbeingrecorded.com/news/2009/01/12/how-to-keep-pdf-relevant-flash-and-semantics/pitman2009-01-13T00:37:47+01:00PDF flash format semantic_web <span itemprop="description">The growing public perception is that PDF is too bulky and increasingly too opaque for the networked world. This is because PDF’s have not kept up with the prevailing trends of transparency, findability, and collaboration. PDF is important as a container with certain rights &amp; privileges (DigSig, Security, Markup, Forms), but the data inside a PDF is far more important. Currently, PDF’s are way too opaque, too bloated, and do not clearly convey value to most users. This is especially true on mobile (why would I chose to view PDF on mobile if not required by an enterprise I need to engage with?). For most enterprises and customers, PDF is a cloud of data more than a display standard. It’s value is no longer in consistent display of fonts and formatting. It’s in the data within the millions of PDF’s that the IRS has, for example. Even as a Forms front-end it’s difficult to see why Reader/Acrobat is a better solution than a robust customizable Flash interface. The Flash-based Portfolios feature is a step in this direction.</span>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=officepitman2008-11-30T19:34:59+01:00document format metadata open standard <a itemprop="url" data-versiondate="2008-11-30T19:34:59+01:00" href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" rel="nofollow" class="description-link">http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>hResume is a microformat for publishing résumé or Curriculum Vitae (CV) information [1] using (X)HTML on web pages. Like many other microformats, hResume uses CSS class names to make an otherwise non-semantic XHTML document more meaningful. A document containing resume information could be improved to use hResume without altering the appearance to the browser, making it easy to adopt.http://en.wikipedia.org/wiki/HResumepitman2008-11-14T03:02:41+01:00XHTML cv format microformat resume wikipedia <span itemprop="description">hResume is a microformat for publishing résumé or Curriculum Vitae (CV) information [1] using (X)HTML on web pages. Like many other microformats, hResume uses CSS class names to make an otherwise non-semantic XHTML document more meaningful. A document containing resume information could be improved to use hResume without altering the appearance to the browser, making it easy to adopt.</span>http://wiki.bibliontology.com/index.php/Development_Brainstormingpitman2008-11-12T01:29:01+01:00RDF bibliographic format ontology semanticweb wiki <a itemprop="url" data-versiondate="2008-11-12T01:29:01+01:00" href="http://wiki.bibliontology.com/index.php/Development_Brainstorming" rel="nofollow" class="description-link">http://wiki.bibliontology.com/index.php/Development_Brainstorming</a>author: Thomas Krichel Abstract: This document describes current version of the Research Documents Information Format (ReDIF). This is a simple "field: value" data format inspired from the IAFA templates. A primitive nesting stucture syntax is enabled through the use of clusters of fields. ReDIF is currently used by RePEc.http://ideas.repec.org/p/rpc/rdfdoc/redif.htmlpitman2008-10-03T00:46:29+02:00document format <span itemprop="description">author: Thomas Krichel Abstract: This document describes current version of the Research Documents Information Format (ReDIF). This is a simple &#034;field: value&#034; data format inspired from the IAFA templates. A primitive nesting stucture syntax is enabled through the use of clusters of fields. ReDIF is currently used by RePEc.</span>Reference Type Field Names The following describes the valid reference type field names that can be used with for the reference type field when importing references into Reference Manager.http://www.refman.com/support/risformat_reftypes.asppitman2008-05-02T01:55:18+02:00RIS field format names type <span itemprop="description">Reference Type Field Names The following describes the valid reference type field names that can be used with for the reference type field when importing references into Reference Manager.</span>http://en.wikipedia.org/wiki/RIS_(file_format)pitman2008-01-17T07:22:21+01:00bibliographic data format <a itemprop="url" data-versiondate="2008-01-17T07:22:21+01:00" href="http://en.wikipedia.org/wiki/RIS_(file_format)" rel="nofollow" class="description-link">http://en.wikipedia.org/wiki/RIS_(file_format)</a>http://www.wikisym.org/wiki/index.php/WSR_3pitman2007-12-31T17:46:12+01:00format interchange semantic_web wiki <a itemprop="url" data-versiondate="2007-12-31T17:46:12+01:00" href="http://www.wikisym.org/wiki/index.php/WSR_3" rel="nofollow" class="description-link">http://www.wikisym.org/wiki/index.php/WSR_3</a>