ude-pattern was developed was
> to NOT to have to repeat such text in the content of the document.
>
> Thus I've changed it to use the 'title' attribute instead, which is
> simultaneously a less invasive / content-affecting requirement on the
> author, and still available to
Angus McIntyre wrote:
On Thu, December 13, 2007 12:44 pm, Robert O'Rourke wrote:
Perhaps in the case of a podcast or video blog you could tell your
feed-reader what format you prefer and it would grab the right file.
That's one possibility but I don't know of anyone who does
podcasts/video bl
thing, it's likely in the context
of the microformats principals. Someone saying ‘no’ cannot be backed
up only by their reputation and stature. ‘Citation needed’, is perhaps
the most succinct requirement.
The most worrying thing about this message is that anyone should
perceive the direct
outside of those systems. In
particular, it may be useful to track an object's identifier for later
reference, citation, disambiguation, or service resolution.
Unfortunately, although there are many standards for obtaining or
specifying identifiers themselves, there is no common practice fo
Brian is correct.
In addition, semantically the "author" isn't just a *name*, the author is a
*person*, and the microformat for a person is hCard. That's why we are
using hCard there.
If however, you wanted to reuse "fn" for the name of the work being cited, I
could see a case being made for ex
On 8/16/06, Bruce D'Arcus <[EMAIL PROTECTED]> wrote:
On 8/16/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
> I tried my imagination on one of my straw examples. Does this fit what
> you were expecting?
In general, yes, though I'm not that comfortable commenting on the
details of microfomrat
Hi Jeff,
Alternates was an exploration of a particular pattern that really
hasn't been picked up yet by a uF that's made it all the way through
the process, though I believe will be of some utility in the future --
i.e. kind of the situation we are having with hItem.
I'm not sure what direct util
ications and actively encourages inclusion of inner text in
> hyperlinks.
I've added RFC2119 language (should) to that section, and noted that a
citation is required for the assistive technology implication assertion.
Far too often (in this forum and other forums) I have seen accessibility
ummarize. In this case, I think hcalendar in the context of
> the hcard makes sense (perhaps a combination of both). In other cases
> (as in, "Einstein, deceased: 1955, Franklin, deceased: 1790"), you'd
> want to use 'dday' and leave out the hcal stuff. These are
On 3/29/06, Ross Singer <[EMAIL PROTECTED]> wrote:
> But the real point of my reply is not about perceived biases, it's about the
> misconception that OpenURL is key value pairs. That is one representation
> of OpenURL, but the community profile for journals also has an XML
> incarnation:
> http:
On 8/16/06, Tantek Çelik <[EMAIL PROTECTED]> wrote:
On 8/16/06 5:50 PM, "Bruce D'Arcus" <[EMAIL PROTECTED]> wrote:
> On 8/16/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
>
>> I tried my imagination on one of my straw examples. Does this fit what
>> you were expecting?
>
> In general, yes, th
look at hListing: http://microformats.org/wiki/hlisting-
proposal
and Citations: http://microformats.org/wiki/citation
-brian
Adam Craven - Four Shapes wrote:
Retail is a huge area. Products are listed everywhere and the data is
untamed and lacks cohesion.
The proposal is here to gauge
s for the correction, Bruce! So, if I'm thinking about this
correctly, and using ideas from measures-brainstorming[1], hCard, and
citation formats, the markup for a painting [2] would be:
Gilbert Stuart
American,
1755 - title="18280709" clas
7;t already
provided in the examples listed?
I suggest looking at the other *-examples pages, in particular
<http://microformats.org/wiki/review-examples> and
<http://microformats.org/wiki/citation-examples>. Please take careful
note of the analysis sections and implied schema sections
rm implementation, and then if we ask them to add
>*another* name for microformats purposes.
Ah, if that's still something that needs to be considered in the
autocomplete case then that makes sense.
>> (whereas name would make good
>> autocomplete work).
>
>Citatio
On 9/22/06, Bruce D'Arcus <[EMAIL PROTECTED]> wrote:
On 9/21/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
> I think the ROLE attribute of vcard means something different than
> what you guys were describing with a role.
>
> You were saying role = "what this person's relationship to the cited
Tantek
There is one part the hResume format that is a bit less than eloquent for CVs.
That is the citations section of a CV. there was a micro format discussion for
hCite but this discussion was not brought into hResume. hResume does mark up
citations but not with as much detail as say CoinS
ks for URIs that normally have
>>>>> browser protocol handlers (http:, mailto:), but not so well for
>>>>> other URIs (urn:, info:, etc) - which are particularly important
>>>>> in the context of a citation microformat.
>>>>
>>>> Um
stification to make it more complex. When I wrote xFolk, my
intention was to have a format that would allow tagged links to be
harvested, not so much to display lists of the links that were thus
harvested with proper citation back to the linker and reference to a
harvest date.
--- if that was t
ts of the links that were thus
harvested with proper citation back to the linker and reference to
a harvest date. That's great because people get what it's for
without too much trouble, and as a result they don't have too much
trouble implementing.
One thing I find usefu
On 10/6/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
Brian, I'm attempting to try your X2C service but I'm getting errors
and I'm having trouble pinning down what's going wrong.
I'll take a look at the XSL but if I could put a request in for some
user-visible error reporting that'd help thin
text text text text
This is not well-formed, but very common.
That said, there is a citation format in the works[2], this will allow
for the ability to cite page, etc. Bible chapter, paragraph, verse were
not in the original idea, but could make there way in depending on other
formats.
Have you
d be useful for that. I
>suppose that then demonstrates that there may be still some utility in
>having an hCard for someone who passed away, if their hCard uses AGENT to
>indicate who to contact regarding any personal matters.
>
>
>> So, to summarize. In this case, I think hca
t should be
>> dismissed as far
>> as microformats are concerned.
>
> A large portion of what is published on the web references things
> that don't exist on the web, and thus don't have a canonical URL.
Right, and to resolve whether it is a "large portion"
p://microformats.org/wiki/hlisting-proposal
and Citations: http://microformats.org/wiki/citation
-brian
Adam Craven - Four Shapes wrote:
> Retail is a huge area. Products are listed everywhere and the data is
> untamed and lacks cohesion.
>
> The proposal is here to gauge interest in dev
On 10/6/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
On 10/6/06, Michael McCracken <[EMAIL PROTECTED]> wrote:
> Brian, I'm attempting to try your X2C service but I'm getting errors
> and I'm having trouble pinning down what's going wrong.
>
> I'll take a look at the XSL but if I could put a r
by science. I understand that. I'm specifically talking
>about the structure of markup.
What do you mean by "the structure of the markup"?
>> What analysis would you like?
>[...]
>> What do you mean by "common publishing behaviours", that isn't already
&g
On 26 Jan 2008, at 19:07, Andy Mabbett wrote:
In message <0F667B0C-8A0D-4345-AF3B-
[EMAIL PROTECTED]>, Jim O'Donnell
<[EMAIL PROTECTED]> writes
letter-to-author is the relationship I'm really interested in
That sounds like a situation where you would use th
a URL, so it wouldn't
necessarily be a URI. Allowing both an ISBN uid and a "via" link
allows
parsers that aware of ISBN to do smart things (such as link to
Amazon if
they wish) /or/ follow the "via" tag for the author's source
reference.
I'm not sure how t
I think Jeremy is absolutely right. Genealogy data can already be semantically
marked up with existing
microformats. Don't forget to include the Citation microformat for
genealogical sources.
Also, it is important to keep the one-to-one mapping of the VCARD standard to
hCard.
This seems to be a citation issue... since we need to be able to cite
the author of a theme, just like you use blockquote to cite the
creator of a photo or piece of text.
Scoping becomes an issue quickly, as rel="designer" could apply to a
local widget in the sidebar or to the en
nearly completely with existing or in-progress microformats, mostly tags.
If there is a need to provide more detail than just tags, there are other
microformats in progress: e.g. for "books I like", that seems perfect for a
citation microformat. Or perhaps for books, movies, music e
ets would probably work fine.
In fact, filtering is so well supported on my mail client that I've already
divided the main
microformats list into "Citation", "Currency", "geo", "Species" and
"Genealogy". My filters
take care of parsing the messa
he main reason i brought this up, was because several months ago
Tantek took part in the Wordpress IRC meetup and found it very
helpful. I too have held IRC meetups for hCalendar and the citation
microformats and much was accomplished. Some of the people who took
part came specifically for the meetu
>and
>> places
>Reference strings, in TEI markup at least, can also refer to the names
>of books, ships, plays, films and pretty much anything that can be
>given a name. hCard works for people and places, but is it general
>enough to cover those cases?
I think ships a
important than another, and if that were ever to be the case, the community
> and the effort of microformats generally will suffer greatly.
>
> When someone says you 'can't' do something, it's likely in the context of
> the microformats principals. Someone saying 'no&
e and places, but is it general
>enough to cover those cases?
I think ships are an edge-case for hCard.
For books, plays and films, I would think that's a job for a "citation"
microformat, once we have one (and one is surely needed).
[One could argue that a physical copy of a book could
s via+via self more constraining? You can do everything you can with
uid+url, but you don't have to use URLs for your UIDs.
I do see the value in not adding to hCard. I've argued elsewhere against the
arbitrariness with which "places" became suitable
entities for hCard
er greatly.
>>
>> When someone says you 'can't' do something, it's likely in the context of
>> the microformats principals. Someone saying 'no' cannot be backed up only by
>> their reputation and stature. 'Citation needed', is perhaps the mos
gt;recommendation of microformats to "class" and "rel", rather than
>>forcing authors to pick one value for "name".
>
> While this seems somewhat reasonable, as suggested on the wiki page we are
> discussin there are still 2 problems with the suggested use of
oformats Light that enables most of the functionality that most of
the people are looking for.
In the last 5 days I've seen these microformats proposed:
Bookmark Exchange Format
Attention Microformat
Citation Format
MicroId
Plants Format
Work of Art
Conversation
Following this list you see thes
s most of the functionality that most of
the people are looking for.
In the last 5 days I've seen these microformats proposed:
Bookmark Exchange Format
Attention Microformat
Citation Format
MicroId
Plants Format
Work of Art
Conversation
Following this list you see these requests all the time. This
king for.
We already have 'microformats light,' its called 'semantic markup.'
Semantic markup has been an option longer than microformats have.
In the last 5 days I've seen these microformats proposed:
Bookmark Exchange Format
Attention Microformat
Citation Format
M
as link to
Amazon if
they wish) /or/ follow the "via" tag for the author's source
reference.
I'm not sure how this is relevant. We're talking about hCard here,
not a citation format.
That's valid. I ended up being more general in that example than
necessary for the
ocabularies.
>>> Do grandfathered rel/rev values count? &c.
>>
>> rel/rev syntax and values work without RDFa - they're not RDFa,
>> despite RDFa's attempt to subsume them (and even errantly claim/imply
>> credit in the spec, e.g. rel-license).
>
&
gt; example, is more likely an ISBN rather than a URL, so it wouldn't
> > necessarily be a URI. Allowing both an ISBN uid and a "via" link
> > allows
> > parsers that aware of ISBN to do smart things (such as link to
> > Amazon if
> > they wish) /or/
601 - 646 of 646 matches
Mail list logo
