1 / 7

An Easier Way for Creating Model Metadata

An Easier Way for Creating Model Metadata. Easier is cheaper, and cheaper is better for everyone!. Here’s the Idea:. Develop a web interface, “fill in the blank” form where metadata could be entered, answering simple questions and selecting from code lists, etc. Throw in a little XML.

kiefer
Télécharger la présentation

An Easier Way for Creating Model Metadata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Easier Way for Creating Model Metadata Easier is cheaper, and cheaper is better for everyone!

  2. Here’s the Idea: Develop a web interface, “fill in the blank” form where metadata could be entered, answering simple questions and selecting from code lists, etc.

  3. Throw in a little XML The information would be tagged with the corisponding short name tag, and then the data could be put transferred into two different formats. Either: A document format or A file that can be stored in a model database

  4. A Pretty Document Model Title: CToM: The Crosier Toast model Version of Model: 1.1 Responsible Party: Crosier, S. J. Date of creation: 2000-07-01 Keywords: toast, breakfast, cooking Model Title: <title> Version of Model: <version> Responsible Party: <respparty> Date of creation: <date> Keywords: <keyword> A Little Computer Magic The short names would have their spot on a basic document format. Each location on this document where a short name tag exists, would be replaces with it’s corrisponding.

  5. An XML File The data that was entered could also be converted, using the standardized short names, into an XML file which could be easily transferred or stored. The modeler could create one XML file for his or her model. They could store a copy of the file, and could send the file to anyone who was interested in knowing more about the model. <title>CToM: The Crosier Toast Model</title> <version>1.1</version><respparty>Crosier, S.J. </respparty><createdate>2000-07-01</createdate> <keyword>toast</Keyword><keyword>breakfast </keyword><keyword>cooking</keyword> A downloadable XML reader would be available that anyone could use to enter this XML file into, and could read the file.

  6. A Model Database An organization (like ADL) could request these files from modelers who have models that are of interest to the group or oganization. These files would be cataloged according to short names. The database could save all of the metadata elements, or be selective in what they store. The database could then be queried according to specific elements of metadata, for example, a range of dates of creation, the model creator, the keywords, etc..

  7. Other Applications If this type of technology could be developed for model metadata, then metadata files for other topics could be created in the same way. This would bring down the cost of metadata creation and transfer, which would promote more complete metadata creation and collection. Easier is cheaper, and cheaper is better for everyone!

More Related