Re: Rules.CSV format as alternative to htaccess

Hi Stian,

2016-03-03 12:09 GMT+01:00 Stian Soiland-Reyes <
soiland-reyes@cs.manchester.ac.uk>:

> I changed the wiki to be public, so it should be possible to change it now.
>
> About notable owners, I think this should be handled in the existing
> README.md way.
>
>
> One thing that comes up when I'm looking at the purl.org redirections
> is that there's often the with and without slash variants.. e.g.
> http://purl.org/pav and http://purl.org/pav/hasVersion -- it would be
> good if these could be represented within /pav/rules.csv  rather than
> also have a line in /rules.csv  -- perhaps the special values should
> be empty string for "folder" and "." for "folder/".
>
This would correspond to the recipe 4:
https://www.w3.org/TR/swbp-vocab-pub/#recipe4, and i think it would be
great if we could handle them in the rules.csv file as well!
Best,
Daniel

>
> As for the existing w3id.org htaccess rules, I think any non-slash
> folder usage now is indirect through Apache's own directory matching,
> e.g. https://w3id.org/bundle works as it should by a 301 Moved
> Permanently to https://w3id.org/bundle/ which then does 302 Found to
> its final destination.
>
> On 1 March 2016 at 16:55, Daniel Garijo <dgarijo@fi.upm.es> wrote:
> > Hi Stian,
> > I like it a lot! Definitely more simple than having to create the
> htaccess
> > by hand.
> > I also think that the media type is a very interesting question, as
> > sometimes I have done ORs in the rewrite conditions.
> > Regarding an owner for each rewrite rule, I think it's too much. In most
> of
> > the cases a single owner will edit most of the htaccess (except in repos
> > like /people). And you can see the edits through the commits, right?
> > I have tried to edit the wiki to fix a typo, but I don't have
> permission. I
> > will try with a pull request.
> > Best,
> > Daniel
> >
> > 2016-03-01 17:35 GMT+01:00 Ian Dunlop <ianwdunlop@gmail.com>:
> >>
> >> 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!
> >>
> >>
> >
>
>
>
> --
> Stian Soiland-Reyes, eScience Lab
> School of Computer Science
> The University of Manchester
> http://soiland-reyes.com/stian/work/
> http://orcid.org/0000-0001-9842-9718
>
>