exporting bookmarks with tags from delicious

So as many of you have already heard, it looks like Yahoo will be shuttering delicious. Sad but apparently true. In any event, one would think that it would be a relatively simple matter to export from delicious and import into your browser’s bookmarks. The export part is relatively straightfoward, but (at least for those using Firefox, which I do), if you want to import your tags along with your bookmarks, things get a little trickier, because of some incompabitilies between the format that delicious uses for its export file (html) and the format that Firefox uses (JSON).

Apparently, some folks far cleverer than I came up with some ruby scripts that can do it, but why go to all that trouble. Here’s the easiest solution I’ve been able to find: Go here but before you follow the steps, make note of the following:

  1. instead of typing in the URL identified in Step 2 (http://api.del.icio.us/posts/all) use this one instead: https://api.del.icio.us/v1/posts/all (you need to copy and paste into the location bar).
  2. In Step 6, there is one minor detail omitted – the steps to restore should be [Bookmark] -> [Organize Bookmarks] -> [import and backup] -> [Restore] -> [Choose file] -> <created file at 5>.
  3. Also in Step 6, if you have a lot of bookmarks be forwarned that Firefox may become non-responsive as it processes the import. It may give you the “script is taking a long time to respond” message. If you do get that, select the “don’t ask again” checkbox and then click “continue”, then go grab a coffee or some other beverage. Once its done, you should have all your bookmarks (and tags) from delicious now safely ensconced in your Firefox bookmarks.

If you still need an online bookmarks tool, consider Mozilla Sync or Diigo. Perhaps not surprisingly, there seems to be a bit of a backlog in processing imported bookmarks into Diigo. If you don’t need to import bookmarks into Firefox and plan to use something like Diigo exclusively, then of course no need to go through all of the hassle above, as (from what I understand) Diigo will import tags when you import your delicious bookmarks.

Goodbye delicious, it’s been nice knowing you.

electronic document regulations for financial institutions finalized

Earlier this year (May 8 to be precise), the Canadian federal government published some draft regulations relat­ing to the use of elec­tronic doc­u­ments by fed­er­ally reg­u­lated fin­an­cial insti­tu­tions. You can find a rather brief summary in an earlier post, along with some colour commentary comparing the regulations against similar types of provisions in the Ontario Consumer Protection Act and Electronic Commerce Act. You can find the earlier draft regulations in that post or at the Canada Gazette website (scroll down to the bottom).

In any event, about two weeks ago (November 10 to be precise), the federal government released the finalized regulations for banks and bank holding companies, cooperative credit associations, insurance and insurance holding companies and trust and loan companies.

If you haven’t yet reviewed the legislation, you may want to look at my earlier post, which remains, I think, somewhat useful, as the revisions made between the draft and final regulations are not that significant. If you’d like to see for yourself, I’ve taken the liberty of generating redlines (in Word format) for each of them (banks – redline,  coops – redlineinsur – redline and trusts – redline) or you can read the summary below.

There’s basically two items that are common across all the regulations. The first isn’t really much of a change but rather the fixing of the date upon which they come into force, which has now been set for June 1, 2011. The second change is a minor clarification that specific information provided in a consent is only applicable if that consent is provided in writing (whether in paper or electronic form). Here’s the specific change, which looks to be common across all four regulations:

(4) TheIf the addressee’s consent is provided in writing, in paper or electronic form, it must include the name of the information system designated by the addressee for the receipt of the electronic document and a list, in paper or electronic form, of the notices, documents or other information that is covered by the consent.

Seems to make sense, given that such consent can also be provided orally, and that is addressed in the next clause:

(5) If the addressee’s consent is provided orally, the originator or the person acting for the originator must, without delay, provide the addressee in writing, in paper or electronic form, with the information referred to in subsection (2) and confirm the information referred to in subsection (4).

The federal government’s provides the following comments in the related regulatory impact analysis statement (scroll down toward the end) with respect to this change, the in-force date and some changes which had been requested but were not made:

Consultation

After pre-publication of these regulations on May 8, 2010, in the Canada Gazette, Part I, comments related to about 10 different issues were raised from financial industry associations. Only two of the four regulations were commented on, namely the Electronic Documents Regulations and the Policyholders Disclosure Regulations. In addition, the comments did not raise any substantial concerns but rather focused on ensuring that the regulations efficiently achieved the stated policy goals.

As a result, the Government has made minor modifications to the Electronic Documents Regulations to more efficiently handle situations where a customer of a financial institution provides oral consent for the electronic delivery of documents. The previous version of the Regulations appeared to require customers to give financial institutions written documentation when giving consent in call cases — notwithstanding the fact that the Regulations allow for consent to be granted orally. Section 5(4) now sets out the information that must be provided when consent is not provided orally (including the name of the information system designated by the addressee and a list of the notices, documents or other information that is covered by the consent). Section 5(5) goes on to set out the responsibilities of the originator to properly document oral consent and confirm the information received from the customer.

Some comments have not been reflected as stakeholders requested changes that were inconsistent with the policy intent of the regulations. For example, requested changes to the Policyholder Disclosure Regulations would have had the effect of unduly narrowing the scope of information provided to holders of insurance policies with governance rights attached. Other comments to remove from the definition of adjustable policies those where an insurance company can indirectly change the premium or charge for insurance would have had the effect of restricting the Government’s ability to ensure compliance with the regulations.

Implementation, enforcement and service standards

Industry representatives asked that the regulations come into force from six months to one year after final publication, indicating operational challenges (systems, procedures, training). To allow financial institutions sufficient time to prepare documentation in advance of annual general meetings, this package of regulations will come into force on June 1, 2011.

The regulations do not require any new mechanisms to ensure compliance and enforcement. The Office of the Superintendent of Financial Institutions (OSFI) already administers the governance provisions in the federal financial institutions statutes. As such, OSFI would ensure compliance with the new requirements using its existing compliance tools, including compliance agreements and administrative monetary penalties.

free legal advice (at least in California, for now)

And no, I don’t mean this blog, because as you know I don’t dispense legal advice here.

In any event, read about a new startup called LawPivot in an entry from the venerable TechCrunch. It’s described by TC as “a self described “Quora for legal” that allows technology companies to confidentially ask legal questions to expert attorneys.” And currently, for free. By the looks of it, seems to be limited to California for the time being. But hurry! Apparently the business model is to eventually charge both the askers and the askees for access.

TechCrunch seems to be bullish on its prospects. Myself a bit less so. I would think that one of the drivers of something like this would be to develop a critical mass of legal information or advice, much in the same way that many law firms have started developing massive indexed and searchable databases both for their internal use and sometimes for access by clients. Limiting it to one-off queries seems to limit the ability to leverage advice and to result in, to some extent, a duplication of efforts by the various lawyers seeking to impress a potential client.

But who knows. Perhaps they plan to leverage content in some other way at a later stage. Worth keeping an eye on. And of course, if you’re in Calfornia, worth giving a spin if you’re looking for some free legal advice.

standardized seed financing docs for canucks

Some of my loyal readers may recall one of my posts earlier this year about the development of standardized seed financing docs in the US, where there were, at the time, about four different sets of docs which had been developed. It pointed to a more detailed article by Brad Feld. In any event, I had asked the question whether anyone was aware of a similar initiative in Canada but didn’t hear from anyone. Was actually going to try doing it myself, but free work that you give away sometimes goes quickly to the back burner (or rather off the stove altogether) when things get busy. Least that’s my excuse.

In any event, I was very happy to hear that someone in Canada has in fact undertaken this initiative. The folks at MaRS here in Toronto, and in particular Mark Zimmerman, have apparently developed a nice set of Canadianized templates, including a term sheet (.doc) a subscription agreement (.doc), articles of amendment (.doc) and a shareholders’ agreement (.doc), with a founder’s agreement and employment agreement in the work. They already have a template independent contractor agreement (.doc).

I haven’t had a chance to look at them, but if you happen to need a set of seed round docs, and you’re here in the great white north, I’d encourage you to check them out. The folks at MaRS deserve a pat on the back for taking the initiative.

Tip o’ the fedora to Jonathan Polak for bringing this to my attention.

it.can presentation on open source

I gave a speech, along with Thomas Prowse (Genband) and Fred Dixon (Blindside Networks) at the IT.Can Annual Conference (PDF) in Montreal last week. The following is the paper that went along with the presentation, for whatever it’s worth. Not particularly earth-shattering but an approach that is a little different than user/purchaser centric approach I usually see about the topic in other papers and presentations, at least within the realm of those addressed to lawyers. Also in Word format: IT.Can 2010 open source (paper) v2.

Many other great presentations as well, by some of the leading IT practitioners in Canada. Not a member? Consider joining. Well worth it.

OPEN SOURCE BUSINESS MODELS

by David Ma[1]

1.                  INTRODUCTION

This paper will: (a) review some of the more common business models used to exploit intellectual property; (b) describe, in brief, what open source is; and (c) identify characteristics of open source licenses as they pertain to those business models.

It is oriented primarily to owners or developers of intellectual property that are contemplating the alternatives available to them in the commercial exploitation of that IP. The general context on which this paper focuses is the development and exploitation of software. However, some or all of the principles described below may be applied in other contexts, and we describe some of these briefly toward the end of the paper.

The intent of this paper is not to advocate open source business models as the definitive way to undertake such a venture. Rather, it is to familiarize the reader with the underpinnings of what is becoming an increasingly prevalent approach to exploiting IP which warrants serious consideration as an alternative to more traditional methods – namely, a proprietary licensing model which emphasizes the treatment of underlying source code as a trade secret. It may well be that the particular circumstances of a business undertaking do not lend themselves to such models. However, it would be, in the author’s opinion, inadvisable not to give them due consideration.

Read more it.can presentation on open source

amazon one-click patent – federal court decision

If I were to pick a subtitle for this post, it would probably be “Bilski, Canadian style”.

One of my colleagues (Thanks Peter!) was kind enough to mention that the judgement of the Federal Court of Canada (PDF) was released earlier today, so I set aside a few minutes to go through it. Admittedly, I haven’t been following the case all that closely.

In any event, rather than slogging through all 35 pages yourself, the following is a rather abbreviated summary of the decision:

  • After quite a bit of back and forth on the application process, the Commissioner of Patents ultimately rejected Amazon’s patent application in 2009
  • The Commissioner rejected Amazon’s patent on the basis that it was “non-patentable subject matter”, primarily for any one of three reasons:
    • the claimed invention was not physical in nature nor did it result in some change or effect on physical objects;
    • the claims were claims on business methods, which the Commissioner concluded were not patentable; and
    • the claims were not “technological” in nature (meaning that they could be used to address a technical problem) and therefore not patentable.
  • The Federal Court disagreed with each of the Commissioner’s reasons:
    • the Court was of the opinion that the physicality test was too restrictive – instead, the proper test was whether or not the claims had “practical application” – i.e. something that results in a “change in character or condition” and found that Amazon’s claims could meet that standard through Amazon’s customers “manipulating their computer and creating an order”;
    • the Court did not agree that business methods were non-patentable under Canadian law; and
    • the Court did not agree that there was a “technology” test for patentability under Canadian law.

On the first point relating to physicality, the Court’s comments seem to echo, to some degree, the Bilski decision by the US Supreme Court and its rejection of the “machine or transformation” test.

Although the Federal Court did not agree with the Commissioner’s rejection of the patent, it also did not affirm its validity nor did it grant the patent. Instead, it sent back the patent for re-examination.

Of course, there is quite a bit more in the decision itself, including riveting details on novelty, analyses of the process used to assess patentability, elements of that process versus application of same to the patent itself, etc. etc. So consider the bullet points above a gross oversimplification and use accordingly.

us supreme court releases bilski decision on patents

The US Supreme Court yesterday released its decision on the Bilski v. Kappos case.

The bottom line:

Business methods can still be patented in the U.S.

The summary:

Bilski attempted to patent a method of hedging energy commodities, primarily in the form of a mathematical formula. The US Patent Office rejected the application. The rejection was upheld by the Board of Patent Appeals and the Court of Appeal for the Federal Circuit.

Most notably, the Court of Appeal rejected the previous test which had enabled the claiming of business method patents (the State Street Bank & Trust case), instead holding that “a claimed process is patent eligible [only] if: (1) it is tied to a particular machine or apparatus, or (2) it transforms a particular article into a different state or thing”.

Needless to say, this new test would have put a bit of a damper on business method patents.

The Supreme Court did not agree with the Court of Appeal. It held that the “machine or transformation” test is not the only test for patent eligibility for a process and that business method patents are in fact permissible under the Patent Act.

That being said, they nonetheless agreed with the Court of Appeal that Bilski’s patent should be rejected, not because it failed to meet the “machine or transformation” test, but rather because it was an attempt to patent an abstract idea rather than a business method. The Supreme Court affirmed that abstract ideas are not patentable.

Comments:

Many like the EFF seem to be disappointed, but from a jurisprudential perspective the judgement makes sense to me. The Supreme Court’s rationale was that courts “should not read into the patent laws limitations and conditions which the legislature has not expressed” and there was no reasonable basis on which the term “process” had to be specifically tied to a machine or the transformation of an article.

In other words, it’s not the job of the courts to make up new stuff when it comes to the law – their job is only to interpret the law correctly. And if there’s any issue with the Patent Act, then it should be dealt with through legislative change rather than a judicial decision.

Perhaps not quite the interventionist approach that some might have been hoping for.

So, as the EFF notes, all of you out there that have a glimmer of inspiration on how to make your fortune from, for example, a system for reserving toilets, (or suing others who come up with the same thing but didn’t apply for a patent) can still pursue that dream.

Bilski v. Kappos (PDF)

fusenet’s employment/entrepreneur program

A very interesting story in IT World Canada about a company called Fusenet that has put into place a novel approach to business. In effect, it is empowering its employees to become entrepreneurs and giving them equity in their creations. Fascinating approach. Inevitably comparisons can be drawn with a similar program Google runs, but as far as I’m aware Google retains ownership of everything created by its employees. Not so with Fusenet’s model. From the article:

Every Friday, the Pet Project Program (P3) goes into effect. “If you’ve been approved into the program, on Friday, we don’t expect to see you at your desk. You’ll be in our lab or you’ll be collaborating with other people,” said Singhal.

The P3 model is codified into employee agreements and the intellectual property developed during this time does not belong to Fusenet, he said.

If an employee spends three months working every Friday to develop a new technology for better video compression, for example, and then presents it to the company, the idea still belongs to the employee, said Singhal.

Fusenet will ask the employee how much they want to sell the idea for or whether they want to start a company that will sell or license the product, he said. “We’ll help you market that and say, ‘We’ll take 50 per cent of the equity, you take the other 50 per cent,’” he said.

“We will help you with money, we will give you all the resources you need – marketing, customer service, R&D – but you get to keep a significant chunk of the equity in the business as opposed to having just the pride of being able to say you started it,” he said.

The policy applies to all employees, but it’s the software developers who are most likely to come up with the ideas, said Singhal. “We thought this was an interesting model … 99 per cent of the companies out there will take the software,” he said.

Fusenet has experienced one major success, one emerging success and two failures as a result of the model, said Singhal. Another five projects are currently in the R&D stage, he said.

Of course there is a caveat noted in the story about how such an arrangement must be carefully documented. I could also see a few risks associated with this as far as delineation of IP and who owns what. Very often, when new ideas spring up, they may be closely related to some existing intellectual property or based upon it. The question then is where the dividing line is or should be drawn and how that is set out in the documents. Not an insurmountable issue but one that does warrant a bit of thought.

I certainly admire Fusenet for having the vision and courage to adopt such a model. Of course, it’s no guarantee for success but certainly puts all the right incentives in place to have an environment conducive to that. I really do hope to see some interesting things come out of their shop in the near future. They will, after all, be very likely to attract the right sort of folks with this program.

new copyright act now online – updated

Update: For anyone out there who: (a) pored over the previous incarnation of this bill (i.e. Bill C-61) back in 2008; (b) doesn’t happen to have redlining software; and (c) just wants to review what has changed between C-61 and C-32, here are redlines showing the changes from C-61 to C-32 (Word and PDF). Happy reading.

The much anticipated Copyright Modernization Act (or Bill C-32) was tabled yesterday and is now on-line and available for your reading pleasure. Given the broad interest in this act, it’s not surprising that there has already been a ton of press on it, including summaries and analyses galore.  I don’t propose to reinvent the wheel, so will simply point to you a post in Michael Geist’s blog where he provides a summary and various links to media coverage of the bill (which also have their own summaries) plus of course his own take on it.

My initial impression is that the bill strikes a relatively good balance between content creators and content users. Of course, given the highly politicized nature of copyright reform, and the sometimes fairly extreme views taken in various camps, it won’t make everyone happy. From the perspective of Geist et al. on the user side, the biggest criticism so far has been how digital locks (or “TPMs”) are dealt with. The short version is that TPMs are permitted even if they prevent users from exercising specific rights that are deemed by the Copyright Act not to constitute copyright infringement.

I have my own views on TPMs but will reserve that for another post.