Re: Call for maintainers - Musicbrainz RDFa markup

By the way, the easiest way to work with the server is to use the VM but
this hadn't been updated since last year. I have an up-to-date version for
the Summer School and I'll bring it into the Museum next week.

(Incidentally, there's an implicit announcement for the two lists: I work
as Development Manager at the British Museum now, hence the change in
address)

Barry


On Thu, Sep 5, 2013 at 1:04 PM, Yves Raimond <yves.raimond@gmail.com> wrote:

> On Thu, Sep 5, 2013 at 12:41 PM, Barry Norton <barrynorton@gmail.com>
> wrote:
> > Perl with Catalyst and Template Toolkit
> >
> > http://musicbrainz.org/doc/MusicBrainz_Server
>
> The code is here:
>
> https://github.com/metabrainz/musicbrainz-server
>
> I think most of the work will be in the templates themselves.
>
> Best,
> y
>
> >
> >
> > On Thu, Sep 5, 2013 at 12:33 PM, Joshan Mahmud <joshan.mahmud@gmail.com>
> > wrote:
> >>
> >> Hi all
> >>
> >> Could I ask the question of what the code base is written in?
> >>
> >> Cheers
> >> Josh
> >>
> >>
> >> On Thu, Sep 5, 2013 at 10:32 AM, Alexandre Passant <alex@seevl.net>
> wrote:
> >>>
> >>> Hey
> >>>
> >>>
> >>> On Thu, Sep 5, 2013 at 10:28 AM, Barry Norton <barrynorton@gmail.com>
> >>> wrote:
> >>>>
> >>>> Yves, thanks for this call-to-arms: one I also just made yesterday at
> >>>> the ESWC Summer School, where we're busy this week with lots of
> music-based
> >>>> Linked Data teaching, including using the MusicBrainz R2RML mappings
> [1]
> >>>> that also owe their existence to the LinkedBrainz project.
> >>>>
> >>>> To be clear about the relationship, LinkedBrainz developed D2RQ
> mappings
> >>>> alongside the perl code to embed RDFa in the HTML generation process
> in the
> >>>> MusicBrainz codeset. Since then, as part of the EUCLID project, I have
> >>>> transitioned the mappings to the R2RML standard and found a couple of
> >>>> willing contributors. Unfortunately none of us feel qualified to keep
> the
> >>>> RDFa in sync.
> >>>
> >>>
> >>> I'm interested in maintaining the RDFa - as just posted on the MBZ
> blog,
> >>> pending I can grasp the codebase and the way mappings are generated in
> the
> >>> HTML.
> >>> What you're saying is that the way it should work is: MBZ schema change
> >>> => R2RML changes => RDFa change?
> >>>
> >>> Alex.
> >>>
> >>>
> >>>>
> >>>> One solution is to find someone who can, and come together to keep the
> >>>> two in sync (already through 3+ significant musicbrainz RDBMS schema
> changes
> >>>> since the LinkedBrainz project); another is (which would be very sad)
> to
> >>>> lose the RDFa and re-examine the decision whether separate
> RDF-resolvable
> >>>> resources could be provided at MB.org or elsewhere.
> >>>>
> >>>> Barry
> >>>>
> >>>> [1] github.com/LinkedBrainz/MusicBrainz-R2RML
> >>>>
> >>>>
> >>>> On Thu, Sep 5, 2013 at 8:55 AM, Yves Raimond <yves.raimond@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> Musicbrainz is a large music database and currently exposes a large
> >>>>> amount of data as RDFa, accounting for quite a big (and useful) part
> >>>>> of the Linked Data cloud. However they're lacking someone to maintain
> >>>>> it going forward, to adapt it to previous and upcoming schema
> changes:
> >>>>>
> >>>>>   http://blog.musicbrainz.org/2013/09/03/our-rdfa-dilemma/
> >>>>>
> >>>>> Please contact me (or the Musicbrainz development team directly) if
> >>>>> you'd like to take this on and make a significant contribution to the
> >>>>> Linked Data cloud :)
> >>>>>
> >>>>> Best,
> >>>>> Yves
> >>>>>
> >>>>> --
> >>>>> You received this message because you are subscribed to the Google
> >>>>> Groups "Music Ontology Specification Group" group.
> >>>>> To unsubscribe from this group and stop receiving emails from it,
> send
> >>>>> an email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> >>>>> To post to this group, send email to
> >>>>> music-ontology-specification-group@googlegroups.com.
> >>>>> Visit this group at
> >>>>> http://groups.google.com/group/music-ontology-specification-group.
> >>>>> For more options, visit https://groups.google.com/groups/opt_out.
> >>>>
> >>>>
> >>>> --
> >>>> You received this message because you are subscribed to the Google
> >>>> Groups "Music Ontology Specification Group" group.
> >>>> To unsubscribe from this group and stop receiving emails from it, send
> >>>> an email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> >>>> To post to this group, send email to
> >>>> music-ontology-specification-group@googlegroups.com.
> >>>> Visit this group at
> >>>> http://groups.google.com/group/music-ontology-specification-group.
> >>>> For more options, visit https://groups.google.com/groups/opt_out.
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Dr. Alexandre Passant - @terraces
> >>> Founder, CEO - http://seevl.net & http://mdg.io
> >>> http://facebook.com/seevl - http://twitter.com/seevl
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "Music Ontology Specification Group" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an
> >>> email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> >>> To post to this group, send email to
> >>> music-ontology-specification-group@googlegroups.com.
> >>> Visit this group at
> >>> http://groups.google.com/group/music-ontology-specification-group.
> >>> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Music Ontology Specification Group" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to
> music-ontology-specification-group+unsubscribe@googlegroups.com.
> >> To post to this group, send email to
> >> music-ontology-specification-group@googlegroups.com.
> >> Visit this group at
> >> http://groups.google.com/group/music-ontology-specification-group.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Music Ontology Specification Group" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to music-ontology-specification-group+unsubscribe@googlegroups.com
> .
> > To post to this group, send email to
> > music-ontology-specification-group@googlegroups.com.
> > Visit this group at
> > http://groups.google.com/group/music-ontology-specification-group.
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Music Ontology Specification Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to music-ontology-specification-group+unsubscribe@googlegroups.com.
> To post to this group, send email to
> music-ontology-specification-group@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/music-ontology-specification-group.
> For more options, visit https://groups.google.com/groups/opt_out.
>