semantic HTML syntax
1 view
Skip to first unread message
Guillaume Lebleu
Jan 6, 2009, 5:28:12 PM1/6/09
to prowl-users
I was going over the syntax and thought it might be beneficial to
support a plain old semantic html format in addition to the current
plain text syntax.
The benefit would be more freedom in formatting and the embedding in
any content, such as a blog post.
The http://microformats.org community has already created several
building block specifications/patterns for dates and currency amounts,
that PROWL could build upon.
support a plain old semantic html format in addition to the current
plain text syntax.
The benefit would be more freedom in formatting and the embedding in
any content, such as a blog post.
The http://microformats.org community has already created several
building block specifications/patterns for dates and currency amounts,
that PROWL could build upon.
els
Jan 6, 2009, 7:45:38 PM1/6/09
to prowl-users
Thanks for the suggestion/comment.
Itemized Report Structure (1.2 and 1.3):
I think additional mark-ups are definitely possible and desirable for
posted records, and I was originally leaning towards plain html but I
just wanted to get the demonstration started with what I already have.
I would be very interested in seeing how you might structure a report
and what mark-ups/tag names you suggest. The main thing for me, at
this early stage, is giving simple reporter apps the option to strip
tags from a report if it is not capable of handling them (to encourage
developer involvement early on regardless of the programming skill).
Single Published Record (1.1): I don't know if your suggestion also
applies to single published records, but the following are my concerns
with regards to mobile device compatibility and expected use of freely
hosted blogs. Please let me know if you think my concerns are
misplaced.
1) Could a user with a basic cell phone SMS a transaction record that
has microformats in it?
With 140 or 160 chars max SMS size, the transaction record might might
not fit in text message. But ...
2) Could the transaction record be texted plain and the SMS message
preprocessor add the tags?
Yes. But then that would require a user to install software or
register with a service provider that offer such service together with
a publishing platform. Not really a big deal, but ...
3) Would such a feature be available and supported from freely-hosted
blogs, such as blogger and wordpress.com?
I'm thinking not in the near future. To quickly try the idea, I
attempted to enter a vcard markup in the icb2 demo blogger site and it
blocked my post entry ("not valid HTML tags"). I don't know, maybe a
simple request to Blogger would get something set-up to support
markups on regular posts (as opposed to singular instances of gadgets
that already allow markups).
To me, the publishing aspect is very important for the early adoption
of Prowl, and therefore freely-hosted blogs platforms would have to be
accomodated which reduces the learning curve and risks when people try
different ledger-based currency models (i.e., if you don't like CC,
switch your accounting model to ocaup, etc.). They could probably
invest in domain names and upgraded sites once their respective
"brands" or communities are stable. But until then, the more visible
these types of transaction become on the web, the better chance we'll
have of encouraging user participation and developer contribution.
Right now, most ledger-based transactions are "hidden" inside members-
only site.
Edgar
On Jan 6, 2:28 pm, Guillaume Lebleu <guilla...@lebleu.org> wrote:
> I was going over the syntax and thought it might be beneficial to
> support a plain old semantic html format in addition to the current
> plain text syntax.
>
> The benefit would be more freedom in formatting and the embedding in
> any content, such as a blog post.
>
> Thehttp://microformats.orgcommunity has already created several
Itemized Report Structure (1.2 and 1.3):
I think additional mark-ups are definitely possible and desirable for
posted records, and I was originally leaning towards plain html but I
just wanted to get the demonstration started with what I already have.
I would be very interested in seeing how you might structure a report
and what mark-ups/tag names you suggest. The main thing for me, at
this early stage, is giving simple reporter apps the option to strip
tags from a report if it is not capable of handling them (to encourage
developer involvement early on regardless of the programming skill).
Single Published Record (1.1): I don't know if your suggestion also
applies to single published records, but the following are my concerns
with regards to mobile device compatibility and expected use of freely
hosted blogs. Please let me know if you think my concerns are
misplaced.
1) Could a user with a basic cell phone SMS a transaction record that
has microformats in it?
With 140 or 160 chars max SMS size, the transaction record might might
not fit in text message. But ...
2) Could the transaction record be texted plain and the SMS message
preprocessor add the tags?
Yes. But then that would require a user to install software or
register with a service provider that offer such service together with
a publishing platform. Not really a big deal, but ...
3) Would such a feature be available and supported from freely-hosted
blogs, such as blogger and wordpress.com?
I'm thinking not in the near future. To quickly try the idea, I
attempted to enter a vcard markup in the icb2 demo blogger site and it
blocked my post entry ("not valid HTML tags"). I don't know, maybe a
simple request to Blogger would get something set-up to support
markups on regular posts (as opposed to singular instances of gadgets
that already allow markups).
To me, the publishing aspect is very important for the early adoption
of Prowl, and therefore freely-hosted blogs platforms would have to be
accomodated which reduces the learning curve and risks when people try
different ledger-based currency models (i.e., if you don't like CC,
switch your accounting model to ocaup, etc.). They could probably
invest in domain names and upgraded sites once their respective
"brands" or communities are stable. But until then, the more visible
these types of transaction become on the web, the better chance we'll
have of encouraging user participation and developer contribution.
Right now, most ledger-based transactions are "hidden" inside members-
only site.
Edgar
On Jan 6, 2:28 pm, Guillaume Lebleu <guilla...@lebleu.org> wrote:
> I was going over the syntax and thought it might be beneficial to
> support a plain old semantic html format in addition to the current
> plain text syntax.
>
> The benefit would be more freedom in formatting and the embedding in
> any content, such as a blog post.
>
els
Jan 6, 2009, 8:32:56 PM1/6/09
to prowl-users
After looking at the blogger post source code some more, I think I see
how a published record might become simpler for the user by
considering blogger's own markup of post-dates and times as part of
the transaction record. This is the same for twitter posts, which I am
pnly just now noticing.
Hmmm ... it is still easier to use a substring-in-string approach for
verifying that copies have been published in corresponding sites, but
it might be worth having an indicator on records if it uses mark-ups
for post-dates if it makes publishing simpler.
Edgar
> > Thehttp://microformats.orgcommunityhas already created several
>
> - Show quoted text -
how a published record might become simpler for the user by
considering blogger's own markup of post-dates and times as part of
the transaction record. This is the same for twitter posts, which I am
pnly just now noticing.
Hmmm ... it is still easier to use a substring-in-string approach for
verifying that copies have been published in corresponding sites, but
it might be worth having an indicator on records if it uses mark-ups
for post-dates if it makes publishing simpler.
Edgar
> > building block specifications/patterns for dates and currency amounts,
> > that PROWL could build upon.- Hide quoted text -
>
> - Show quoted text -
Guillaume Lebleu
Jan 6, 2009, 10:16:52 PM1/6/09
to prowl-users
> I would be very interested in seeing how you might structure a report
> and what mark-ups/tag names you suggest.
I haven't given much thought, but here is an idea based on your
> and what mark-ups/tag names you suggest.
example:
2008-01-03 from buyer.com to mybrand.org 200.00 dollar #01029
<span class="record" id="01029"><span class="dstart">2008-01-03</span>
from <span class="sender">buyer.com</span> to <span
class="receiver">mybrand.org</span> <span class="amount">200.00 <span
class="currency" title="USD">dollar</span></span></span>
The main benefit would be to allow more flexibility in the content:
<span class="record" id="01029">On <span class="dstart"
title="2008-01-03">January 3rd 2008</span>, <span
class="sender">buyer.com</span> paid span class="amount">200.00 <span
class="currency" title="USD">dollar</span></span> to <span
class="receiver">mybrand.org</span></span>
> Single Published Record (1.1): I don't know if your suggestion also
> applies to single published records, but the following are my concerns
> with regards to mobile device compatibility and expected use of freely
> hosted blogs. Please let me know if you think my concerns are
> misplaced.
>
> 1) Could a user with a basic cell phone SMS a transaction record that
> has microformats in it?
approved by the microformats community. In the case of Twitter or SMS
you might want to talk about microsyntax instead. Microformats and
microsyntaxes are implemented differently in different contexts. For
HTML, it is semantic HTML (meaningful class names for instance), for
SMS/Twitter it can be a plain text syntax similar to the one you
already use. You might want to look into the Tipjoy and http://twitpay.me/
:
Twitpay: @[TwitterName] twitpay $[Amount] [Comment]
Example: @startupdunia twitpay $10 thanks for the service
Tipjoy: p [TwitterName] $[Amount]
I think SMS microsyntaxes
els
Jan 6, 2009, 10:56:59 PM1/6/09
to prowl-users
Ok, warning heeded.
One of my main guidelines for development is if a feature will make it
easier for a user to try a system. If a user is lazy, he or she would
not have to type in a transaction date if a reporter could see
microsyntax/format markups that are automatically generated by a
publishing platform. In that case, I'll consider adding a
functionality or feature.
On the other hand, flexibility in publishing so that a record would
flow more naturally with the rest of the post might not be desirable
at this point. I want transaction records to be readily identifiable
in a post or web page, so that uninitiated web surfers would say
"what's that?" and possibly get curious enough to investigate "odd"
ways of paying for things.
Twitpay and Tipjoy are excellent links, very similar to the publishing
idea behind Prowl, and uses very simple formats also. Although, I
would still want the ability to pay using my URL and not have to
register with twitter to transact with a twitter member. Also, a
common publishing syntax would be highly desirable for aggregated
feeds of transaction records, to simplify inter-operable reporter app
development. Otherwise, the reporter would have to be a very smart app
and transferring ledger-based balances/reports would not be as easy.
Edgar
> already use. You might want to look into the Tipjoy andhttp://twitpay.me/
> > > Thehttp://microformats.orgcommunityhasalready created several
One of my main guidelines for development is if a feature will make it
easier for a user to try a system. If a user is lazy, he or she would
not have to type in a transaction date if a reporter could see
microsyntax/format markups that are automatically generated by a
publishing platform. In that case, I'll consider adding a
functionality or feature.
On the other hand, flexibility in publishing so that a record would
flow more naturally with the rest of the post might not be desirable
at this point. I want transaction records to be readily identifiable
in a post or web page, so that uninitiated web surfers would say
"what's that?" and possibly get curious enough to investigate "odd"
ways of paying for things.
Twitpay and Tipjoy are excellent links, very similar to the publishing
idea behind Prowl, and uses very simple formats also. Although, I
would still want the ability to pay using my URL and not have to
register with twitter to transact with a twitter member. Also, a
common publishing syntax would be highly desirable for aggregated
feeds of transaction records, to simplify inter-operable reporter app
development. Otherwise, the reporter would have to be a very smart app
and transferring ledger-based balances/reports would not be as easy.
Edgar
> > > building block specifications/patterns for dates and currency amounts,
Reply all
Reply to author
Forward
0 new messages