Re: Finding Metadata for CSV Files

I would argue that approach (5) would be attractive for those outside of
the linked-data world that are nonetheless consumers of CSV data and often
in some document transfer protocol (queuing systems, ftps, files produced
by upstream systems then deposited on fileshares, etc).

Those sorts of systems would typically not use URIs within their toolsets,
hence a simple naming convention would be a simple approach for finding
associated annotations.

It's perhaps too simplistic for general use but robust enough to be adopted
by those who are less linked-data centric.
On Mar 9, 2014 4:07 PM, "Jeni Tennison" <jeni@jenitennison.com> wrote:

> From: Andy Seaborne andy@apache.org Date: 9 March 2014 at 10:33:57:
> > 5. (no advocacy) Naming convention : if there is a "data.csv" then the
> > metadata is adjacent under "data.csv.json" or somesuch.
> >
> > Similar to a Simple Data Format bundle but in an unpacked form (DSF has
> > "datapackage.json" for a whole bundle).
> >
> > The downside with this is that files become separated and the
> > association is lost.
>
> Yes, that would be an alternative, but I don't think we should include it
> as an approach in a Recommendation. It runs counter to the arguments in
>
>   http://tools.ietf.org/html/draft-ietf-appsawg-uri-get-off-my-lawn-01
>
> that caution against a protocol that specifies a particular URL path.
>
> Cheers,
>
> Jeni
> --
> Jeni Tennison
> http://www.jenitennison.com/
>
>