Quick Upload

Loading...
Flash Player 9 (or above) is needed to view slideshows. We have detected that you do not have it on your computer.To install it, go here
Post to Twitter Post to Twitter
Share on Facebook
Myspace Hi5 Friendster Xanga LiveJournal Facebook Blogger Tagged Typepad Freewebs BlackPlanet gigya icons
SlideShare is now available on LinkedIn. Add it to your LinkedIn profile.

Wiki-syntax for Description Set Profile

From Enok, 6 months ago Add as contact

Presentation of the wiki-syntax for the Dublin Core Description Set Profile.

255 views | 0 comments | 0 favorites | 1 downloads | 0 embeds (Stats)

Embed in your blog options close
Embed (wordpress.com) Exclude related slideshows Embed in your blog

More Info

This slideshow is Public
Total Views: 255 on Slideshare: 255 from embeds: 0
Flagged as inappropriate Flag as inappropriate

Flag as inappropriate

Select your reason for flagging this slideshow as inappropriate.

If needed, use the feedback form to let us know more details.

Slideshow Transcript

  1. Slide 1: A wiki syntax for DC Description Set Profiles Fredrik Enoksson <fen@csc.kth.se> Knowledge Management Research group University of Uppsala & Royal Institute of Technology, Sweden http://kmr.nada.kth.se DC 2007, Singapore Aug 28, 2007 The Knowledge Management Research Group 1
  2. Slide 2: DSP wiki syntax, why?  Most Annotation Profile are basically webpages  Combines the formal expression of a DSP together with Annotation Profile documentation.  From the wiki-syntax create:  An HTML page can be created for human consumption An XML-serialization for the DSP  Easy to use(learn) and maintain The Knowledge Management Research Group 2
  3. Slide 3: Design goals and syntax  As easy to express as possible  Mix normal and specific DSP wiki-syntax  4 basic structures  DT, for the Description Template  ST, for the Statement Template  NLC, for the Non-literal value constraint  LC, for the Literal value constraint Reuse of Hierarchical structure of DSP  An ST belongs to the DT it is declared under  An LC or NLC belongs to the ST it is declared under The Knowledge Management Research Group 3
  4. Slide 4: Description Template Declaration of a Description Template:  identifier  minimum and maximum occurrence  standalone  Resource Class Membership Constraint DT=(min=\"1\" max=\"1\" standalone=\"yes\" identifier=\"book\") The Knowledge Management Research Group 4
  5. Slide 5: Statement Template Declaration:  Minimum and maximum occurrence  Type (Literal or Non-literal)  Property list constraints or sub-property ST=(max=\"1\" type=\"literal\" PC={http://purl.org/dc/terms/title}) The Knowledge Management Research Group 5
  6. Slide 6: Literal Constraint  Syntax Encoding Scheme  occurrence  list of possible schemas SESConstraint=(occurrence=\"disallowed\") Language Constraint  occurrence  list of languages LangC=(occurrence=\"disallowed\")  Literal list (with SES or language) {[value=\"example\" lang=\"en\"], [value=”exempel” lang=”sv”]} The Knowledge Management Research Group 6
  7. Slide 7: Non-literal value constraint Vocabulary Encoding Scheme  Occurrence  List of possible values VESConstraint=( occurrence=\"optional\" { http://www.example.com/uri3}) Value URI constraint  occurrence  List of possible URIs VURIConstraint=( occurrence=\"optional\" {http://www.example.com/uri1}) The Knowledge Management Research Group 7
  8. Slide 8: Non-literal value constraint, continued  Description description=\"agent\"  Class membership {}  Value String  maximum and minimum occurrence  rest is declared the same way as Literal Value Constraint VStringConstraint=(max=\"1\" LangC=(occurrence=\"disallowed\") The Knowledge Management Research Group 8
  9. Slide 9: Example {{{#!DSP == Description template: Book == DT=(min=\"1\" max=\"1\" standalone=\"yes\" identifier=\"book\") DT 1 === Title === ST=(max=\"1\" type=\"literal\" PC={http://purl.org/dc/terms/title}) || Definition || A name given to the resource. || ST 1.1 LC=(LangC=(occurrence=\"optional\") SESConstraint=(occurrence=\"disallowed\") ) === Creator === ST=(max=\"1\" type=\"nonliteral\" PC={http://purl.org/dc/terms/creator}) || Definition || An entity primarily responsible for making the resource. || NLC=(VURIConstraint=(occurrence=\"disallowed\") VESConstraint=(occurrence=\"disallowed\") ST 1.2 VStringConstraint=(max=\"1\" LangC=(occurrence=\"disallowed\") SESConstraint=(occurrence=\"disallowed\")) description=\"creator\" ) == Description template: Creator == DT=(min=\"1\" max=\"1\" standalone=\"no\" identifier=\"creator\") DT 2 === Name === ST=(max=\"1\" type=\"literal\" PC={http://xmlns.com/foaf/0.1/name}) || Definition || A name for some thing. || LC=(LangC=(occurrence=\"disallowed\") SESConstraint=(occurrence=\"disallowed\") ) ST 2.1 }}} //closing brackets The Knowledge Management Research Group 9