#250: Improve contributor RDF
-------------------------+--------------------------------------------------
Reporter: earle | Owner: Nobody
Type: enhancement | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: trivial | Keywords:
-------------------------+--------------------------------------------------
At present:
{{{
<dc:contributor>
<foaf:Person rdf:ID="Name">
<foaf:nick>Name</foaf:nick>
</foaf:Person>
</dc:contributor>
}}}
Better:
{{{
<dc:contributor
rdf:about="http://openguides.example.org/wiki.cgi?id=Name;format=rdf" />
}}}
As the current design of the system (no specific user profile pages)
stands, the output will be faintly semantically odd as it will imply that
each person is a dc:contributor to themselves. But, I suppose there's some
philosophical truth to that, and it's still better than the current
output.
#248 will allow further improvement to:
{{{
<dc:contributor rdf:about="http://openguides.example.org/page/Name" />
}}}
And if user profiles are ever implemented,
{{{
<dc:contributor rdf:about="http://openguides.example.org/user/Name" />
}}}
which, with Content-Type negotiation, is the optimal case.
--
Ticket URL: <http://dev.openguides.org/ticket/250>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#36: Separate out installation of the OpenGuides software from installing a
guide
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: Nobody
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: 0.51
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by bob):
All Build.Pl should say is that the user needs to run a separate script to
create a guide.
This will help with automatic testing.
the script that should probably ask the same questions as build.pl does
currently.
or take cli options.
It should also probably create the database.
I think all tests just use sqlite now in a local db this negates some of
the concerns above. these days openguides mostly relies on wiki::toolkit
to have tested your db connectivity .
--
Ticket URL: <http://dev.openguides.org/ticket/36#comment:8>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#36: Separate out installation of the OpenGuides software from installing a
guide
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: Nobody
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: 0.51
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by perigrin):
Having talked about this (again) with Bob and Earl on IRC. I'd like to
have a completely seperate create-openguide script or some such that
Build.pl could just call when it was done installing stuff. (I don't know
the intricacies of Build.pl but I do think I could figure it out using
Module::Install if you'd be willing to accept a patch large enough to
include changing the Build process).
This would as an added benefit leave a script lying about for those of us
who host multiple guides so that we could just run create-openguide to
build new guide installs.
--
Ticket URL: <http://dev.openguides.org/ticket/36#comment:7>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project