Re: [LAD] LV2 port groups - Linux-audio-dev

18 Aug 2009

On Tue, 2009-08-18 at 07:53 +0000, Michael Chapman wrote:
...
  On Sunday 16 August 2009 7:17 pm, Jörn Nettingsmeier
wrote:
  michael, there are plans to implement the
ACN/SN3D scheme in the LV2
 plugin standard.          Excellent news!
  since it's based on rdf, the question is
whether it might feasible to
 use the URLs for each ACN on ambisonics.ch as unique identifiers (which
 would be quite elegant and point users right to the relevant
 documentation).          Sounds good.
  however, that would depend on whether you could
guarantee stability of
 said URL space.          Don't see any practical problem.
         Legalistically the Association will undoubtedly go through
 other officers over the years, but I cannot see any restraint on the
 present Council giving an irrevocable commitment for something that is
 manifestly in the interests of ambisonics.
         I am also (I hope we all are) committed to Tim Berners-Lee
 philosophy of not chopping and changing URLS (his great example is that
 info.cern.ch --to his regret-- became w3.org, without even a redirect ...
 and so the oldest web address in the universe disappeared).
 > a short excerpt of the preceding discussion is quoted
 > below. please maintain the cc: list when replying. 
Sounds good.

It's probably a mistake on my part to use your /documentation/ URIs as
the URIs for the concepts themselves anyway.  Stable URIs are still good
for all the usual reasons though.

...
   The stream
descriptions could use them as well if there were URIs such
 as:

 http://ambisonics.ch/standards/filetypes/h1v1

 instead of:

 http://ambisonics.ch/standards/filetypes/f

 None of my business, but if you are going HV, rather than HVP (which I
 don't think I would ...) then Malham Notation (e.gg: "f", "fh")
seems to
 me a lot easier ... 
Sorry, I meant h1p1.  Point being the current scheme doesn't really tie
in with the use of (H,V) notation elsewhere on the site, and doesn't
extend to higher orders very nicely.  Nitpicks, anyway.

...
  A redirect from http://.../h1v1 to http://.../f would
not be impossible.
 Would that be anyuse?

  or better,
http://ambisonics.ch/standards/streams/f if I can nitpick :)

 Likewise a redirect from http://.../filetypes/... to
 http://.../streams/.... though if we are nitpicking I prefer
 http://.../signal_sets/... ;-)>

 Not sure about the 'ethics' of littering the name space with redirects and
 welcome comments from anyone who has thought more about this than I have.
 Not least how does one redirect: presumably a 303 ("see other") is
 preferable to a 301 ("moved permanently")? But I've not done that many /
 thought that much about redirects in my life .... ;-)> 
Probably not worth changing.  Also, hyphens in URIs are prettier :)

...
  Please accept the gratuitous comments above as that.
Seems silly not to
 throw in my bits of experience at this early stage.
 The bottom line is though, that this is your project and we are willing to
 help as much as we can with whatever _you_ want. 
I'm just acting as RDF scribe, really.  I defer to you folks who
actually know a lot about ambisonics completely.  Aside from a very
helpful ambisonics for dummies sort of intro from Fons, I'm clueless :)

Thanks,

-dr