info:sid/localhost:CollectionWikiData:WikiDFaq
info:sid/localhost:CollectionWikiData
CollectionWikiData
http://alcme.oclc.org:80/wikid/search/WikiDb.localhost
WikiDFaq
display
WikiD Documentation
Documentation for the OSS WikiD web application
userAssigned
mailto:jyoung@oclc.org
no
info:sid/localhost:CollectionSimpleSchemas:wiki
info:sid/localhost:CollectionExternalSchemas:xhtml
info:sid/localhost:CollectionExternalSchemas:xhtml
1.1
1
cnda6q
300
http://www.oclc.org/schemas/WikiRepository
xml
http://alcme.oclc.org:80/wikid/docs/WikiRepository
info:sid/localhost:CollectionWikiData:WikiDFaq
anonymous
CollectionWikiData
2006/01/11/21
inf_3asid_2flocalhost_3aCollectionWikiData_3aWikiDFaq_5f20060111213028795
text/xml
CollectionWikiData:WikiDFaq
2005-12-15
2006-01-11
1
1.1
repos.hasDate = "hasdate" and oai.identifier exact "info:sid/localhost:CollectionWikiData:WikiDFaq"
cql.any
=
huh?
1
1
xml
default
2006-01-11
http://alcme.oclc.org:80/wikid/docs/WikiRepository/2006/01/11/21/inf_3asid_2flocalhost_3aCollectionWikiData_3aWikiDFaq_5f20060111213028795
= You say that WikiD handles "structured data". It looks like the structural relationships are simply handled by URL linking. Is this correct? =
There are (at least) two ways to represent structural relationships. One method is to create relationships between records, and another is to create records that are inherently structured. In some cases, an application may need to incorporate both approaches.
The GSAFD Thesaurus is a good example of a combined application. In this case, the records are stored in WikiD in MARC 21 XML format (http://alcme.oclc.org/wikid/raw/CollectionGsafd:GSAFD000001.marc''''''), crosswalked on the fly into z39.88 format (Zthes) (http://alcme.oclc.org/wikid/raw/CollectionGsafd:GSAFD000001.zthes''''''), and rendered into HTML in the browser via XSLT (http://alcme.oclc.org/wikid/CollectionGsafd:GSAFD000001''''''). Note that you can navigate between records via URLs and select different views via pull-down menus. In the case of mapped terms (MT), you can also link to LCSH equivalents that exist completely independent of WikiD.
You say that WikiD handles "structured data". It looks like the structural relationships are simply handled by URL linking. Is this correct?
There are (at least) two ways to represent structural relationships. One method is to create relationships between records, and another is to create records that are inherently structured. In some cases, an application may need to incorporate both approaches.
The GSAFD Thesaurus is a good example of a combined application. In this case, the records are stored in WikiD in MARC 21 XML format (http://alcme.oclc.org/wikid/raw/CollectionGsafd:GSAFD000001.marc), crosswalked on the fly into z39.88 format (Zthes) (http://alcme.oclc.org/wikid/raw/CollectionGsafd:GSAFD000001.zthes), and rendered into HTML in the browser via XSLT (http://alcme.oclc.org/wikid/CollectionGsafd:GSAFD000001). Note that you can navigate between records via URLs and select different views via pull-down menus. In the case of mapped terms (MT), you can also link to LCSH equivalents that exist completely independent of WikiD.