Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:to paraphrase Alice in Dilbert (Score 1) 271

how do you keep an armed private security force loyal?

By carefully selecting them beforehand, and by offering them and their families a place in the hideout.

Give them homes in the shelter and they take over whenever they feel like it

That's the careful selection part. Loyal people still exist in this world, you know?

Comment Re: Clarifying what you really want: (Score 1) 132

Firstly, thanks a lot for your time. This is exactly the kind of exchange I was hoping for (well, that and a small hope someone would post "sure, look here at http://semantic-documentation-...").

Is it absolutely required that the data be embedded in, and tagged within, your documents which are stored in the wiki?

Not absolutely, but I am afraid that if prose and metadata are seperate, they will go out of sync. One thing I like about SMW, for example, is how easy it is to update both at the same time, it comes so naturally that you don't even realise it.

RDFa is RDF in attributes.

Yes, if there were an editor (you already point out there isn't, damn) this would be really cool.

Earlier, you said you figured other people would have wanted to do this before. Of course they have. It's called "The Semantic Web,"

Yes and no. I want something very similar, except with a more narrow focus and thus easier to make possible. I'm currently looking at ArchiMate following someone elses pointers and the advantage of modelling business processes in it as well. Someone in the Netherlands has studied the exact problem I'm trying to solve and published a small paper.

You would not believe the insanely complex data structures necessary to build real, usable databases with only triples.

I believe. The database design for my online game (see footer) is anything but trivial and it has many places where I've encountered exactly this problem of complex relations between entities.

So, I think you would be far better off with a separate database to contain your information. The records in that database could include citations pointing to your documents, in case someone wanted to drill down to the true source of the info.

Yes, I've been thinking along similar lines, except that I would like to embed or something, at least one step better than linking, but that's a UI issue.

Yes, in most documentation you have some prose and then tables or diagrams containing hard data. It would be possible to do it this way, if the systems are well integrated.

You can still incorporate your documentation library, but from the other way around. Instead of storing your information IN your documents and mining it out, you store your information in a purpose-built SYSTEM and then refer to your documents as supporting evidence.

That is another option. What I have learnt from all the answers here put together is that no such solution exists (what a shame. Anyone got VC and looking for a Startup concept?) and that it will either have to be built or put together from existing components. That turns it into an integration issue.

Very interesting answers, thanks. I will follow up on them and talk to others in the company to find the solution that best fits.

Comment Re:No (Score 2) 499

Not to create scarcity means most creators are valueless, at more or less the valuation of a person capable of doing what you can do with a simple shell script.

Not at all. Post-scarcity on IP makes reproductions valueless, which is a whole different point. People willingly pay money to see artists perform their work live (like concerts), or commission work just for them (the way artists used to make a living when they had patrons).

Comment Re:Scammers (Score 1) 271

Very smart insight. You should also mention that organized crime has the organisational advantage in not only having a clear command structure, but also one that can operate independently of the public communication networks. Heck, in some countries they have their own mobile networks.

So, it honestly depends on the warehouse owner/manager and the individual connections that the person has.

Depends on the scenario. It makes for a better movie when the breakdown of civilization happens in hours, but from history I would guess that it will take days or weeks, more realistically. That is more than enough to take a few trucks, drive over to the nearest warehouse and simply take everything you want, at gunpoint. Time it right during the breakdown and no police will show up to stop you. You just need to be slightly faster and more organised than other looters.

Comment cheap (Score 2) 271

If you're a billionaire, then 35k is not even worth discussing, even the $3 mio. for an actual space is a minor expense. Easily comparable to what we normal people pay for, say, car insurance. So it's really just that: An "just in case" expense.

Comment Re:Clarifying what you really want: (Score 1) 132

There is existing documentation emerging from the project phase that is largely written in Word and is planned to be added to a wiki or something similar, where it can be better maintained and updated. So every piece of documentation will be touched anyway.

The metadata I am looking for is not about whole documents. I don't give a rats ass about that, if I am looking for the document about encryption protocols, I already know where to find it. I want factlets. From a security perspective, when a network is compromised I want to query the configuration database to find all systems on that subnet, but also the documentation to figure out the destinations of all data flows out of that subnet, for example. When a server fails, I want to understand which other systems that rely on it will likely fail next. When an application is reworked, I want to know which other applications are connected in one way or the other.

All this understanding of the system architecture is usually in the heads of people and hidden somewhere in tomes of documentation and graphs that you need to read and understand. I want that knowledge query-able.

Comment Re:Locality of self. (Score 1) 259

We could just program the new you not to notice the difference.

Or possibly your software version of you would become another part of you. At that point it'd be easy enough to set you up with an implant that allows you to communicate with it, synchronize your memories and such. Except the software you would have much easier access to the online networks of information and might even be able to copy itself around for backup purposes and to accomplish more tasks simultaneously. Freed from the constraints of having to run on a meatputer, the new you could contribute more to "you" than your meat version. Eventually, when that part of you dies, you might not even notice it, any more than you notice the deaths of a bunch of brain cells when you go on a bender. Or perhaps you could store your DNA off and have a new body cloned for you whenever you feel like being a meat thing again for a while. If you change the idea of consciousness that radically, it's hard to even speculate what the mind of the future even looks like.

Comment Re:API Dokumentation + Usecases + Glossary ... (Score 1) 132

You are probably right that a knowledge manager would be useful at this stage. And yes, I understand I won't be able to buy a product and press a button and everything is good. But I need to start somewhere, and the right technology choice is usually a good starting point.

Just that I would like to put the metadata into the documentation while it is being written, instead of using some kind of search or analysis in an attempt to extract it later on. It seems stupid to me to not do it right the first time.

Comment Why Do They Treat Americans Like Little Bitches? (Score 1) 352

About half will vote Democrat because they're Democrats. About half will vote Republican because they're Republicans. If the Democrats or Republicans feel disheartened about their candidate, they'll just stay home, and 20% or less of voters will actually turn out to vote. The politicians and point-one-percenters are treating Americans like little bitches because they are little bitches. This situation will continue until that stops being the case.

Comment git (Score 1) 316

Git, with jenkins integration and sensible branching policy. When jenkins sees a commit to the current development branch, or nightly, it can kick off your testing for you and tell you if anyone broke the build. Have a development branch where most churn takes place, an integration branch that you can release the development branch to when you're gearing up for a release and the features go to integration testing and a current release branch that's updated with the integration-tested code and released. Once your testers have OKed the integration build, it can be merged to your releases branch and executable that's going out the door can be built. Tag your releases with sensible versions once that happens successfully, so that you can always build your current release or any past release by checking out a tag and rebuilding it. You can use an update hook to lock your release branch so that no commits can happen to it outside release windows.

Really about 1/4th of what you need is a VCS, and 3/4s of what you need is a sensible, documented and enforced process that requires unit tests and reproducible builds. I've been in the industry for 25 years now and have only seen this a couple of times. Sun's was very strict and required an 11 page form to be filled out so that the version control branch you were updating to could be unlocked. You had to include what feature or bug the update addressed, a description of what your code did, a sign off from a code review board and the diffs for the commit. Once you checked it all in, an automated system would pick up the changes, build and test them and send out an E-Mail blaming you if the build broke. Rogue Wave software also had an automated build and test system which would do nightly builds of their libraries over all the systems they supported (Which was damn close to all the systems that were ever invented.)

At most other places, the build process was an afterthought that was thrown together by the developers on the team. This could be anything from some hastily-assembled makefiles to home-rolled shell scripts. Java projects would typically use ant or maven. Or occasionally ant AND maven. I've encountered one or two java projects that used make. I've also encountered one or two projects where they couldn't guarantee or had forgotten how to do a reproducible build. These ranged from "Oh just run make 3 or 4 times in the top level until all the build errors from missing libraries go away" to "Steve was running a jenkins server on his personal workstation and it got shut down when he was laid off. Can you fix that for us while you're at it?" If any of that sounds like where you're at, the first step to recovery is admitting you have a problem.

The universe seems neither benign nor hostile, merely indifferent. -- Sagan