[uf-discuss] Re: [hcite] nesting container elements

and the journal have a title. I actually brought this up in December in response to Brian's straw format[1], but the words I thought to use were "collection" or "in". I like "in" largely because some citation formats actually use that word to describe

Re: [uf-discuss] hCite progress

;Pages to indicate the length of a book should be beyond scope. It's >> >not relevant to citations. >> >> I disagree, not least because people often cite a whole book, rather >> than part of it. > >Which is exactly why the length of the book is irrelevant. No it isn&

Re: [uf-discuss] [citation]: Brian's outstanding issues 2:

ow, for example, that Tantek once said it's not generally good practice to double up classes ("hcite book") but I'd like some explanation about why. But I will say that in either case, one must allow for extensions. I've worked on this for a long time, and defining a fixed l

Re: [uf-discuss] Citation format straw proposal on the wiki

a isn't what is happening by the 80. Look at the > examples collected on the wiki, very little metadata if any. > (http://microformats.org/wiki/citation-examples -- look to the Implied > Schema section) Earlier in this thread I stated that many of these examples are exactly the o

Re: [uf-discuss] Easy book citations

t I mostly see it as distantly related to hCite. But I see citation metadata as a cycle. I want ulitmately to be able to output good uF metadata such that users can: - view a nicely formatted document in their browser, complete with proper citations - click some button and go to the original arti

[uf-discuss] Re: Microformats for scientific papers

getting a scholarly (not just scientific) article microformat would be hCite/citation microformat, and a metadata format (possibly related to Dublin Core??). For the most part, we're already there. (X)HTML already has structures in place for cross references, quotations, tables,

[uf-discuss] Re: Microformats for scientific papers

throughout. It seems to me that the main part of getting a scholarly (not just scientific) article microformat would be hCite/citation microformat, and a metadata format (possibly related to Dublin Core??). There is more than that, particularly when you want to include the actual data

Re: [uf-discuss] hCite progress

le often cite a whole book, rather than part of it. Which is exactly why the length of the book is irrelevant. The only time you include pages in a citation is if you are referring to a section within a book (typically a chapter), and the purpose there is simply to help you find it. Page count does

Re: [uf-discuss] hCite progress

On 11/13/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: But citation uFs are being recommended for more than pure academic citations - in resumes, for example, where the page count is likely to be far more relevant. I seriously doubt it. I certainly wouldn't include it (and don&

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Bruce D'Arcus <[EMAIL PROTECTED]> writes >> But citation uFs are being recommended for more than pure academic >> citations - in resumes, for example, where the page count is likely to >> be far more relevant. > >I seriousl

Re: [uf-discuss] hCite elevator pitch and my bibliography generator

Henri Sivonen wrote: Rephrasing: How would I need to change my markup to comply with what hCite is currently expected to be? If I do that now, will I pollute the space of future hCite data? As far as I'm aware, the architectural plans are still being drawn up for hCite. It is curr

Re: [uf-discuss] Easy book citations

ll most likely be met, as well (although not necessarily the reverse). Does this seem accurate? -Ross. On 7/30/06, Edward Summers <[EMAIL PROTECTED]> wrote: On Jul 30, 2006, at 2:08 PM, Tantek Çelik wrote: > What if we set a goal for hCite 0.1 of August 30? Is that reasonable? If Brian Suda

[uf-discuss] [hCite] dates

Looking at the examples on citation-examples, I find the following frequencies of marking up a date: publication date: 21 date accessed: 3 date copyrighted: 1 (from OCLC worldcat online) I just added date-accessed to the working straw schema. Certainly all three are useful, but can we find

Re: [uf-discuss] [hCite] dates

On 1/17/07, Joe Andrieu <[EMAIL PROTECTED]> wrote: Michael McCracken wrote: > Looking at the examples on citation-examples, I find the > following frequencies of marking up a date: > > publication date: 21 > date accessed: 3 > date copyrighted: 1 (from OCLC worldcat

Re: [uf-discuss] Citation: next steps?

ir work Interlocking Lives). So hCite should permit multiple creators, and use role for clarification purposes. And I totally agree that in many works there are primary and secondary creators. I like your proposal: Yeah, I was thinking that, though the general approach is to just use "con

Re: Re: [uf-discuss] Easy book citations

up with all the developments since our last major discussion. -brian On 7/30/06, Edward Summers <[EMAIL PROTECTED]> wrote: On Jul 30, 2006, at 2:08 PM, Tantek Çelik wrote: > What if we set a goal for hCite 0.1 of August 30? Is that reasonable? If Brian Suda has the spare cycles I think

Re: [uf-discuss] [hcite] date-published

Mike said: >From Bruce D'Arcus on the wiki: > >"I've mentioned more than once that "date-published" is misleadingly >specific; too much for real world citations. Consider that many books >are published in the year preceding their copyright date, which is

[uf-discuss] Re: Citation format straw proposal on the wiki

[EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of microformats-discuss digest..." Today's Topics: 1. Re: Citation format straw proposal on the wiki (Breton Slivka) 2. Re: seeking clarification w/r/to hCard and RF

Re: hCite Transformations Test (was Re: [uf-discuss] hCite progress)

Roy Rosenzweig > , > The Park and the People: A History of >Central Park. Presumably, that's because the author name is the first "fn" inside the "hcite". Why use "fn" and not "title"? --

Re: Re: [uf-discuss] Citation Microformat: LazyWeb for BibTeXperts

is no way that the conventions of BibTeX -- conventions which preceded the web-- ought to be in any way privileged in hCite. "Key" is one of these. They are indeed just identifiers. Within BibTeX, keys only need to be locally unique. For reference, I use URIs to achieve the same thing in

Re: RE: [uf-discuss] Citation Microformat: LazyWeb for BibTeXperts

s rule. Whether we call it "dtvalid" or "dtaccessed" doesn't matter that much. BTW, worth looking at Zotero, which has just gone live: <http://zotero.org> They'll be supporting hCite once it's done. Bruce ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss

'date accessed' in bibtex (was Re: [uf-discuss] hCite progress)

se it's more meaningful. -mike * meaning I'm not aware of any common style files that use it. There could be plenty that aren't common or I haven't seen... On 11/13/06, Brian Suda <[EMAIL PROTECTED]> wrote: Also, i have wiki-fied several citation examples from a pre

[uf-discuss] [hcite] nesting container elements

(note - I originally sent this to uf-dev accidentally. My impression is that more hcite people are on uf-discuss. Correct me if I'm wrong and we can move this to uf-dev. Thanks!) We need to deal with bibliographic details for things like chapters in a book, articles in a journal or magazine

Re: [uf-discuss] New new mailing list

On 2/7/07, Michael McCracken <[EMAIL PROTECTED]> wrote: So, is the microformats-new mailing list now the appropriate place for discussing hCite development? Thanks, -mike Good question. My personal opinion is that we should kind of grandfather older stuff, while encouraging newcomer

Re: [uf-discuss] [hCite] call for examples: language

is inferred from the @lang property of the hcite element? (And hence, drop the 'language' field from the hCite straw format?) --- i would agree, that removing the explicit "language" field from the straw format is a good idea. Maybe make a note that this IS a value, but is extra

Re: [uf-discuss] hCite progress

ring might not be useful is capturing a citation for a specific page of a work versus capturing a citation of a work in its entirety. Its one thing to cite a specific quote from page 40 of an article in a journal, and another to cite an entire article that exists on pages 37-65 in a journal.

Re: [uf-discuss] Citation format straw proposal on the wiki

; subjects/keywords, pricing, copyright, licensing, owner, format, > coverage, and audience, all of which are mapped in the > citation-formats. All the above is true except for format/media. While for standard texts this information is not relevant, for other sources it is. > (** to be

Re: [uf-discuss] New new mailing list

<[EMAIL PROTECTED]> wrote: On 2/7/07, Michael McCracken <[EMAIL PROTECTED]> wrote: > So, is the microformats-new mailing list now the appropriate place for > discussing hCite development? > > Thanks, > -mike Good question. My personal opinion is that we should kind

Re: [uf-discuss] [citation] Call for scope check (was Re: Citation: next steps?)

On 9/22/06, Ryan Cannon <[EMAIL PROTECTED]> wrote: They seem the closest thing to what we're looking for, i.e. BibTex could be to hCite what vCard is to hCard. Blithely creating our own format seems reckless and doomed to obscurity. I've certainly invested a lot of time and

Re: [uf-discuss] Citation format straw proposal on the wiki

Let me be clear, I do not care if OpenURL is used as an hCite format.  I do very much care that whatever is chosen is very easily translated to something OpenURL link resolvers can handle. Now on to clear up the confusion surrounding OpenURL. On 3/29/06, Bruce D'Arcus <[EMAIL PROTECTED

Re: [uf-discuss] [hCite] call for examples: language

On Jan 31, 2007, at 1:17 PM, Michael McCracken wrote: If we use @lang, doesn't that mean we're specifying the language of the words in the hCite element, but not necessarily the language of the thing we're citing? Practically aren't these t

Re: [uf-discuss] hCite progress

as included the page count. Granted, I would need to do more research about this to make a more substantiated claim; I'm only familiar with arts/humanities reviews, specifically history books in academic journals. So, if page count is out of the scope of hCite, and if it turns out (from

Re: [uf-discuss] New new mailing list

On Feb 7, 2007, at 3:16 PM, Benjamin West wrote: On 2/7/07, Michael McCracken <[EMAIL PROTECTED]> wrote: So, is the microformats-new mailing list now the appropriate place for discussing hCite development? Good question. My personal opinion is that we should kind of grandfather

Re: [uf-discuss] Citation: next steps?

Hello Mike, thanks for bringing this up. I spent a good portion of the weekend looking at my earlier straw proposal. I started to create an XMDP file and took the examples listed on the wiki and attempted to mark them-up with the citation microformat. This would help to find any deficiencies

Re: [uf-discuss] [hcite] date-published

On 2/21/07, Jeremy Boggs <[EMAIL PROTECTED]> wrote: That said, should there also be a date-accessed or date-visited value for hCite? --- the SHOULD is defined by real-world examples. We shouldn't ask if we SHOULD add a feature, we should see if that feature already is being publi

Re: [uf-discuss] Citation: next steps?

Brian, This is a good summary to date and deserving of being captured on the citation-brainstorming page. Thanks, Tantek On 8/29/06 3:19 PM, "Brian Suda" <[EMAIL PROTECTED]> wrote: > Hello Mike, thanks for bringing this up. > > I spent a good portion of the week

Re: [uf-discuss] [hcite] indentifier

7;m not sure exactly when/where that explaination came from, but i would also include things like ISBN, ISSN as identifiers. I wrote an hCite export template for BibDesk*, and used the identifier (cite-key) as the id attribute on the root element. I'll argue that `identifier` is not data that

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Scott Reynen <[EMAIL PROTECTED]> writes >> So, if page count is out of the scope of hCite, and if it turns out >>(from my observation about media-info) that it doesn't fit into the >>media-info format, would page count just not b

Re: [uf-discuss] [citation]: Brian's outstanding issues 2:

-- I just speak a lot. hCite won't go that route unless a lot of people say it should. I'm personally in favor of including types and having language along the lines of "producers SHOULD include type information" - because it'll make my life easier when I write the BibDesk parse

Re: [uf-discuss] [hCite] call for examples: language

In message <[EMAIL PROTECTED]>, Michael McCracken <[EMAIL PROTECTED]> writes >If we use @lang, doesn't that mean we're specifying the language of >the words in the hCite element Yes (or the sub-element to which the attribute applied). So: Mein Kampf

Re: [uf-discuss] hCite progress

On Nov 13, 2006, at 2:58 PM, Scott Reynen wrote: This might be outside the scope of hCite, but one use case I had in mind requiring specific pages to be parse-able is actually viewing those pages online with a link to something like books.google.com or amazon.com. That would be possible if

Re: [uf-discuss] hCite elevator pitch and my bibliography generator

time being, I'd guess that .bib is better supported than hCite. That way when you update the HTML page, you do NOT have to update several other files as well since they are dynamically created from the single SOURCE XHTML file. In my case, the .bib is the source file. -- Henri Sivonen [

Re: [uf-discuss] hCite progress

So, if page count is out of the scope of hCite, and if it turns out (from my observation about media-info) that it doesn't fit into the media-info format, would page count just not be marked up at all? What exactly would we gain from this markup in terms of functionality? So, if

Re: [uf-discuss] hCite elevator pitch and my bibliography generator

t;. I could wrap each name in a span with a class. But what class? Rephrasing: How would I need to change my markup to comply with what hCite is currently expected to be? If I do that now, will I pollute the space of future hCite data? Other examples of my current markup: [Cascading]Cascading St

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Scott Reynen <[EMAIL PROTECTED]> writes >Are we talking about treating that string as a defined format that >will allow it to be parsed into specific pages, or just as a string? >This might be outside the scope of hCite, but one use case I h

Re: [uf-discuss] [hCite] call for examples: language

On 1/31/07, Edward Summers <[EMAIL PROTECTED]> wrote: On Jan 31, 2007, at 1:17 PM, Michael McCracken wrote: > If we use @lang, doesn't that mean we're specifying the language of > the words in the hCite element, but not necessarily the language of > the thing we'

Re: [uf-discuss] [hCite] call for examples: language

On Jan 31, 2007, at 10:30 AM, Edward Summers wrote: On Jan 31, 2007, at 1:17 PM, Michael McCracken wrote: If we use @lang, doesn't that mean we're specifying the language of the words in the hCite element, but not necessarily the language of the thing we're citing? Practical

Re: [uf-discuss] [hcite] indentifier

On 21/02/07, Ryan Cannon <[EMAIL PROTECTED]> wrote: Identifier is, Per the straw man[1]: > An (not necessarily globally unique) identifier, such as a > cite-key, pubmed ID number, or simply the reference number > or string within a publication ([1] or [CLRS2001]) I wrote

Re: [uf-discuss] [citation]: Brian's outstanding issues 2:

antek once said it's not generally good practice to double up classes ("hcite book") but I'd like some explanation about why. But I will say that in either case, one must allow for extensions. I've worked on this for a long time, and defining a fixed list of types that is

Re: [uf-discuss] hCite progress

-50". So i think something akin to the first example here will work. Are we talking about treating that string as a defined format that will allow it to be parsed into specific pages, or just as a string? This might be outside the scope of hCite, but one use case I had in mind requiring

Re: [uf-discuss] [hCite] dates

Brian Suda wrote: >> publication date: 21 >> date accessed: 3 >> date copyrighted: 1 (from OCLC worldcat online) >> > > --- the other senario is to strip this down to the basics for a > version 1 and NOT include those lesser used dates, then use hCite for

Re: [uf-discuss] [hCite] call for examples: language

guage citing another language, that would help provide evidence for a language field in hCite. If there are no such examples, we could just say that the citations are assumed to be in the same language, and remove the language field (potentially revisiting it for later revisions of the microformat).

Re: [uf-discuss] hCite progress

book is 45 pages long" which is metadata about the book, and is in the realm of media-info microformat. Then there is "this sites pages 43-45" meaning a location. So now we need figure out what we are to do? does the first metadata become 45 and the citation stay "pages" or do we

Re: [uf-discuss] hCite progress

st; raise questions without offering much on > solutions. My apologies.) Does anyone else have thoughts about this? There are specific formatting rules for page ranges in various formal citation styles, right? Right. Are they clear and consistent enough that we can just adopt one of those for page

Re: [uf-discuss] Re: [hcite] indentifier

could be a separate recommendation from the hCite, which could be reused in other contexts. The conclusion of my analysis are: Every identifier is a collection of predicates of the subjects that together uniquely identify the entity (ex. book title, book author, and book edition year and type

Re: hCite Transformations Test (was Re: [uf-discuss] hCite progress)

put up more examples of other types of publications, if that is helpful. --- that would be great! the other thing that would help is "expected output" you can certailny mark-up the data with LOADS of extras, like authors email address, publishers email, etc. but what is the expected outp

RE: [uf-discuss] Work-of-art/Tim Gambell

Thank you Breton. I did see that referred to so I wondered (and found, as you say, that hCite also seems defunct). The last post in the thread I saw seemed to be along the lines of "maybe I'd better check out hCite" and then radio silence. OK, I'll get myself over to the ne

Re: [uf-discuss] relatinal modeling in microformats?

r point, but I'm hardly discussing "modeling for the sake of modeling." Rather, I'm trying to look out ahead just a bit, and mostly to see how the general question relates to the specific issues of hCite. I know I'm not the only one who is worried that microformats will v

[uf-discuss] Re: [hcite] indentifier

-readable because these are used to uniquely identify for find the object in a physical world. Things like key-value-pairs are machines use only and shouldn't be part of hCite. We're agreeing, just coming at it from different directions. Perhaps we should change the description of identif

Re: [uf-discuss] Proposal: species

On 9/16/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: [...] Thoughts, anyone? Sounds like a good idea to me; could be used in hCite too (since titles often include species names and such). Bruce ___ microformats-discuss mailing list microf

[uf-discuss] books, ids

for hCite? Bruce ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] [hcite] date-published

On 2/20/07, Michael McCracken <[EMAIL PROTECTED]> wrote: Is anyone against changing 'date-published' to 'date'? --- the questions is what is the semantics of 'date'? if you create 'date' and use it the date published/updated/copyrighted/etc then those all have different semantics. -brian -- b

Re: [uf-discuss] [hCite] dates

ion 1 and NOT include those lesser used dates, then use hCite for > awhile, see what falls down and itterate? I'm confident that we could come up with other examples of "date accessed" use in the wild, as it's very much a requirement of academic citations of potentially-tra

Re: [uf-discuss] hCite progress

On 11/14/06, Ross Singer <[EMAIL PROTECTED]> wrote: The only places I can really see them occurring are bookstore and library catalogs -- do they really need to be included? What purpose would it serve? Academic paper citations require page number references for literature (be that books or jo

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Ross Singer <[EMAIL PROTECTED]> writes >If you can't grab total number of pages, does your plan of absolute >bird book aggregation fail miserably? I'm not sure what you think can be achieved by such an asinine comment. -- Andy Mabbett Say "NO!" to

Re: [uf-discuss] hCite progress

On Nov 17, 2006, at 8:01 AM, Bruce D'Arcus wrote: I'm going to challenge you here, Andy, because this is yet another time (e.g. not the first) when I think you're stepping over the line. You're being hostile, and I don't think it's appropriate for productive discussion. I agree. Peace, Scott

Re: [uf-discuss] [hCite] dates

In message <[EMAIL PROTECTED]>, Michael McCracken <[EMAIL PROTECTED]> writes >Would 2007 be acceptable, or >should we insist on the full ISO date? I thought that both 2007 and 2007-01 were valid ISO dates... -- Andy Mabbett We

Re: [uf-discuss] hCite progress

On Nov 13, 2006, at 12:35 PM, Bruce D'Arcus wrote: For the best balance of simplicity and generality, I'd suggest just "pages." Don't worry about start and end because, as you noted, pages can be discontinuous. So what would that look like in markup for, say, "pages 10-50"? We don't have to

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Frances Berriman <[EMAIL PROTECTED]> writes >Surely Pages 43 - 45 is an abbreviated way of saying "this comes from >pages 43, 44 and 45 of a 100 page long book". How does that differ from pages 43-45 of a 48 page book, or a 480 page book? -- Andy Mabbett

Re: [uf-discuss] hCite progress

On Nov 13, 2006, at 4:11 PM, Bruce D'Arcus wrote: But I do feel strongly that page count is beyond scope. Do we want to then include ways to encode the length of a CD or a DVD film or an HTML document? I think not, particularly when there are more important issues to worry about. +1 ___

Re: [uf-discuss] [hcite] nesting container elements

On Mar 30, 2007, at 1:10 PM, Scott Reynen wrote: That is, rather than specify which node is a container with a class name, do it by actually having it contain the relevant nodes, e.g. (and I'm proposing this as actual markup, just how nesting could work): Oops, I meant to say I'm *not* pr

Re: [uf-discuss] hCite elevator pitch and my bibliography generator

On Mar 10, 2007, at 21:46, Henri Sivonen wrote: I needed a .bib-based bibliography generator for XHTML, so I wrote one with help from a friend who had developed a .bib parser. In case others are interested, I've published the source code. There's no documentation to speak of. http://hsivon

Re: [uf-discuss] hCite progress

On 11/14/06, Jeremy Boggs <[EMAIL PROTECTED]> wrote: On Nov 13, 2006, at 3:11 PM, Bruce D'Arcus wrote: > Page count is only relevant to publishers and book stores (maybe). Page count is also important in academic and non-academic reviews of books, specifically when the review prints the informa

Re: [uf-discuss] [hCite] call for examples: language

In message <[EMAIL PROTECTED]>, Michael McCracken <[EMAIL PROTECTED]> writes >- We only have two examples of pages marking up the language on the >web - W3C and Amazon.com. Might that be because most if not all of the examples are from English-language websites, and that English-speakers are less

Re: [uf-discuss] [hCite] dates

On 1/17/07, Andy Mabbett <[EMAIL PROTECTED]> wrote: In message <[EMAIL PROTECTED]>, Michael McCracken <[EMAIL PROTECTED]> writes >Would 2007 be acceptable, or >should we insist on the full ISO date? I thought that both 2007 and 2007-01 were valid ISO dates... Yes, I was mistaken about how b

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Bruce D'Arcus <[EMAIL PROTECTED]> writes >Pages to indicate the length of a book should be beyond scope. It's >not relevant to citations. I disagree, not least because people often cite a whole book, rather than part of it. >For the best balance of simplicity and

Re: [uf-discuss] hCite progress

On 11/14/06, Frances Berriman <[EMAIL PROTECTED]> wrote: On 11/14/06, Ross Singer <[EMAIL PROTECTED]> wrote: > The only places I can really see them occurring are bookstore and > library catalogs -- do they really need to be included? What purpose > would it serve? Academic paper citations requ

Re: [uf-discuss] hCite progress

They generally require page number -- not number of pages in the book. -Ross. On 11/14/06, Frances Berriman <[EMAIL PROTECTED]> wrote: On 11/14/06, Ross Singer <[EMAIL PROTECTED]> wrote: > The only places I can really see them occurring are bookstore and > library catalogs -- do they really nee

Re: [uf-discuss] hCite progress

On 11/16/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: In message <[EMAIL PROTECTED]>, Ross Singer <[EMAIL PROTECTED]> writes >If you can't grab total number of pages, does your plan of absolute >bird book aggregation fail miserably? I'm not sure what you think can be achieved by such an asinine

Re: [uf-discuss] hCite progress

On 11/13/06, Scott Reynen <[EMAIL PROTECTED]> wrote: On Nov 13, 2006, at 12:35 PM, Bruce D'Arcus wrote: > For the best balance of simplicity and generality, I'd suggest just > "pages." Don't worry about start and end because, as you noted, pages > can be discontinuous. So what would that look l

Re: URI profiles [was RE: [uf-discuss] Comments from IBM/Lotus repabout Microformats]

les/draft/hlisting >http://microformats.org/wiki/profiles/draft/hcite > >With restricted access to the non-draft profiles. > >Thoughts on how to organize official profiles? While it might be OK to leave draft profiles on the wiki (and I'd be careful about that), canonical versions wou

Re: [uf-discuss] [hCite] call for examples: language

In message <[EMAIL PROTECTED]>, Michael McCracken <[EMAIL PROTECTED]> writes >On 1/31/07, Andy Mabbett <[EMAIL PROTECTED]> wrote: >> In message >> <[EMAIL PROTECTED]>, Michael >> McCracken <[EMAIL PROTECTED]> writes >> >> >- We only have two examples of pages marking up the language on the >> >web

Re: [uf-discuss] hCite progress

On 11/16/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: I'm not sure what you think can be achieved by such an asinine comment. Look, we all have our use cases. All I'm asking is that if total number of pages is omitted, are your hopes dashed? My use case, OpenURL linking, has fairly specific

Re: [uf-discuss] hCite progress

On Nov 16, 2006, at 6:37 PM, Ross Singer wrote: Honestly, the more metadata the merrier. But I think inclusion of more metadata elements than absolutely necessary will be a turn off. Exactly. We'd all like more structured data on the web. But creating structures for data doesn't always le

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Bruce D'Arcus <[EMAIL PROTECTED]> writes >On 11/16/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: >> In message >> <[EMAIL PROTECTED]>, Ross >> Singer <[EMAIL PROTECTED]> writes >> >> >If you can't grab total number of pages, does your plan of absolute >> >bird book ag

Re: [uf-discuss] New new mailing list

So, is the microformats-new mailing list now the appropriate place for discussing hCite development? Thanks, -mike On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote: Ok, after much feedback, deliberation and procrastination, we've started a new mailing list, microformats-new[1] for dev

Re: [uf-discuss] Easy book citations

Bruce D'Arcus: > But if you follow the BibTeX way strictly (where all properties are > single values) you will end up with an hCite tha is liimited, and > akward to extend. Every time someone needs to represent a different > kind of resource, they'll have to go through some c

Re: [uf-discuss] Comments from IBM/Lotus rep about Microformats

can be addressed? I think the only way it can be addressed is with some effort to harmonize microformats and RDFa, which is not going to happen for what seem to me largely political reasons. The fact that we can't have a title property in hCite is already evidence of the practical problem

Re: [uf-discuss] [hCite] dates

In message <[EMAIL PROTECTED]>, Brian Suda <[EMAIL PROTECTED]> writes >Then there is the weird senario in the UK where >some Magazines come-out a month before their publication date. Not some, but "most". There are magazines which sometimes produce 13 monthly (or, rather, 4-weeekly) issues a yea

[uf-discuss] mark-up formatting in e-mail (was: hCite elevator pitch and my bibliography generator)

In message <[EMAIL PROTECTED]>, Henri Sivonen <[EMAIL PROTECTED]> writes >[Cascading]Cascading Style >Sheets. Håkon Wium Lie. PhD >thesis, University of Oslo, class="year">2005. http:// people.opera.co >m/howcome/2006/phd/ (referenced: 2007-02-26< >/span>) Please - everyone - format your mark-u

Re: [uf-discuss] books, ids

to locate, acquire, catalog, lend and preserve library materials. ]]] -- About OCLC [OCLC - Home] http://www.oclc.org/about/default.htm ... complete with pretty URIs. http://www.worldcat.org/oclc/26396865 http://www.worldcat.org/isbn/0816621268 Could be useful for hCite? yes. -- Karl Dub

Re: Re: [uf-discuss] hCite progress

Well, the mark-up might look something like: pages 10-50 or pages 10-50 or (another idea, which doesn't mean much any more) was pages 10-50 But as Bruce said: start-end pages are not really important, just capture the string "pages 10-50". So i think something akin to the first example here wil

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Jeremy Boggs <[EMAIL PROTECTED]> writes >> the total number of pages in a cited article, book-chapter, or >> other section of a publication >Whether I paraphrase a section on page 4 of Brian's _Using >Microformats_ book, or get a direct quote from

RE: [uf-discuss] [hCite] dates

Michael McCracken wrote: > On 1/17/07, Joe Andrieu <[EMAIL PROTECTED]> wrote: > > Actually, date accessed has at least three more examples: > > umich > > ning > > Google > > > > However, they use "retrieved" rather than accessed, > although it is the > > same meaning. > > > > What would be

Re: [uf-discuss] [hcite] date-published

On 2/20/07, Michael McCracken <[EMAIL PROTECTED]> wrote: A quick scan through the markup examples we have confirms my impression that most examples from the web are equally vague about what the dates they show mean. Our condensed summaries on -examples often describe them as date-published, but i

hCard creator and multitoken given/family names (was: Re: [uf-discuss] hCite elevator pitch and my bibliography generator)

On Mar 23, 2007, at 14:22, Paul Wilkins wrote: Currently the formatted names are accepted in the following formats given-name (space) family-name family-name (comma) given-name family-name (comma) given-name-first-initial family-name (space) given-name-first-initial (optional period) Then it

RE: URI profiles [was RE: [uf-discuss] Comments from IBM/Lotus repabout Microformats]

art working on the XMDPs. http://microformats.org/wiki/profiles/hcard http://microformats.org/wiki/profiles/hlisting http://microformats.org/wiki/profiles/xfn http://microformats.org/wiki/profiles/hcite Etc. I don't know that this is the right addressing scheme, but it seems to me that something l

Re: [uf-discuss] mark-up formatting in e-mail (was: hCite elevator pitch and my bibliography generator))

On 3/24/07 4:19 AM, "Andy Mabbett" <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]>, Henri Sivonen > <[EMAIL PROTECTED]> writes > >> [Cascading]Cascading Style >> Sheets. Håkon Wium Lie. PhD >> thesis, University of Oslo, > class="year">2005. http:// people.opera.co >> m/howcome/2006

Re: [uf-discuss] hCite progress

In message <[EMAIL PROTECTED]>, Brian Suda <[EMAIL PROTECTED]> writes >There have been a few hiccups that i am starting to uncover - so any >guidance is welcomed. >I'm not >sure how they handle references in something like a newspaper where >the article starts on page 1 and then jumps to page 43.

Re: [uf-discuss] [hCite] call for examples: language

Le 1 févr. 2007 à 04:05, Colin Barrett a écrit : Book titles and the language they are in are not always identical. In general, messing with the meaning of @lang is tricky, as UAs may take that as a hint to use a different encoding. encoding and languages are not the same beast. I do not kn

<    1   2   3   4   5   6   7   >