Meaning of HTML prefix attribute (Open Graph Protocol)?
HtmlFacebookValidationFacebook OpengraphHtml Problem Overview
I'm new to Facebook Open Graph Protocol. I have been trying to figure out what the meaning of the HTML prefix attribute is. The closest post on Stack Overflow I could find dealing with this subject is this post which was very helpful as it deals with what the differences are among the various possible syntaxes and which one to use.
However the post does not say anything about what this prefix attribute is or what it does. AFAIK this is not a standard HTML attribute. I was able to find this document which I think is where the W3C defines this attribute but was not able to make any sense of it.
Could someone please explain to me:
-
What does the
prefixattribute do? -
Can I write
`<html prefix="og:http://ogp.me/ns#">`
instead of
`<html prefix="og: http://ogp.me/ns#">`
or would that be a syntax error?
- Can I include multiple
prefixattributes for any given HTML tag?
`<head prefix="a: http://www.aaa.com/ns#" prefix="b: http://www.bbb.com/ns#">`
Based on my knowledge of HTML, this would be wrong, but then `prefix` is a nonstandard attribute. So perhaps, what I would like to know is, can I write:
`<head prefix="a: http://www.aaa.com/ns# b: http://www.bbb.com/ns#">`
or does specifying multiple prefixes at any place in the HTML tree not make sense for some reason?
4. If this prefix tag is not part of the HTML spec, how would submitting a page containing this attribute to a code validator ever result in my code being standards compliant?
Thank you for answering my questions.
Html Solutions
Solution 1 - Html
First:
prefix is one of the attributes defined by the RDFa (Resource Description Framework in Attributes) extension. RDFa is used to implement the Semantic Web in web pages represented in many markup languages, like HTML and XML. Instead of having a web page telling the browser just how it should be structured, now you can also tell it what the page represents, like a Person, a List of Products, etc.
And for you to be able to semantically represent data on your web page, you need to use a semantic vocabulary, which tells the browser exactly that: what's being represented in your page. A popular semantic vocabulary is schema.org.
But sometimes a singular semantic vocabulary cannot represent and describe all of your web page. That's where the prefix attribute comes in:
> What does the prefix attribute do?
The prefix attribute allows you to specify one or more semantic vocabularies being used. The following example uses two vocabularies to represent a Person that has a favorite Animal: schema.org and vocab.org.
<p vocab="http://schema.org/" prefix="ov: http://open.vocab.org/terms/" resource="#manu" typeof="Person">
My name is <span property="name">MY_NAME</span>
and my telephone is <span property="telephone">MY_TELEPHONE</span>.
My favorite animal is the <span property="ov:preferredAnimal">FAVORITE_ANIMAL</span>.
</p>
> Can I write <html prefix="og:http://ogp.me/ns#"> instead of <html prefix="og: http://ogp.me/ns#"> or would that be a syntax error?
Besides from not being able to find any examples on the web using the former syntax, from the specification of the RDFa Core you can see that at least one space is indeed mandatory:
prefix
a white space separated list of prefix-name IRI pairs of the form
NCName ':' ' '+ xsd:anyURI
> Can I include multiple prefix attributes for any given HTML tag?
Yes, you can. From the specification of the prefix attribute given above, and from lots of examples given on the specification of the RDFa Core, the following is allowed:
<html
prefix="foaf: http://xmlns.com/foaf/0.1/
dc: http://purl.org/dc/terms/"
>
<!-- your page -->
</html>
> If this prefix tag is not part of the HTML spec, how would submitting a page containing this attribute to a code validator ever result in my code being standards compliant?
As mentioned by @wensveen, HTML5 supports the RDFa attributes out-of-the-box.
Solution 2 - Html
It appears the prefix attribute is indeed defined in the RDFa specification you linked. While you need to specify the correct media type for XHTML documents (application/xhtml+xml) and the correct doctype (<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">) and probably some more XML push-ups, this isn't necessary for HTML5.
In HTML5 you can use the RDFa-defined attributes out-of-the-box.
See: HTML+RDFa 1.1 specification
I don't know if there are any specific advantages of this way of mapping a prefix to a namespace. It isn't entirely clear to me either.