I understand the majority of this topic and how to nest something like address vocabulary in person vocabulary.
but I'm wondering into more details for less straight forward pieces of info or "mixed up" info. Any Advice documentation is appreciated
So Couple Example Questions
1.) Is there no way to associate an email address that google understands? Maybe I missed this?
2.) Let's say John & Jane Sign the bottom of their Blog Together They both have the same site and affiliations, would using the name prop twice in one section of person be appropriate? would it associate that both John and Jane are two separate people both affiliations?
3.) Can more than one of any itemprop be used for example I have 3 affiliations and 3 titles, I don't want to write my name three times so i would use itemprop name and than title prop 3 separate times? furthermore how would i associate the title and role of the the three separate ones together?
4.) To take that farther what if Jane also had the Title of SEO where as John had the title of Music and Jane and John had the title of Web Development and both had the same URL how could more intertwined mark ups like this be represented without listing all the info for each person separately?
4.) Let's say you have an affiliation with company a and company b what would be the best method to also nest the business information for company a and company b ?
The Majority of my questions are along the same lines but I think nipping these or any documentation that covers scenarios similar to these would help clear up alot of confusion
I don't think most of this is possible with the current status of microdata. One way round it would be to add the info in another place (i.e. first person at the end of a post, then second person hidden at end of page), which semantically is stupid, but would allow naive parsing to pick up both cards.
As I say though, I don't think there is a neat way to do this in the page at the moment.
Related
So I'm writing an app where there's a HTML tag which should have all the ACM CCS tags/fields as options and basically users should be able to select one or more of these tags and assign them.
However how can I go about getting all the ACM CCS tags as strings in the first place, so I can create the element with the proper options in the first place?
Getting them manually isn't really an option as there are probably thousands of them by the looks of it.
Considering they're part of the academic culture I thought they'd already been extracted at some point by someone in a certain format and then shared somewhere but I couldn't find any such thing.
For reference, if you don't know what I'm talking about, I want all the names of all the CCS tags in no particular order from this site: https://dl.acm.org/ccs
So for example, in the end I wanna obtain such strings as "General and reference", "Hardware" , etc.
I've looked into web crawlers and the likes but I seriously have no clue how to even use one, let alone build one. As far as I've seen all these names are stored inside <li> tags so if I had something that'd "parse" the whole site with all its pages and then store the content of all the <li> tags it encounters as strings that would work.
By other words, must "author" refers the engineer or it means the customer?
the name of the document's author.
is all that said about it in Standard metadata names article of MDN.
You should specify yourself as the name of the author as it is will indicate the author of that HTML document.
In large projects it will be easier to track who wrote what. In away it will be easier to maintain and apply changes. If you specify customer as an author it will distinguish it from your other projects but not the files inside the project.
Suppose a team of three developers were assigned the task to develop a specific website each author will wrote his name as an author. So as to easily recognised.
If there was only one programmer and in future somebody else is assigned still it will be easy to know who was the original writer or at least how many people were involved in development of original website (front end)
It is a good practice to specify the developer's name in code. But the <meta name="author"> HTML element is NOT design for that purpose. It is intended to store the author of the "document", IE the author of the text present on that page.
For example on a blog post page it will store the author of the blog post.
In order to uniquely identify my model records in the django admin interface, I am joining the unicode of several fields in sequence. These become the links to select individual records to edit.
To improve readability I'd like to display them to appear as columns. So rather than...
Fred Flintstone 1985-06-11
Jim Bean 1999-03-02
Wolfgang Amadeus Mozart 1756-01-27
I want
Fred Flintstone 1985-06-11
Jim Bean 1999-03-02
Wolfgang Amadeus Mozart 1756-01-27
If I format my __unicode__ function return to have extra whitespace, Django will include it in the html but the browser collapses the whitespace. Is there a simple way to change the layout of these line items while keeping the admin? Maybe by somehow getting "pre" tags to be output - I'm not an html expert so I suspect that may not be legal inside the "a href", but maybe the text could be appended after the link, with a fixed link at the front something like
Select<pre>Fred Flintstone 1985-06-11</pre>
Select<pre>Jim Bean 1999-03-02</pre>
Apologies if that's bad html but hopefully you understand what I'm saying.
I realise I could do a template and my own view but the admin almost does what I need for a lot of the application apart from this formatting issue, and there will be quite a lot of different pages like this.
You want this instead: https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.list_display
Basically, you specify how to list your model items and this is used instead of calling __unicode__ on your model.
Can people explain what taxonomy means in terms of a web site?
My current understanding it a classification of the contents in relationship to each other, but it seems like it must go beyond that simplistic definition. and yes, I have read the wikipedia entry for this.
a way to categorize your content. One content could exist in multiple taxonomy categories. For example, Ronald Reagon could exist in the following categories: Presidents, Actors. You could have a site with content about Ronald Reagan. You could have category filters. Taxonomy would allow you to show the Reagan content for each category without having to duplicate the content.
Taxonomy tends to refer to a main navigational hierarchy - Stack Overflow's taxonomy for example would be the "Questions", "Tags", "Users", "Badges", and "Unanswered" links at the top of the page.
Taxonomy can mean many things though but for a website it tends to refer to the navigational hierarchy and organization of the site.
One of the sites I develop has lots of information linked between each other; we have companies, we have products for those companies. The company page links to the page listing the products for that company, and vice versa.
From the HTML spec:
CITE:
Contains a citation or a reference to other sources.
Does this imply that I could (semantically) use a <cite> for a company link? What about on the company page to a product?
If not, could someone tell me what might be the "correct" semantic tag for this?
If you're just linking to other pages then semantically you should just use <a href=...>. If you're quoting a small piece of information, like the information from the HTML spec in your question, and providing a link to the original source, you might use <cite>. Think of it as a citation in a book or research paper.
I'm not sure that cite is intended to mark up links - you may be looking at something akin to a more professional (less inter-personal) XFN using the rel attribute of the link.
Cite is more for marking up titles of articles or other created work.
XFN is specifically for marking up the relationship you (or your company) have with the person or company you are linking to. What I'm not sure of is what xfn values there are (if any) for company links.
http://reference.sitepoint.com/html/xfn
What you might consider is in what detail will the information be used? Semantic markup, although a noble direction to head in, is not yet utilised to it's full extent when looking at (by a human) or parsing (by a program) a resource.