Skip to content
This repository has been archived by the owner on Jan 25, 2018. It is now read-only.

Where should we be maintaining the XSL's were using? #43

Closed
mejackreed opened this issue Feb 25, 2015 · 4 comments
Closed

Where should we be maintaining the XSL's were using? #43

mejackreed opened this issue Feb 25, 2015 · 4 comments
Labels

Comments

@mejackreed
Copy link
Member

Currently xsl's are being used now in GeoCombine. Where should we maintain these long term?

@drh-stanford
Copy link

We can gem-ify geoblacklight-schema to make it more shareable if needed. The gis-robot-suite also uses the XSLTs via a git submodule.

The XSLTs that convert to/from geoblacklight could stay here long-term. OpenGeoMetadata is probably better for schema conversion XSLTs, maybe in a new repo explicitly for metadata/schema conversion. I dunno whether the OGP metadata WG has a github repo for metadata tools. It'd be nice to have a specific repo that others can use just to get the converters without needing other software to use them. People use all sorts of different software for XSLT conversions.

@mejackreed
Copy link
Member Author

One concern I have about gemification, is what are we actually gemifying? A collection of shell and ruby scripts and xslt's? The schema validation used for geoblacklight-schema? How do all of these relate to eachother, and how do we semantically version it, test it?

@drh-stanford
Copy link

Yeah, that's why I've just been using git submodules. There isn't a Ruby API.

@drh-stanford
Copy link

Tracking in #70

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants