Back to dissertation.

 

---

3. Standardization of vertical portal concepts

---

 

3.1. Functional

 

3.1.1. Any member of a community must have producing tools in order to deliver information with the rest of his community.

 

e.g. Community's blog as a unique producing tool where all the information produced by someone is referenced.

(See 2.2.1.1)

 

3.1.2. Promotion mechanisms must be added to each information.

 

Vote systems everywhere for evaluate accuracy and interest of each piece of information.

All information should be able to move from the end of the tail to the head.

(See 2.2.1.1)

 

3.1.3. Let users communicate through public and private messages

 

These messages can become live conversations.

(See 2.2.5.1)

 

3.1.4. Let the community manages its sub-communities

 

Users can create and register to groups/sub-communities.

(See 2.2.5.3)

 

3.1.5. Broadcast different kind of media, text, audio and video

 

(See 2.2.6)

 

3.1.6. Exporting widgets is critical

 

Widgets are now everywhere, on client side (e.g. Windows Vista), on aggregators (e.g. Netvibes), on mobile devices (e.g. iPhone) and even on other portals (e.g. MySpace)

(See 2.2.8)

 

3.1.7. Graphical customization

 

It's your place and everyone doesn't have the same preferred colour.

(See 2.2.9)

 

3.1.8. Provide highly customizable areas for importing widgets

(See 2.2.9)

 

3.2. Technical

 

3.2.1. When it's possible, semantic should be added to each vertical information.

 

This technical recommendation has been pointed out during a reflexion on blogs as main producing tool for portal's users.

In that case templates could help the integration of RDFa with vertical ontologies.

When there aren't ontologies for a specific information folksonomies (tag) are still a great way to categorize information.

(See 2.2.1.1)

 

3.2.2. Messages and comments may become live conversations thanks to Ajax.

 

Ajax should be implemented anywhere a conversation can potentially start.

e.g. tangler.com

(See 2.2.1.2)

 

3.2.3. Implement external authentification and configuration files

 

External authentification (e.g. OpenID) and configuration files (e.g. import/export FOAF)

(See 2.2.4)

 

3.2.4. Summarize services into a user-friendly way designed specifically for mobile devices

 

Focusing on how we can ease information access.

(See 2.2.7)

 

3.2.5. Consider accessibility for video implementation as a priority

 

Be ready to implement SMIL as soon as a browser can render it.

(See 2.2.6)

 

3.2.6. Implement RSS everywhere an information is likely to be aggregated

 

(See 2.2.8)

 

3.2.7. Common semantic tools means common database through the semantic web

 

The first rule when you create a database is to avoid duplicated information.

(See 2.2.8)

 

3.2.8. Use XHTML + CSS would ease the graphical customization process

 

(See 2.2.9)

 

3.2.9. Widgets are following W3C recommendations

 

(See 2.2.9)

 

3.2.10. Accessible for everyone

 

Vertical portals should strictly follow WAI recommendations and the WCAG 2.

(See 2.2.10)