Hey RDFers!
It is essential for regular users and site owners to be able to swich of the 'RDF tab' which is shown as a default (!) on every node -- see attachment, please!

As it is now, the only way to get rid of this is to either hack the module itself or switch it off.

Please, please, please ... ;)

CommentFileSizeAuthor
#21 1089442-remove-rdf-tab.patch614 byteslinclark
#14 1089442-settings-page.png46.73 KBmilesw
#14 1089442-14-optionalize-rdf-tab.patch4.24 KBmilesw
#13 1089442-13-optionalize-rdf-tab.patch4.24 KBmilesw
#7 1089442-7-rdf-tab-permissions.patch3.55 KBmilesw
#4 1089442-rdf-tab-permissions.patch1.76 KBlinclark
rdf_tab__phi_2011-03-11T18-17.png88.31 KBBlooniverse

Comments

Blooniverse’s picture

Blooniverse commented

... I am referring to the version from '2011-Mar-11', btw.

Blooniverse’s picture

Blooniverse commented

... I am aware, btw, that the modification of 'page.php.tpl' with <?php if ($tabs && $logged_in): ?> (e.g. Bartik: on line 196) gets rid of this occurence. But generally this modification is not necessary -- RDF seems to be the only module which doesn't differentiate between authenticated and non-authenticated users. Thanks for noticing this! RDF is a great piece of work!!!

scor’s picture

scor commented

That's a good feature request. It's there because it makes it easy to show that there is an RDF output available, but there could be an option to turn this tab off. patches welcome.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Needs review
StatusFileSize
new 1089442-rdf-tab-permissions.patch1.76 KB

It sounds from your description that just being able to turn off the RDF tab for anonymous users would be fine... that you don't need node-by-node options.

If this is the case, then this patch should fix the problem. It adds a permission for accessing RDF content. You can grant this to different roles, so only those people will see the tab.

Anonymous’s picture

Anonymous (not verified) commented

Updated some language in hook_permission in the patch.

milesw’s picture

milesw commented

@linclark: I wonder if two separate permissions would be better. One permission could be used to allow roles to administer RDF settings. The other permission could simply be used to control access to the RDF version of content, just like you're doing in #4 patch. Perhaps "administer rdf settings" and "access rdf content"? What do you think?

milesw’s picture

milesw commented
StatusFileSize
new 1089442-7-rdf-tab-permissions.patch3.55 KB

This patch builds on #4, adding another permission.

The two permissions are:
- Administer RDF settings
"Configure RDF publishing settings, including namespaces used by the site."
- Access RDF content
"View RDF versions of site content."

The first one is used for admin pages, the second is simply for viewing serialized RDF.

It still doesn't feel quite right. It seems like the RDF representation should be accessible (with the right permissions) without making it a local task. Maybe including it as a local task should be an option?

Anonymous’s picture

Anonymous (not verified) commented

This also gets to a bigger question.... can we turn off RDFa-output based on permissioning as well. I think if people see a permission called Access RDF, they will think it can permission RDFa as well.

How to permission RDFa is actually a question we've been getting a lot at Drupal events, and I think it's something people want. It will also probably be more necessary with some of the stuff I'm planning for SPARQL Views. Basically, you'll be able to visit a site and get a JSON string that has the content type schema with fields and RDF mappings. Then you can take that JSON and import it on your site as a SPARQL Views resource. This will mean that if Joe has a Person content type on his site, Jane will be able to query it with SPARQL Views just by copying the JSON from Joe's site and pasting it into her site.

I think this has the chance to be extremely useful for many people because it will make getting content from other sites much easier... but it will also be super scary for others. We need to give them the option of restricting RDFa output while still having access to the RDF mapping API for anything else they need.

I'm making my head spin in circles just thinking about the permutations of permission and config options on this... I'll think about it more later.

milesw’s picture

milesw commented

Hmm, I can imagine people getting confusing about RDF vs. RDFa. The description for the permission could mention something along the lines of "This does not affect RDFa output in pages."

Do you think it makes sense to start with the two permissions in #7? I assume a permission for RDFa isn't as simple as adding a hook_permission() and some elements to hook_menu(). ;)

I think my patch in #7 might be bad. Will test it again later.

Anonymous’s picture

Anonymous (not verified) commented

Ok, so I think that there should be a configuration option to turn on RDF/XML. I do not think this should be on by default, but that the user should have to turn on RDF/XML. Most people will not want these tabs, so I think that is a sensible default.

I think that it makes sense to also allow configuration of visibility by role. I think this configuration should take the place of permissions because permissions imply that access has been restricted to content when in this case the access isn't restricted (since RDF is still available in RDFa). This also means one less permission to add to the hella-confusing permissions page.

Any thoughts? If folks agree, I think we should be able to get this one committed soon.

milesw’s picture

milesw commented

I agree with the first part, but I'm wary about managing permissions for something outside the standard permissions page. It seems like this would add unnecessary complexity. For example, you would have to require users to have "Administer Permissions" to even access the configuration page containing these options.

What about "View content as RDFa" and "View content as RDF/XML" on the permissions page? Obviously the RDFa one would take quite a bit of effort.

Anonymous’s picture

Anonymous (not verified) commented

Ok, I broke out the permissions issue into #1128700: Add permissions for RDF content.

I think that in the short term for this issue, we could just add the configuration to turn RDF/XML tabs on or off.

I think this may be a new configuration page in the RDF publishing settings config section. I'm guessing that we will have other config options that make sense to go with this one eventually. This may make sense to be our MENU_DEFAULT_LOCAL_TASK page?

milesw’s picture

milesw commented
StatusFileSize
new 1089442-13-optionalize-rdf-tab.patch4.24 KB

Hard to say at this point whether it's appropriate for the miscellaneous settings to be MENU_DEFAULT_LOCAL_TASK. It depends on what kind of config options end up there. For now, let's go ahead and try it that way.

This patch adds a settings page as the default local task for "RDF publishing settings". The only setting on there is an option to turn on/off RDF tabs for User and Node. If the tab is turned off, the RDF/XML version is still accessible.

milesw’s picture

milesw commented
StatusFileSize
new 1089442-14-optionalize-rdf-tab.patch4.24 KB
new 1089442-settings-page.png46.73 KB

Tweaked wording in form description, adding a screenshot.

scor’s picture

scor commented

The RDF tab should eventually die, in favor of optional links for each serialization formats, see #781972: Use RestWS for non-RDFa serializations and content negotiation in Drupal 7.

scor’s picture

scor commented
Project: Resource Description Framework (RDF) » RDF Extensions
scor’s picture

scor commented

I suggest to drop this issue in favor of #1171030: Advertise the various formats supported by RestWS. (and remove the current RDF menu item of course)

Anonymous’s picture

Anonymous (not verified) commented
Title: UX: Optionalize RDF tab per node (via admin_settings) » Remove the RDF tab

I agree, changing issue title to reflect. We can remove the tab without removing the page for now.

scor’s picture

scor commented
Issue tags: +Novice

easy patch...

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Needs work

Back to needs work since it only needs the change in comment #17-18

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Needs review
StatusFileSize
new 1089442-remove-rdf-tab.patch614 bytes

This patch simply removes the tags. The menu item itself will be removed as a part of #781972: Use RestWS for non-RDFa serializations and content negotiation in Drupal 7

scor’s picture

scor commented
Status: Needs review » Fixed

Good bye RDF tab! 2b64aeb

Status: Fixed » Closed (fixed)
Issue tags: -Novice

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +Novice

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.