I don't think that makes any sense. You should make positive
assertions about data, not negative ones... and why bother with a
not-a-license schema? There's far too many negatives... as in
licenses that it wouldn't be I think we ought only deal with what
things *are* and not what they
Hello,
On 11/17/06, Chris Messina [EMAIL PROTECTED] wrote:
I don't think that makes any sense. You should make positive
assertions about data, not negative ones...
Why?
Andy is in fact trying to make a negative assertion, of the license token.
and why bother with a
not-a-license schema?
On Sat, 2006-11-18 at 07:16 +, Andy Mabbett wrote:
hReview can use rel=license to show that the license, not the page
itself, is available under a certain license.
You meant ... to show that the contents of the hReview itself is
licensed, not the page ...
Why not do the page for
On 11/18/06, Korby Parnell [EMAIL PROTECTED] wrote:
Hi--
I can't seem to find any information about question and answer microformats on
microformats.org. Insofar as I'm new to this list, has there been any backchannel discussion
about distributed QA systems and a microformat or microformats
Hello Korby,
On 11/17/06, Korby Parnell [EMAIL PROTECTED] wrote:
Hi--
I can't seem to find any information about question and answer microformats on
microformats.org. Insofar as I'm new to this list, has there been any backchannel discussion
about distributed QA systems and a microformat or
The _link_ itself isn't a negative assertion; the negative assertion
is in the rights conferered on others by the license that is linked
to. Copyright Me, All Rights Reserved is a good a legal license a
Free For All, Help Yourself.
The URI could be to the copyright office.
Regards, etc...
David
Hello,
On 11/18/06, Andy Mabbett [EMAIL PROTECTED] wrote:
I'm starting to look at using rel=license. Am I right in thing that it
can be used to indicate that a page is NOT available under a license, as
well as for those that are? For instance:
This page is a rel=license
Of course. I retract my last message. Orthogonal issues.
Regards, etc...
On 11/18/06, kota the vantguarde [EMAIL PROTECTED] wrote:
Hello,
On 11/18/06, Andy Mabbett [EMAIL PROTECTED] wrote:
I'm starting to look at using rel=license. Am I right in thing that it
can be used to indicate that a
I'm looking at the schema for hListing [1] and I have a question: is
the item explicitly marked as class=item? It's not clear from the
markup.
Regards, etc...
David
[1] http://microformats.org/wiki/hlisting#Schema
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
On 11/18/06, David Janes [EMAIL PROTECTED] wrote:
I'm looking at the schema for hListing [1] and I have a question: is
the item explicitly marked as class=item? It's not clear from the
markup.
Yes, it is abit confusing and contracitory.
In the schema it says Optional, but then in the Item
I would suggest there's a serious issue with what you've produced so
far, insofar as you have seemed to come up with the microformat first
rather than doing analysis of what's currently in use on the web and
also what's currently being done in other microformats.
For example, hListing and
In message [EMAIL PROTECTED], Mike
Linksvayer [EMAIL PROTECTED] writes
On Sat, 2006-11-18 at 07:16 +, Andy Mabbett wrote:
hReview can use rel=license to show that the license, not the page
itself, is available under a certain license.
You meant ... to show that the contents of the hReview
In message
[EMAIL PROTECTED], Charles
Iliya Krempeaux [EMAIL PROTECTED] writes
and why bother with a
not-a-license schema? There's far too many negatives... as in
licenses that it wouldn't be
Andy might want to name one (or a few) specific licenses that it is
not.
No, thanks.
--
Andy
Rather than trying to devise a microformat (hThing or hItem) that can
describe any thing (or at least any physical thing), with all the
possible or probable properties that might entail: would it perhaps be
better to define a re-usable wrapper, and say that any microformat(s) or
properties inside
The fact that this effort seems vague and non-specific to begin with
seems to preclude it from ever gaining adoption; additionally, finding
existing behavior would be a challenge, not to mention the limited
semantic usefulness of knowing that something is a thing or item.
What *specific*
My current plan is (and has been) to keep it as simple as possible and
_not_ to try to solve the everything problem. In particular, my
current thinking is here [1] which basically says do the same thing
with item from hReview/hListing as was done to adr and geo from
hCard, add a missing field or
My primary goal is to document an existing behavior, that items are
referred to and used in microformats today. If you'll care to look at
the examples found so far and also the usage in existing microformats,
you'll see that this is clearly an _existing behaviour_, insofar as
hListing and hReview
Fair enough. Awhile back I talked to Tantek about micro-patterns as
opposed to data-bearing formats.
This seems more a discussion of design patterns and templates than of
formats, but I'll give the examples a look over.
Chris
On 11/18/06, David Janes [EMAIL PROTECTED] wrote:
My primary goal
In case anyone missed it... something to play with and offer ideas for:
http://ma.gnolia.com/blog/2006/11/14/json-html-and-microformats-oh-my
Chris
--
Chris Messina
Citizen Provocateur
Open Source Ambassador-at-Large
Work: http://citizenagency.com
Blog: http://factoryjoe.com/blog
Cell: 412
To all:
Well, looks like it's time for me to inject my two cents. I had planned to
bring this to the group later when I had time to focus on it, but looks like
the ship is sailing so I better get on board or left behind...
BTW, I'm not presenting the following to be contrary to anyone else's
20 matches
Mail list logo
