It's very useful
posted @ 2008-08-16 18:23 天堂水 阅读(5) | 评论 (0)编辑
It's very useful
posted @ 2008-08-16 18:19 天堂水 阅读(5) | 评论 (0)编辑

Abstract. A common feeling is that Semantic Web and Web 2.0 are two competing visions for the future evolution of the Web. In fact, the core technologies and concerns of these two terms are complementary. Web 2.0 applications focus on community and user interaction, which draws on Semantic Web infrastructure to facilitate information sharing. And Semantic Web provides machine-readable data to support the semantic requirement of Web 2.0. There is a significant benefit from combining Web 2.0 and Semantic Web. This paper evaluates the current development of Semantic Web and Web 2.0, and presents some approaches for compounding these two technologies.

 

1.     Introduction

Web 2.0 is mostly a social revolution in the use of Web technologies, a paradigm shift from the Web as a publishing medium to a medium of interaction and participation (Lassila, 2007). The core technologies for Web 2.0 application involve RSS (Really Simple Syndication), AJAX (Asynchronous JavaScript and XML), microformats, and REST (Representational State Transfer). One major goal of Web 2.0 is to promote collaboration among users and improve the user interaction. Many Internet service suppliers provide applications based Web 2.0 technologies such as MySpace, YouTube, Flikr and Wikipedia to enable users to post personal content, music, video and photos on the web. Web 2.0’s success is mainly attributed to the widespread web applications such as weblog, syndication and tagging system (Mikroyannidia, 2007).

 

The Semantic Web with data oriented is considered as an extension of the existing Web with document oriented. The perspective of Semantic Web is to create one absolutely semantic environment which enables the agent to infer resources. The current rapid rate of growth in the amount of web information has brought a challenge to managing this information (Mikroyannidia, 2007). Most of published contents are not structured for logical reasoning, so a keyword search is not efficient any more. The Semantic Web aims to solve these problems by presenting information in machine-understandable formats that enables agents to integrate information and enhances search precision. It uses ontology to represent knowledge, however, the difficulty of ontology creation and maintenance which needs experts viewing their domains results in few Web 2.0 applications deploy the semantic data.

 

2.     Current Work

With the past years’ development in Semantic Web since the concept came out, the Semantic Web has matured into a set of standards. Resource Description Framework (RDF) and Web Ontology Language (OWL) have become standards and new technologies are becoming maturity for embedding semantics in existing Web pages and querying RDF knowledge stores, so something exciting is clearly happening in this area (Lassila, 2007). The academic conferences have presented some current work that has been presented. Corporate research centers and academic labs are improving the vision of Semantic Web languages. W3C released the new vision of query language SPARQL in January 2008. GRDDL (Gleaning Resource Description from Dialects of Languages) and RDFa provide a technology base for making Semantic Web applications interoperate more smoothly with traditional Web applications (Hendler, 2008). Many open source software have facilitated Semantic Web development such as Jena, jBoss, PostgreSQL database and Protégé. Despite this, the current Semantic Web has no practical, scalable way for non experts to create adequate mapping functions between a large amount of constantly changing ontology and instance information or to manage their periodic maintenance (Greaves, 2007). One of six challenges (Benjamins, 2006) for Semantic Web is ontology availability, development and evolution. At the non expert level, RDF and OWL are difficult to learn and written in an accurate syntax. Most existing editors and software development environments are feasible for knowledge representation experts. The ontology creator need be familiar with complex knowledge logic. Current software developers would rather employ less semantically demanding representations, such as XML or microformats rather than RDF and OWL.

 

In fact, many key features of Web 2.0 applications derive from the vision of the Semantic Web. In particular, at the time the “Web 2.0” was coined the initial RDF and OWL recommendations were cleared (Greaves, 2007). Depending on a lightweight, flexible, and shared semantic model, Web 2.0 has quickly matured. Moreover, today it encompasses most exciting Web based applications: mashups, blogs, wikis, tagging systems, user-created publication systems, and social networking applications. In contrast, there are no innovative and commercially successful applications for Semantic Web. Web 2.0 has become a technology wave for software developers. The International Semantic Web Conference in 2006 began to consider encouraging Semantic Web technical capabilities to support Web 2.0 application’s semantic requirements (Greaves, 2007). However, the progress is extremely difficult. Although the basic combination reasoning is able to extend and regularize tag systems and increase search precision, the completely match between Semantic Web technologies and Web 2.0 application requirements is considerably more muddled (Greaves, 2007). Some research progresses have been implemented. A Semantic Tagging and Searching System STSS (Hope, 2007) is created to converge Web 2.0 and Semantic Web. Some approaches are used to create Semantic Web Blog.

 

3.     Semantic Tagging

A collaborative form of this process for shared web-based resources, called “tagging” (Marlow, 2006), which is widely applied in most Web 2.0 applications. The conventional keyword based tags fail to search contents identified by different tags with the same meaning. In particular, the synonyms are not considered as the same semantic. STSS improves search results by adding context data to tags. Before posting the content to the web, users choose the defined context for the tag provided by the ontology. For example, the tag “Tiger” might have more than one context such as “animal”, “cartoon” and “story”. The user can select one or more contexts. After submitting, STSS creates a new relationship between the tag and the context selected. Adding contexts to the tags provides broader search results, because the search can return all content that matches the keyword and all content associated with tags that are context of the keyword. The benefit of this approach allows the user easily to edit tags without destroying the ontology consistencies (Hope, 2007). However, due to the only a single ontology used in the system the contexts cannot be shared with other ontologies.

 

The other approach to solve the problem of tagging is to make explicit semantics behind the tag space in social tagging systems (Specia, 2007). Compared with the approach above, it does not rely on the additional context. This solution consists of three steps: pre-processing, clustering and identifying concept and relationship. The first step involves removing unusual tags which cannot be found in ontologies, and grouping similar tags. Each group is replaced by its representative. The second step is to analyze the tag space to indentify groups and finally generate related cluster (Specia, 2007). In the third step, the knowledge provided by other sources including ontologies available on the web is implemented to identify relationships between tags in each cluster, if they exist categorizes them. After that, the tags will be mapped into concepts, properties and instance of ontologies. This approach is feasible and promising, which makes use of the existing ontologis searched by Swoogle. The new ontology derived from folksonomies (Specia, 2007) provides machine-readable data, which enables Web 2.0 search engines to retrieve more accurate information.

 

4.     Semantic Weblog

(Karger, 2004) constructs a semantic blogging environment based on a Semantic Web browser “Haystack”. The most current blogs have machine readable contents encoded in an XML format called RSS which allows individual blogs to be aggregated together. In this paradigm, the XSL transform is considered as a standard to translate existing RSS 9.0/2.0 feeds into RDF. In this model, Haystack provides specialized forms retrieving different level of semantics for RDF representation automatically and enables users to publish such information using RSS 1.0 (Karger, 2004). Another scenario of Semantic Weblog is presented in (Ankolekar, 2007). A plug-in that uses Semantic Web technologies allow bloggers to add information about blog entries. The semantic data can be created by a light weight ontology language FOAF which is easier to handle than complex RDF/OWL.

 

5.     Future Work and Conclusion

Form the view of the business model, in order to prosper in the market the Semantic Web should provide an essential capability better, faster, or cheaper for no expert users than any other competing technology. Web 2.0 applications have made it easier for everybody to share a wide variety of contents over the Internet. It is necessary to deploy an efficient and accurate searching method for specific content in this ocean of information. Semantic data creations tools will help embed the semantics to web information. Web 2.0 and Semantic Web need complement each other, and in fact both communities need elements from each other’s technologies to overcome their own limitations. One believable thing is that semantic technologies will bring a robust and extensible enhancement for emerging Web 2.0 applications. Definitely, data reuse, distribution and aggregation can be greatly facilitated by the Semantic Web’s infrastructures. Web 2.0 proponents should encourage themselves to embrace those Semantic Web technologies. In the future, the two communities are expected to create an innovative Web application as the representation of Web 2.0 and Semantic Web by exploiting each other’s achievements and insights.

 

References

Ankolekar,A. Krotzsch,M. & Tran,T. 2008, ‘The tow cultures: Mashing up Web 2.0 and the Semantic Web’, Elsevier Science Publishers B. V, vol.6, no.1, pp.70-75.

 

Benjamins,R,V. & Contreras,J. 2006, ‘Six Challenges for the Semantic Web’, [Online] Available at: http://www.cs.man.ac.uk/~ocorcho/documents/KRR2002WS_BenjaminsEtAl.pdf

 

Greaves,M. 2007, ‘Semantic Web 2.0’, IEEE Educational Activities Department, vol.22, no.2, pp.94-96.

 

Hendler,J. & Golbeck,J. 2008,’Metcale’s Law, Web 2.0 and Semantic Web’, Elsevier Science Publishers B.V, vol.6, no.1, pp14-20.

 

Hope,G. Wang,T. & Barkataki,S. 2007, ’Convergence of Web 2.0 and Semantic Web: A Semantic Tagging and Searching System for Creating and Searching Blogs’, Proceedings of the International Conference on Semantic Computing, pp.201-208

 

Karger,D.R. & Quan,D. 2004, ‘What Would It Mean to Blog on the Semantic Web?’, Proceedings of the Third International Semantic Web Conference (ISWC2004), pp.214-228.

 

Lassila,O. & Hendler,J. 2007, ‘Embracing Web 3.0’, IEEE Educational Activities Department, vol.11, no.3, pp.90-93.

 

Mikroyannidia,A. 2007, ‘Toward a Social Semantic Web’, IEEE Computer Society Press, vol.40, no.11, pp.113-115.

 

Marlow,C. Naaman,M. Boyd,D. & Davis,M. 2006, ‘HT06, tagging paper, taxonomy, Flickr, academic article, to read’, Proceedings of the Seventeenth Conference on Hypertext and Hypermedia, pp.31-40.

 

Specia,L. & Motta,E. 2007, ‘Integrating Folksonomies with the Semantic Web’, [Online] Available at: http://www.eswc2007.org/pdf/eswc07-specia.pdf

posted @ 2008-08-02 22:11 天堂水 阅读(651) | 评论 (4)编辑
真倒霉,在当当网上买了这本书,却没有光盘(让朋友签收的)先不说验货的问题。在网上搜了一下,没想到有很多人抱怨缺少光盘。根本得不到很好的处理,而且浪费时间。

唯一希望网上有提供下载的地方。
posted @ 2008-07-28 18:33 天堂水 阅读(123) | 评论 (0)编辑

DateTime.ToString()函数有四个重载。一般用得多的就是不带参数的那个了。殊不知,DateTime.ToString(string format)功能更强大,能输出不同格式的日期。以下把一些情况罗列出来,供大家参考。有些在MSDN上有的就没有列出来了。

1.         y代表年份,注意是小写的y,大写的Y并不代表年份。

2.         M表示月份。

3.         d表示日期,注意D并不代表什么。

4.         hH表示小时,h用的是12小时制,H用的是24小时制。

5.         m表示分钟。

6.         s表示秒。注意S并不代表什么。

格式

输出

示例

y

7

string yy = DateTime.Now.ToString("y-MM")

yy="7-05"

yy

07

string yy = DateTime.Now.ToString("yy-MM")

yy="07-05"

yyy或更多的y

1984

string yy = DateTime.Now.ToString("yyyy");

yy="2007"

M

5.

string mon = DateTime.Parse("1984-05-09")ToString("yyyy-M")

mon = "1984-5"

MM

05.

string mon = DateTime.Parse("1984-05-09")ToString("M")

mon = "05"

MMM

如果是中文版的操作系统,则会输出:五月.

如果是英文操作系统,则输入月份前三个字母的简写:May

string mon = DateTime.Parse("2006-07-01").ToString("MMM")

英文版操作系统:Jul

中文版操作系统:七月

MMMM或更多的M

如果是中文版的操作系统,则会输出:五月.

如果是英文操作系统,则输入月份的全写

string mon = DateTime.Parse("2006-07-01").ToString("MMM")

英文版操作系统:July

中文版操作系统:七月

日期或星期

d

9

string dd= DateTime.Parse("1984-05-09")ToString("d")

dd= "9"

 

dd

09

string dd= DateTime.Parse("1984-05-09")ToString("dd")

dd= "09"

ddd

如果是中文版的操作系统,则会输出星期,如星期三。.

如果是英文操作系统,则输出星期的简写:如

Wed

string dd = DateTime.Parse("2006-07-01").ToString("ddd")

英文版操作系统:Wed

中文版操作系统:星期三

dddd或更多的d

如果是中文版的操作系统,则会输出星期,如星期三。.

如果是英文操作系统,则输出星期:如

Wednesday

string dd = DateTime.Parse("2006-07-01").ToString("dddd")

英文版操作系统:Wednesday

中文版操作系统:星期三

小时

h

小时范围:1-12

string hh = DateTime.Now.ToString(“h”);

hh = 8

hh或更多的h

小时范围:1-12

string hh = DateTime.Now.ToString(“hh”);

hh = 08

H

小时范围:0-23

string hh = DateTime.Now.ToString(“yyyy-H”);

hh = 2006-8

HH或更多的H

小时范围:0-23

string hh = DateTime.Now.ToString(“yyyy-HH”);

hh = 2006-08

string hh = DateTime.Pare(“2006-7-4 18:00:00”).ToString(“yyyy-HH”);

hh = 2006-18

分钟

m

6

string mm =  DateTime.Now.ToString("yyyy-MM-dd-m");

mm = “2006-07-01-6”;

mm或更多的m

06

string mm =  DateTime.Now.ToString("yyyy-MM-dd-mm");

mm = “2006-07-01-06”;

s

6

string mm =  DateTime.Now.ToString("yyyy-MM-dd-s");

mm = “2006-07-01-6”;

ss或更多的s

06

string mm =  DateTime.Now.ToString("yyyy-MM-dd-ss");

mm = “2006-07-01-06”;

posted @ 2008-07-25 21:22 天堂水 阅读(40) | 评论 (0)编辑
 d           1/3/2002  
  M/d/yyyy   (ShortDatePattern)  
   
  D           Thursday,   January   03,   2002  
  dddd,   MMMM   dd,   yyyy   (LongDatePattern)  
   
  f           Thursday,   January   03,   2002   12:00   AM  
   
  F           Thursday,   January   03,   2002   12:00:00   AM  
  dddd,   MMMM   dd,   yyyy   h:mm:ss   tt   (FullDateTimePattern)  
   
  g           1/3/2002   12:00   AM  
   
  G           1/3/2002   12:00:00   AM  
   
  m           January   03  
  MMMM   dd   (MonthDayPattern)  
   
  M           January   03  
  MMMM   dd   (MonthDayPattern)  
   
  r           Thu,   03   Jan   2002   00:00:00   GMT  
  ddd,   dd   MMM   yyyy   HH':'mm':'ss   'GMT'   (RFC1123Pattern)  
   
  R           Thu,   03   Jan   2002   00:00:00   GMT  
  ddd,   dd   MMM   yyyy   HH':'mm':'ss   'GMT'   (RFC1123Pattern)  
   
  s           2002-01-03T00:00:00  
  yyyy'-'MM'-'dd'T'HH':'mm':'ss   (SortableDateTimePattern)  
   
  t           12:00   AM  
  h:mm   tt   (ShortTimePattern)  
   
  T           12:00:00   AM  
  h:mm:ss   tt   (LongTimePattern)  
   
  u           2002-01-03   00:00:00Z  
  yyyy'-'MM'-'dd   HH':'mm':'ss'Z'   (UniversalSortableDateTimePattern)  
   
  U           Thursday,   January   03,   2002   8:00:00   AM  
   
  y           January,   2002  
  MMMM,   yyyy   (YearMonthPattern)  
   
  Y           January,   2002  
  MMMM,   yyyy   (YearMonthPattern)  
posted @ 2008-07-23 23:20 天堂水 阅读(187) | 评论 (0)编辑

convert(char(10),getDate(),120)

返回当前时间年月日

 

以下是一些参数:来源:http://blog.csdn.net/cngkqy/archive/2006/11/14/1383294.aspx

 

1 101 美国 mm/dd/yyyy
2 102 ANSI yy.mm.dd
3 103 英国/法国 dd/mm/yy
4 104 德国 dd.mm.yy
5 105 意大利 dd-mm-yy
6 106 - dd mon yy
7 107 - mon dd, yy
8 108 - hh:mm:ss
- 9 或 109 (*) 默认值 + 毫秒 mon dd yyyy hh:mi:ss:mmmAM(或 PM)

10 110 美国 mm-dd-yy
11 111 日本 yy/mm/dd
12 112 ISO yymmdd
- 13 或 113 (*) 欧洲默认值 + 毫秒 dd mon yyyy hh:mm:ss:mmm(24h)

14 114 - hh:mi:ss:mmm(24h)
- 20 或 120 (*) ODBC 规范 yyyy-mm-dd hh:mm:ss[.fff]

- 21 或 121 (*) ODBC 规范(带毫秒) yyyy-mm-dd hh:mm:ss[.fff]

- 126(***) ISO8601 yyyy-mm-dd Thh:mm:ss:mmm(不含空格)
- 130* 科威特 dd mon yyyy hh:mi:ss:mmmAM
- 131* 科威特 dd/mm/yy hh:mi:ss:mmmAM  

posted @ 2008-07-23 22:56 天堂水 阅读(119) | 评论 (0)编辑