I need some help in this topic… Something also in this post…

It’s not simple to find correct scheme to make an aggregation of a business work area…

I mean: using RDF as its key element…

Aggregation power…

Without any problem…

**To make a knownledge business aggregation point of data…
To record something about the business logic not so formally…
But with a bottom-up approach…
**

The steps to make this happen are:

• identify resorces and good URIs
• identify global schemas and ontologies to not reinvent the wheel
• making all complete with OUR local business logic schema

I’m looking for some suitable schemas, but it’s not so simple…

VCARD is one, FOAF is another, DOAC maybe…
Something about events, products and so on…
Maybe also project management….
Also Ebiquity ontologies are interesting…

I mean: in a business there are people, events, products, news, and so on…

I’m thinking on it, and in the next days i’ll make something to explain better my thoughts…

Something that i have found:

‘Organization/Business’-semantics

• Responsibility/Accountability
• Role
• Contracts, Agreements
• Timeframe, deadline
• Party (Person/Organization)
  • Name
  • Address
  • …
    => Is that vcard semantics?

Any suggestions ? Trying a PlanetRDF ping… :)
Or Danny …

References:
-> VocabularyMarket
-> Looking for RDF schemas

work in progress

Commenta e condividi

This post is an open question:

imagine a corporate web site with a portfolio or a case history of business success stories….

Is this the case of application of hCard, or something similar, in RDF?

Using RDF to model some business data, and using Longwell to browse it in a clear way, is it an idea?

Having data as RDF, the data is on our control…
And not vendor-lock…

And it’s possible to use all the RDF compatible stuff on it…
Open data…

My short answer: in the next days i’ll make something about it, probably a post…

Some good start points:
-> Using RDF to create a local business review and search network
-> Getting in Touch with XML Contacts
-> Extending FOAF with Resume information
-> Modelling vCards in RDF

Visible Path: it’s very interesting and cool, anyone using it?

work in progress

Commenta e condividi

[ crosspost su VoIT ]

Non ho il tempo di parlarne in modo approfondito, anche perche’ non ho ancora letto tutto; ma ci sono ASSOLUTAMENTE delle cose molto grosse che si stanno muovendo:

• SPARQL: il linguaggio e protocollo di query e’ arrivato alla Candidate Recommendation:

  W3C is pleased to announce the advancement of the SPARQL specifications to Candidate Recommendations.
  ** With SPARQL (pronounced “sparkle”), developers and end users can write and consume search results across a wide range of information such as personal data, social networks and metadata about digital artifacts like music and images**. SPARQL Query Language for RDF specifies syntax for authoring, matching and testing. SPARQL Protocol for RDF describes remote data access and transmission of queries from clients to processors. The SPARQL Query Results XML Format is provided for search results. Visit the Semantic Web home page

• nuovi usi e confronti sul ruolo di RDF, a partire dall’intervento di Tim B.L. sul Guardian, a quello di Shelley Powers, e ad uno molto bello dal titolo “Give me back my data“ : assolutamente da vedere !!!
  Per non parlare poi di un breve, ma ottimo spunto di Danny Ayers, Web 99
• come applicazioni, e’ disponibile un interessante SPARQL Calendar Demo, che offre notevoli spunti sia per applicativi adatti agli utenti finali, sia a nuovi metodi di sviluppo riguardo al Semantic Web: devo assolutamente guardarlo!!!> This SPARQL Calendar Demo demonstrates the use of SPARQL queries over AJAX to integrate data from a myriad of native RDF and non-RDF sources.

  Currently, it finds calendar information from FOAF files, discovers shared interests between people, and suggests events that people with shared interests can attend together.

• da questo sito un paio di idee sul** Why RDF?**> * What XML did for content, RDF does for structure – by providing a standard way to describe resources the entire website, including its metadata, relationships between pages, etc. becomes repurposable, human editable, application agnostic, etc.

  * **RDF unshackles you from the physical location of files and documents**. Because resources (which can be anything) are given universal names, statements about those resources (e.g. annotations, categorization, etc.) can be made anywhere not just in the local XML file or web page containing the resource.
  * **RDF can provide a level of indirection between the application and data, as its general graph structure can represent all kinds of data, such as relational (SQL) or hierarchical (directories, XML)**. Compared to XML data integration strategies, RDF's notion of unique resources and availability of languages for describing the logical relations between data structures (such as OWL) make it easy to build abstractions over arbitrary representations of data.
  

• un ottimo intervento che fa riflettere sulla ciclicita’ di certe idee, e di certe tecnologie, sull’uso di AJAX quale mezzo per usare in modo adeguato anche la potenza elaborativa a lato client, Asking Permission First> I agree that we can do some interesting work with Ajax and grabbing data from the server and processing it on the clients. Perhaps we need to explore some newer uses of JavaScript and RDF in light of the new server-client interoperability.

  However, a developers first priority is to do no harm to those using their application. Their second priority is to ensure their pages are accessible by their target audience. **If we start making assumptions that the client’s machine is ours to do with what we will, we won’t need hackers to inject harm into our scripts–we’ll do a fine job of it, ourselves**
  

• un lungo, ma intrigante intervento sul futuro, presente del Web dal suo inventore, da vedere e rivedere… :)

AGGIORNAMENTO: Ho ripescato il post che cercavo; riguardo al talk di Tim Berners Lee e’ presente anche una piccola serie di appunti, che vanno oltre le slide della presentazione…
-> Tim Berners-Lee and web hopes and fears

I passaggi sono tutti fondamentali, e tutti che chiariscono molto alcuni argomenti fondamentali, tipo:

The Semantic Web is actually the Data Web. “We should’ve called it this in the first place.”
You can publish things as easily in RDF as HTML using PHP. He talks about SPARQL and querying the data web: the aim is for serendipitous reuse, the people you didn’t expect to use it. “**Publish your data.**”

Questo e’ un consiglio che sto cercando di seguire…

Commenta e condividi