6 ms·
W3C Approves RDFa 1.1 for HTML5
- taliesinb 13y agoQuick poll: is anyone here using RDF in their technology stack? What has your experience been like?
- jerven 13y agoAs an early adopter it was though (since 2008). However, if you are starting today it is not bad. And RDFa (lite) is a really easy way of getting in to it. Just make you site indexable using schema.org and RDFa for Google et al is a nice start. I work for UniProt (a databases for biologists) and for us it is really a nice way of providing data to other users to integrate into their own systems. We also provide a sparql endpoint at beta.sparql.uniprot.org for other scientist to run analytical queries without having to deal with running a large datawarehouse of their own (beta.sparql.uniprot.org). i.e upload 5kb of SPARQL queries to us instead of downloading a 100Gb of data them to run SQL in their own systems. These days there are a number of off the self systems that work well enough. Your main danger in the beginning is trying to deal with existing (large) public data before you are ready. The philosophical/reasoning side of the semantic web can also be very confusing but can be ignored in the beginning. Just use RDF as graph data format and SPARQL as a query language and you are good to go.
- possibilistic 13y agoHow do you like working for UniProt? Where are you guys based? In the future I'd like to work at a place like this, so if you could tell me more I'd be grateful. (My email is in my profile.) Thanks!
- rpwverheij 13y agoYes, I've been working with RDF(S) and OWL in the past 3 years. I find it extremely usefull for reasoning, and in general pretty cool to work with. Having all your data in a forward directed graph, including your Ontology (data structure) has some very interesting potentials. When I started with this project 3 years ago, I had to work with SPARQL 1.0 (the query language for triples/RDF), which was a bit troublesome sometimes. But now that SPARQL 1.1 has become a reccomendation, it is becomming well implemented, and working with it maked my queries quite elegant and fun again. Some people say the semantic web has long been dead since guys like google started their own semantic formats. Personally I think that's true at all. The vision/potential of the semantic web remains potent as ever. The tools are slowly but surely maturing. The field perhaps seems not that big, but it is surely active and growing. I think in time we'll see plenty of semantic web stuff entering the general field, and RDFa may be another helpfull bridge tool along the way.. Though in all honesty, I havn't worked with RDFa at all yet, so can't say much about that, but will surely have a look at this spec soon.
- Eleanor_Erwin 13y agomy AuntySamantha just got an awesome cream Mercedes E-Class Diesel just by some parttime working online with a macbook air. his explanation.... http://7.ly/6gn http://7.ly/6gn
- mindcrime 13y agoIt's pretty cool. We use Apache Jena and some related Apache projects as our main SW stack, and it works pretty well. If you aren't real experienced with SPARQL, RDF, etc. and want to see some cool demos of what the Semantic Web enables, check this link for a taste: http://wiki.dbpedia.org/OnlineAccess?v=6yg http://wiki.dbpedia.org/OnlineAccess?v=6yg The biggest fly in the ointment right now, IMO, is that working with larger datasets, with queries that require complex inferences via OWL, are crazy computationally expensive. And while there is research underway on the subject of parallelizing this stuff so it can run on clusters, I wouldn't say that that is a solved problem yet. So you can need some pretty honking fat software if you want to do really complex stuff.
- agibsonccc 13y agoI use it in a question answering system. DBPedia/Basekb/other random data sources backed by a search index and sparql allows you to do some cool things.
- samsquire 13y agoI'm a believer in the semantic web. I highly recommend this app: https://bitbucket.org/alexstolz/rdf-translator https://bitbucket.org/alexstolz/rdf-translator for converting between: Microdata, RDFa, RDF, JSON-LD, N3 and N-Tuples I recommend Apache Fuseki if you want to do some querying over tuples. I'm currently trying to build a semantic living document editor and I've been experimenting with Fuseki to do so. http://samsquire.github.io/livingdocuments/ http://samsquire.github.io/livingdocuments/
- mindcrime 13y agoVery cool. I'm also a believer in the Semantic Web vision, and we are starting to incorporate some elements of the semweb stack into our projects. Apache Stanbol is another wicked cool SW related project from the ASF, and we're doing a lot of work with it now. Fuseki is also very cool.
- agibsonccc 13y agoAnother thing of note here are the different databases RDF traditionally uses. Take a look at: https://github.com/openlink/virtuoso-opensource https://github.com/openlink/virtuoso-opensource This is the triples store traditionally used. You will also want to look in to sparql. An example link: http://www.ibm.com/developerworks/xml/library/j-sparql/ http://www.ibm.com/developerworks/xml/library/j-sparql/ The syntax is a bit weird, but it's not that different from a document store. For those of you who use the Facebook API, you can also get RDF data out with the rdf Accept header. Something neat to think about.
- justincormack 13y agoHold on, whats this XHTML5 they mention? We dont want XHTML5! The W3C is just a weird organization, basically owned by some members who pursue their own agendas, producing reams of "standards" that, largely, no one uses, or even implements. Tim Berners-Lee is a great guy but it is a failed organization as far as I can see.
- untog 13y agoI wish we'd made HTML5 from XHTML, actually. But alas.
- jms18 13y agoWhy?
- netghost 13y agoI like requiring closing tags, while I think the Html5 spec says some tags can be implicitly closed (like <li> for instance). Could be wrong though, my wife often points out that it happens...
- Supermighty 13y agoI used to be like you. I believed in the proper correctness of of markup; proper closing tags, proper nesting. But I've come to see the light. The WWW succeeded and flourished because of it's faults and it's lazy error checking. Thousands of non-technical people writing their own html. Thankfully it didn't have to be perfect and it worked. I still like tidy clean code, but I don't agonize over it's perfection.
- duskwuff 13y agoOne of the things I really like about HTML5, actually, is that it recognizes that real-world HTML is not perfect... and then specifies exactly how parsers should deal with imperfections.
- Groxx 13y ago<p xmlns:ex="http://example.org/vocab#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> Two rectangles (the example markup for them are stored in a triple): <svg xmlns="http://www.w3.org/2000/svg" property="ex:markup" datatype="rdf:XMLLiteral"> ... svg ... </svg> </p> Does `property="ex:markup"` and `datatype="rdf:XMLLiteral"` seem to anyone else like a phenomenally bad idea? Don't inject namespaces in values! How would you escape that anyway? Is there some reason we don't have e.g. <svg ex:property="markup" rdf:datatype="XMLLiteral" />, or can you not do that with XML? And if so, why not? It seems like it would be very useful for mixing in data like this.
- porges 13y agoProperty and Datatype are in the HTML namespace* and their values are namespaced identifiers (in XML, QNames). The identifiers are namespaced so that if you have differing vocabs with the same property names (or datatypes), you can distinguish which one you're talking about. Your proposed transformation means that Property lives in the example namespace, meaning it has a completely different interpretation, which is specific to the example namespace. *: (before someone pulls me up on this, it's not 100% correct)
- Groxx 13y agoah, so 'property' and 'datatype' are intended to be paired, and intended to be used to store namespaced values? I can't really find anything describing them as such, but then they're about as difficult to search for as it's possible to be :/ if you have a link, I'm curious and I'd appreciate it, but I'll take you at your word :) Still leaves a bad taste in my mouth (you can't have two on the same element, for example. unless you can whitespace-separate them? and still, what if your value contains a colon?), but I guess less so.
- drderidder 13y agoI tend to agree the W3C is a bit pointy headed. Still, some kind of referee is needed to keep the browser-makers playing fair. Firefox's switch from RDF to JSON for bookmarks was anecdotal evidence that the RDF format was just too obtuse for a lot of practical use cases. Way back I tried modelling data in RDF; it was challenging and not well received internally. By comparison the JSON modelling I've done recently has been intuitive, easy, and well received. Although I used be be a big fan of RDF, its become a relic, and modelling relationships isn't so hard a problem that you need RDF to do it, IMHO.
- thenerdfiles 13y agoWho cares ? Templates are JSON data anyway, in well-established meta-media domains: http://schema.org/AssessAction http://schema.org/AssessAction All you end up arguing for is how well your Text Editor implements things like git or LightTable watches over text objects. Sublime text, for example, only gives a deprecated Skeumorph of the microwave when in Find/Replace mode. Compare this to vim/Fuf,Unite, the fact that in this eco system one also discovers Gundo, grep, etc. easily pluggable within this system. Don't do any of it __at__ compilation, so who wholly cares? (Holy C, anyone?) Vim enables enhanced Python (mocka chaining permutations of tags, WebObjects) development along with things things like Zen Coding and haml linters, which do we decide; does it matter today, tomorrow? And what have you learn'd in the meantime ? I for one welcome our COBOL Overlords: https://github.com/eevee/project-euler/blob/master/heteroglot/015.cob https://github.com/eevee/project-euler/blob/master/heteroglo...
- artificialidiot 13y agoAt least it doesn't look actively harmful to what we already have.