Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Commit 5fff01a

Browse files
committed
clarified Use Case F to remove RDF-A and XML references
1 parent cf59ebd commit 5fff01a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

metadata-resources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,9 @@ E) Manual translating a data file from another system
6464

6565
Agencies may also manage their data catalogs through various database solutions such as Access, an asset management system, document management system, geoportal, or assorted proprietary systems. Regardless of which system an agency employs, it should include a fundamental export option which allows the catalog to be exported as a CSV file, which can then be imported into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/) for conversation to an appropriately formatted JSON file. Depending on the solutions' varied further functionality, some of them may also provide APIs which can then be configured to maintain the data.json file. If not, they may instead support XML and JSON exports, which can then be converted to the proper format.
6666

67-
F) Convert from CSV or JSON to XML or RDFa lite.
67+
F) Convert from CSV to JSON.
6868

69-
In order to generate appropriately formatted XML or RDFa Lite files, simply import an appropriately formatted CSV or JSON file into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/), ensure that the metadata fields line up, and re-export the file.
69+
In order to generate appropriately formatted JSON, simply import an appropriately formatted CSV into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/), ensure that the metadata fields line up, and re-export the file.
7070

7171

7272

0 commit comments

Comments
 (0)