On May 20, 2009, at 19:24, Bruce D'Arcus wrote:
Re: the recent microdata work and the subsequent effort to include
BibTeX in the spec, I summarized my argument against this on my blog:
http://community.muohio.edu/blogs/darcusb/archives/2009/05/20/on-the-inclusion-of-bibtex-in-html5
Quoting
Interesting.
Despite my PoV against the microdata proposal, I've taken a look at it
and find a minor typo:
Within 5.4.1 vCard, by the end of the n property description, the
spec reads:
The value of the fn property a name in one of the following forms:
shouldn't it read:
The value of the fn
Hi Henri,
On Thu, May 21, 2009 at 4:00 AM, Henri Sivonen hsivo...@iki.fi wrote:
On May 20, 2009, at 19:24, Bruce D'Arcus wrote:
Re: the recent microdata work and the subsequent effort to include
BibTeX in the spec, I summarized my argument against this on my blog:
Oops; two quick things ...
On Thu, May 21, 2009 at 8:02 AM, Bruce D'Arcus bdar...@gmail.com wrote:
Citation and bibliographic formatting conventions do include
information that suggests type; it's not that it requires a human
reader to decipher.
I meant it's JUST that ...
Here's the
On May 21, 2009, at 15:02, Bruce D'Arcus wrote:
Except the assumption that BIbTeX is widely used is overdrawn once you
get out of the technology and sciences sectors.
OK.
This doesn't mean that BibTeX is a bad basis. The set of types and
fields is
limited, though.
It's limited, and it's
On Thu, 2009-05-21 at 13:26 +0200, Eduard Pascual wrote:
[... lots ...]
Eduard, thanks for your long and informative reply. I won't go into
every point mentioned in detail, but in summary I'd like to say that
your message reassured me on a few points and perhaps CRDF is not as bad
as I
On Thu, May 21, 2009 at 9:51 AM, Henri Sivonen hsivo...@iki.fi wrote:
On May 21, 2009, at 15:02, Bruce D'Arcus wrote:
Except the assumption that BIbTeX is widely used is overdrawn once you
get out of the technology and sciences sectors.
OK.
This doesn't mean that BibTeX is a bad basis. The
I think this is a bit of a misnomer, as the current token can be an
end tag token (although it will throw a parse error whatever happens
once it reaches this state). I suggest renaming it to self-closing
tag state.
--
Geoffrey Sneddon
http://gsnedders.com/
Both FOAF and vCard have unstructured personal name properties
(foaf:name and v:fn) that address this.
But vCard required both N and FN, so if you only have FN, you can't get an N
without a lot of dictionary-based domain knowledge and special rules. (Or
you can make a GIGO N...)
Hmm ...
Anne van Kesteren wrote:
2) DOMParser can parse from a byte array instead of a string; this
makes it a little easier to work with XML in encodings other than
UTF-8 or UTF-16.
ECMASCript doesn't have byte arrays though. (Though it would be nice if it did.)
Sure, but it has arrays
10 matches
Mail list logo
