Re: Rules.CSV format as alternative to htaccess

Hello,

That's a great start Stian. I assume that the "example.com" example is
predicated on the csv file being present in a top level folder called
"example" in the github repo (which the page does hint at - I'm just trying
to understand how it all works). Can there be more than one media-type for
a redirect? The examples only show one for each row.
Does each redirect rule need an owner - should we add a column for email
addresses to contact in case of issues?

Cheers,

Ian

On 1 March 2016 at 11:44, Stian Soiland-Reyes <
soiland-reyes@cs.manchester.ac.uk> wrote:

> So here is my suggestion for rules.csv format and mechanism:
>
> https://github.com/stain/w3id-csv/wiki/rules.csv-format
>
> In short, a CSV file (which you can edit in your favourite spreadsheet
> editor) could be used to auto generate corresponding .htaccess (of
> everything is in order) in a w3id folder.
>
> I added an optional column for content negotiatation. i think this could
> cover 90% of existing .htaccess files (although they would not need to
> "upgrade")
>
> Then for purl.org transitions we can simply generate there rules.csv
> files.
>
> Ideas? Suggestions? Feel free to edit in the wiki as well!
>